- Koha-devel - lists.koha-community.org

Global Bug Squashing Day! November 15, 2013
by Mark Tompsett 14 Nov '13

14 Nov '13

Greetings, It’s already 4 hours or so into GBSD (if you are in Kiritimati, Christmas Island, Kiribati). Thanks to Owen Leonard who pointed this out on the channel. For further reference see http://wiki.koha-community.org/wiki/2013-11-15_Global_bug_squashing_day Have fun squishing and squashing! GPML, Mark Tompsett

1 0

Re: [Koha-devel] [Koha] Summary of Open session at KohaCon13 - with a focus on Funding the Future of Koha.
by Brendan Gallagher 13 Nov '13

13 Nov '13

> > I plan to write something, but I need help from a UX person. > > I want a simple taskboard, with bugs, that people can claim by a > simple click. Then a simple karma type system. ByWater have signed off > 10 Catalyst patches, Catalyst have signed off 5 software.coop and 1 > Bywater patch, leaving Catalyst 4 patches to go ... kind of idea. > > It's not fully formed, but if it sounds like something people would to > see, or explore further, let me know and I will devote some evenings > to it. > > I would totally be behind an idea like this. Ideally it would be great to "easily" see if we (ByWater) really are doing enough to eventually get our patches signed off. Something like this would give us a great snapshot of where we need to quickly pick up the slack or just help another developer/company. Although I usually look for patches that are within my skillset to sign-off on, the company or person that submitted the patch is never an issue or goal for me to test or sign-off and I would urge that mind-set stay in the forefront for everyone (which I'm pretty positive that it will). > Chris > > -- > Chris Cormack > Catalyst IT Ltd. > +64 4 803 2238 > PO Box 11-053, Manners St, Wellington 6142, New Zealand > _______________________________________________ > Koha mailing list http://koha-community.org > Koha(a)lists.katipo.co.nz > http://lists.katipo.co.nz/mailman/listinfo/koha > -- --------------------------------------------------------------------------------------------------------------- Brendan A. Gallagher ByWater Solutions CEO Support and Consulting for Open Source Software Installation, Data Migration, Training, Customization, Hosting and Complete Support Packages Headquarters: Santa Barbara, CA - Office: Redding, CT Phone # (888) 900-8944 http://bywatersolutions.com info(a)bywatersolutions.com

2 1

Fwd: Re: [Koha] koha development
by Bob Birchall 13 Nov '13

13 Nov '13

Forwarding to the list. Bob -------- Original Message -------- Subject: Re: [Koha] koha development Date: Tue, 12 Nov 2013 09:46:26 +0530 From: rocky bang <rockybang0(a)gmail.com> To: Bob Birchall <bob(a)calyx.net.au> can you plz tell me is there any perticular maintenance folder or any specific path where Only i can able to apply patch?? coz i am getting errors while applying patches On Mon, Nov 11, 2013 at 1:33 PM, Bob Birchall <bob(a)calyx.net.au <mailto:bob@calyx.net.au>> wrote: On 11/11/13 17:54, rocky bang wrote: hii all, I am new to koha customization, I want to customize my koha 3.12.05. For that i want to know how to create a patch with .patch extension with and without using git. I also got some patches but how do i apply those patches to my koha with same version. Kindly assist me for the same. Thank you in advance. I guess you could start here: http://wiki.koha-community.org/wiki/Category:Development There's a whole page on git: http://wiki.koha-community.org/wiki/Category:Git You should also be aware of the coding guidelines: http://wiki.koha-community.org/wiki/Coding_Guidelines Patches to Koha are always welcome. Often, others will be interested in your customizations. If in doubt, you can ask on the list. Bob Birchall Calyx _______________________________________________ Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz> http://lists.katipo.co.nz/mailman/listinfo/koha

1 0

Re: [Koha-devel] Koha-devel Digest, Vol 96, Issue 11
by Andrea Furin 08 Nov '13

08 Nov '13

Il 08/11/2013 12:00, koha-devel-request(a)lists.koha-community.org ha scritto: > Send Koha-devel mailing list submissions to > koha-devel(a)lists.koha-community.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > or, via email, send a message with subject or body 'help' to > koha-devel-request(a)lists.koha-community.org > > You can reach the person managing the list at > koha-devel-owner(a)lists.koha-community.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Koha-devel digest..." > > > Today's Topics: > > 1. Please help: biblio and biblionumber (Andrea Furin) > 2. Re: Please help: biblio and biblionumber (Bob Birchall) > 3. Unimarc an standard place for biblio and biblionumber > (Zeno Tajoli) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 08 Nov 2013 00:01:38 +0100 > From: Andrea Furin <andrea.furin(a)slacky.it> > To: Koha-devel(a)lists.koha-community.org > Subject: [Koha-devel] Please help: biblio and biblionumber > Message-ID: <527C1BD2.2020101(a)slacky.it> > Content-Type: text/plain; charset=ISO-8859-1 > > hi. I had a very big problem: I cannot solve this: > in "MARC bibliographic framework test" I have an error: > "biblio and biblionumber The biblio.biblionumber and > biblioitems.biblioitemnumber fields be mapped to a MARC subfield" > > Installed Koha 3.12.6 via deb. > > I use Unimarc. > > My records.abs tells: > ############ IDENTIFICATION NUMBERS ################## > melm 001 Local-number,Local-number:n > # Local-number (biblionumber can be either in 090$9 or, on some setup, > on 001) > melm 009 Identifier-standard:w,Identifier-standard:n > melm 090$a Local-number,Local-number:n > melm 099$c > date-entered-on-file:s,date-entered-on-file:n,date-entered-on-file:y,Date-of-acquisition,Date-of-acquisition:d,Dat$ > melm 099$d > Date/time-last-modified:s,Date/time-last-modified:n,Date/time-last-modified:y > melm 099$t ccode:w > > My framework: > biblio.biblionumber -> 001_@ > bilioitems.biblioitemnumber -> 090_a > > > Please help, thanks in advance > > a.f. > > > ------------------------------ > > Message: 2 > Date: Fri, 08 Nov 2013 11:00:43 +1100 > From: Bob Birchall <bob(a)calyx.net.au> > To: koha-devel(a)lists.koha-community.org > Subject: Re: [Koha-devel] Please help: biblio and biblionumber > Message-ID: <527C29AB.4090707(a)calyx.net.au> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hi Andrea, > Its better etiquette to post to only one list. Choose the most > appropriate. In this case, its not really a development question, so > the general list is probably best. > > biblionumber and biblioitemnumber are internal Koha numbers. Field 001 > (in MARC21 and I am assuming in UNIMARC) is a control number that you > can assign. A standard Koha install will use 999$c for biblionumber and > 999$d for biblioitemnumber. You can check these settings at > Administration/Koha To Marc Mapping. There is generally no need to > change these, and its probably not a good idea. > > Did you make any changes of that nature? > > I hope this helps, > Bob > > On 08/11/13 10:01, Andrea Furin wrote: >> hi. I had a very big problem: I cannot solve this: >> in "MARC bibliographic framework test" I have an error: >> "biblio and biblionumber The biblio.biblionumber and >> biblioitems.biblioitemnumber fields be mapped to a MARC subfield" >> >> Installed Koha 3.12.6 via deb. >> >> I use Unimarc. >> >> My records.abs tells: >> ############ IDENTIFICATION NUMBERS ################## >> melm 001 Local-number,Local-number:n >> # Local-number (biblionumber can be either in 090$9 or, on some setup, >> on 001) >> melm 009 Identifier-standard:w,Identifier-standard:n >> melm 090$a Local-number,Local-number:n >> melm 099$c >> date-entered-on-file:s,date-entered-on-file:n,date-entered-on-file:y,Date-of-acquisition,Date-of-acquisition:d,Dat$ >> melm 099$d >> Date/time-last-modified:s,Date/time-last-modified:n,Date/time-last-modified:y >> melm 099$t ccode:w >> >> My framework: >> biblio.biblionumber -> 001_@ >> bilioitems.biblioitemnumber -> 090_a >> >> >> Please help, thanks in advance >> >> a.f. >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel(a)lists.koha-community.org >> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : http://www.koha-community.org/ >> git : http://git.koha-community.org/ >> bugs : http://bugs.koha-community.org/ > > > ------------------------------ > > Message: 3 > Date: Fri, 08 Nov 2013 11:34:33 +0100 > From: Zeno Tajoli <z.tajoli(a)cineca.it> > To: koha-devel(a)lists.koha-community.org > Subject: [Koha-devel] Unimarc an standard place for biblio and > biblionumber > Message-ID: <527CBE39.40600(a)cineca.it> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hi to all, > > stanrting from question of Andrea Furin, I do a check on unimarc setups. > > In en, fr-FR, it-IT the mysql field biblio.biblionumber is connecect > with 001. > > > in "MARC bibliographic framework test" I have an error: >> "biblio and biblionumber The biblio.biblionumber and >> biblioitems.biblioitemnumber fields be mapped to a MARC subfield" > but with this setup the cgi /admin/checkmarc.pl gives this error. > > So, it is better to change checkmarc.pl on insert a new default ? > > In Unimarc xsl for biblionumber it used 090$a > > Bye > Zeno Tajoli I've found this: http://kpro.tamil.fr biblio.biblionumber 090_9 Constraints: subfield ignored biblioitems.biblioitemnumber 090_a Constraints: subfield ignored http://intranet-demo.biblibre.com/ biblio.biblionumber 001_@ Constraints: subfield ignored biblioitems.biblioitemnumber 090_a Constraints: subfield ignored If I keep "Constraints: subfield ignored" all is ok for me too: it this the solution?

1 0

Use of Zebra built-in facets
by Mathieu Saby 08 Nov '13

08 Nov '13

Hi We are currently exporing the Zebra built-in facets feature in my library. I have read that Jared Camins-Esakov announced during KohaCon that he found a way to use them in Koha. Jared, could you tell us if your code is testable somewhere ? Or maybe is it still a draft? Regards, Mathieu -- Mathieu Saby Service d'Informatique Documentaire Service Commun de la Documentation Université Rennes 2 Téléphone : 02 99 14 12 65 Courriel : mathieu.saby(a)univ-rennes2.fr

1 0

Re: [Koha-devel] Customize Z39.50 results
by Andrea Furin 07 Nov '13

07 Nov '13

Il 07/11/2013 04:38, koha-devel-request(a)lists.koha-community.org ha scritto: > Message: 5 > Date: Wed, 6 Nov 2013 21:30:13 +0100 > From: andrea.furin(a)slacky.it > To: Koha-devel(a)lists.koha-community.org > Subject: [Koha-devel] Customize Z39.50 results > Message-ID: <MVUZMD$2E6A3D691C9B0CC0D5F322D795EDFD06(a)slacky.it> > Content-Type: text/plain; charset=utf-8 > > Hi to all, i'm a new entry here, ;-). > Mu first question: > in z39.50 my search results the field "Date" is always empty and I need to quickly view Date and Publisher in the results: I need the Unimarc 210_d be linked with "Date" in Z39.50 results mask and Unimarc 210_c "Publisher" with a new field "Publisher": is it possible to custome in this way? > TIA > > a.f. > > > ------------------------------ I've resolved! First of all there is an error in /usr/share/koha/lib/C4/Breeding.pm if you want to see the publication year in z39.50 search results mask you have to change line 399: $row_data{date} = $oldbiblio->{date}; --> $row_data{publicationyear} = $oldbiblio->{publicationyear}; For customize Z39.50 results mask consider file /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/modules/cataloguing/z3950_search.tt (change ../prog/LANGUAGE/modules/.. if not english) at line 155 the search results mask: <th>Server</th> <th>Title</th> <th>Author</th> <th>Date</th> <th>Edition</th> <th>ISBN</th> <th>LCCN</th> here you can add what you want, for example: <th>Publisher</th> Below the correspondet modified lines: <td>[% breeding_loo.server %] <div class="linktools"><a href="/cgi-bin/koha/catalogue/showmarc.pl?importid=[% breeding_loo.bree$ <td>[% breeding_loo.title |html %]</td> <td>[% breeding_loo.author %]</td> <td>[% breeding_loo.date %]</td> ** <td>[% breeding_loo.publisher %]</td> <td>[% breeding_loo.edition %]</td> <td>[% breeding_loo.isbn %]</td> <td>[% breeding_loo.lccn %]</td> Now consider file /usr/share/koha/lib/C4/Breeding.pm at line 394: $row_data{server} = $servername[$k]; $row_data{isbn} = $oldbiblio->{isbn}; $row_data{lccn} = $oldbiblio->{lccn}; $row_data{title} = $oldbiblio->{title}; $row_data{author} = $oldbiblio->{author}; ** $row_data{date} = $oldbiblio->{publicationyear}; ** $row_data{publishercode}= $oldbiblio->{publishercode}; $row_data{edition} = $oldbiblio->{editionstatement}; $row_data{breedingid} = $breedingid; $row_data{biblionumber} = $biblionumber; make sure that "= $oldbiblio->{publicationyear}" and NOT "= $oldbiblio->{date}" Finally you have to modify Koha to MARC mapping in Administration - Catalogue select "biblioitems" publicationyear -> 210_d (Unimarc) publishercode -> 210_c (Unimarc) I hope this can be useful. Many Thanks to "Stefano Bargioni" bargioni(a)pusc.it --

1 0

koha-translate is down...
by Paul Poulain 07 Nov '13

07 Nov '13

Hello, When I reach translate.koha-community.org, I get a nasty: Server Error An error has occurred. Thank you for your patience. (1, "Can't create/write to file '/tmp/#sql_38a_0.MYI' (Errcode: 30)") seems a disk is full or something like that :\ -- Paul POULAIN - BibLibre http://www.biblibre.com Free & Open Source Softwares for libraries Koha, Drupal, Piwik, Jasper

2 2

Summary of Open session at KohaCon13 - with a focus on Funding the Future of Koha.
by Brendan Gallagher 07 Nov '13

07 Nov '13

Hello All - I’d like to give a summary of a open discussion that occurred at KohaCon14 in Reno. A spot opened up from a presenter not being able to attend - so I volunteered to lead a discussion on Funding the future of Koha. First we invited all current and past RM’s of Koha up to the front of the room, to educate the audience on some of the “plumbing” needs in the code. When I use the term “plumbing” - I really mean portions of the code that need to be “rewritten”, “updated for current coding practices”, and a “plan for placing newer technologies and practices into the code”. Mainly plumbing = what do we need to get completed in the near future and how are we going to get that done. Many of these “needs” are larger projects that not a single organization or library can fund, as we would really need to dedicate an expert programmer some uninterrupted time to accomplish these goals. Not one support vendor can brunt the front of the plumbing needs that need to happen. We need to work together to fund this and we need to have a place and plan going forward "now". Let's do this for Koha! Points that were raised. Many attendees felt that a clear plan on what path Koha should be developing towards would be a useful project. Although setting a ridged path is a difficult thing with a community like ours, maybe a place for everyone to get or stash ideas for future paths would be a good thing to organize. An important comment here from the attendees was that when someone is funding a development - they should not just fund the code, but also plan for time and funding for the Sign-Off process and the QA process. Funding and how would we organize this? Since many in the audience were from the USA - there was discussion of getting a users group going again OR creating some sort of “non-profit like org” where libraries could pool funding towards projects. An organization like this would be able to apply for grants etc. Something where we could crowd-source funding and then fund a developer for a number of hours towards a project. My thoughts on some things that we can do in the USA. Have a hackfest in Athen’s Ohio next summer. Next year will be 10 years since Koha migrated to the US and I think it’s about time we have a hackfest here. I have briefly talked with Owen Leonard about putting this together for next summer and would love for help and encourage those from overseas to join us. (Also a commitment here that we will be sending a few employees to the France Hackfest in March and will continue to do this every year that we can - that also being right around a feature freeze for releases it's important to have a solid week dedicated to hacking koha only) Gauge the interest of a North American Koha users group so at least we are having more of the community meeting together and sharing practices and ideas. Comments from Galen "As far as a US or North American user group goes: I think a relaunch should start off with just the goal of hosting a US/NA conference, as it would /not/ be necessary to set up a nonprofit first to run conferences. We'd just need willing hosts and, if necessary, a firm willing and able to act as a fiscal agent. That's not to say that such a group couldn't pursue nonprofit status later, but we can get a lot of education and user-connecting done without ever having to have a formal organization." Thanks all - this is to promote discussion and hopefully we can all do this together! Brendan -- --------------------------------------------------------------------------------------------------------------- Brendan A. Gallagher ByWater Solutions CEO Support and Consulting for Open Source Software Installation, Data Migration, Training, Customization, Hosting and Complete Support Packages Headquarters: Santa Barbara, CA - Office: Redding, CT Phone # (888) 900-8944 http://bywatersolutions.com brendan(a)bywatersolutions.com <info(a)bywatersolutions.com>

2 1

Customize Z39.50 results
by andrea.furin＠slacky.it 06 Nov '13

06 Nov '13

Hi to all, i'm a new entry here, ;-). Mu first question: in z39.50 my search results the field "Date" is always empty and I need to quickly view Date and Publisher in the results: I need the Unimarc 210_d be linked with "Date" in Z39.50 results mask and Unimarc 210_c "Publisher" with a new field "Publisher": is it possible to custome in this way? TIA a.f.

1 0

3.14.x branched
by Galen Charlton 06 Nov '13

06 Nov '13

Hi, I have branched 3.14.x. Until 3.14.0 is released, I will push bugfixes, particularly release blockers, to both master and 3.14.x. New feature and enhancement patches will be pushed only to master, although I will hold off applying any that require a database update until after 3.14.0 is cut. Regards, Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: gmc(a)esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org

1 0