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

"Sponsored-by: " in commits
by Paul Poulain 19 Nov '12

19 Nov '12

A reminder: the script that generates the release notes automatically detect when there is a "Sponsored-by: Some Library that sponsored" and put "Some library that sponsored" in the release notes. This feature was used only twice in the 3.10 release, I think it's an undocumented feature ;-) So, for next patches, don't hesitate to add the "Sponsored-by: " tag in your commits. (I've added the hint on http://wiki.koha-community.org/wiki/SubmitingAPatch) Note: for 3.10, the 2 that were already here are: * Centre collégial des services regroupés (CCSR) * Universidad Nacional de Córdoba I'm adding the following ones with the patch bumping kohaversion to 3.10.0: Sponsored-by: Central Kansas Library System (CKLS), Plum Creek Library System and Washoe County Library System Sponsored-by: Los Gatos Public Library and Harrison Carmel Public Library Sponsored-by: Talking Tech Sponsored-by: VOKAL Sponsored-by: Brooklyn Law School Library Sponsored-by: North Central Regional Library (NCRL) Sponsored-by: Washoe County Library System Sponsored-by: Corpus Christi Public Libraries Sponsored-by: Northeast Kansas Library System (NEKLS) Sponsored-by: Université d'Aix-Marseille Sponsored-by: Université de Rennes 2 Sponsored-by: Université de Lyon 3 Sponsored-by: Université de St Etienne Sponsored-by: BDP de la Meuse If there are more to add, let me know ! -- Paul POULAIN - BibLibre http://www.biblibre.com Free & Open Source Softwares for libraries Koha, Drupal, Piwik, Jasper

1 0

Koha 3.10 release in 4 days (reminder)
by Paul Poulain 19 Nov '12

19 Nov '12

Hello world, Just a reminder = the Koha 3.10.0 release is expected for the end of this week (friday). You have up to thursday to work on translations ! -- Paul POULAIN - BibLibre http://www.biblibre.com Free & Open Source Softwares for libraries Koha, Drupal, Piwik, Jasper

2 1

Why not change IndependantBranches?
by MJ Ray 19 Nov '12

19 Nov '12

So there's this text in the kohadocs.git en/manual.xml about IndependantBranches that says "It is important that this value be set before going live and that it NOT be changed." The kohadocs.git log message of when that IndependentBranches warning line was added is commit c2885b75d1dd8085df072fcd0af17d1bbe046f90 "integrate wayne state manual contents" Anyone know why it's important that this value not be changed after going live? Anecdotes after asking on IRC a few times and by direct mail suggests that some have tried changing it and not noticed anything break - just the behaviour changes and some patrons might not be visible by any staff except a superlibrarian. Thanks in advance for any answers, -- MJ Ray, Software Engineering Specialist, www.software.coop member. Emails 3 x daily: please use info(a)software.coop for faster answer. Turo Technology LLP, reg'd in England+Wales, number OC303457 Registered Office: 12 Canada Road, Erith, LONDON, DA8 2HE

5 7

Field 001 auto-increment problem in 3.8.5
by Paul 17 Nov '12

17 Nov '12

I have finally resolved my problem with the 001 field (new table in the Koha db and new Perl script) and put it into our production server. However, I *may* have discovered a bug and would appreciate if someone could confirm whether it is intrinsic to 3.8.5 or to our specific installation [both my sandbox and production server exhibit the same behaviour, but use the same db.] If it is a bug, I will be happy to supply my solution if there is not a more elegant fix. Basically, in the MARC Frameworks Constraints / Other Options / Plugin, it does not matter what plugin script name is used, Koha continues to use callnumber.pl regardless. However, at item level, 952$o ("full call number") will accept and run a differently named script, e.g. our_callnumber.pl I have checked the relevant row in marc_subfield_structure as: ([] added for clarity) 1 @ [control field] [control field] 0 0 [blank] 0 [blank] [blank] controlnumber.pl 0 0 [blank] \N [blank] [blank] 9999 and do not have a working script called controlnumber.pl -- I have an empty file and just added it to 001 / Constraints / Other Options / Plugin to demonstrate that callnumber.pl is in fact being used - modified for our use -- and if I remove or rename callnumber.pl the system fails. I haven't found anywhere that callnumber.pl might be "hardcoded" ... perhaps somewhere, I just haven't had time to go beyond a quick grep. Best - Paul

1 0

Field 001 auto-increment problem in 3.8.5
by Paul 17 Nov '12

17 Nov '12

I have finally resolved my problem with the 001 field (new table in the Koha db and new Perl script) and put it into our production server. However, I *may* have discovered a bug and would appreciate if someone could confirm whether it is intrinsic to 3.8.5 or to our specific installation [both my sandbox and production server exhibit the same behaviour, but use the same db.] If it is a bug, I will be happy to supply my solution if there is not a more elegant fix. Basically, in the MARC Frameworks Constraints / Other Options / Plugin, it does not matter what plugin script name is used, Koha continues to use callnumber.pl regardless. However, at item level, 952$o ("full call number") will accept and run a differently named script, e.g. our_callnumber.pl I have checked the relevant row in marc_subfield_structure as: ([] added for clarity) 1 @ [control field] [control field] 0 0 [blank] 0 [blank] [blank] controlnumber.pl 0 0 [blank] \N [blank] [blank] 9999 and do not have a working script called controlnumber.pl -- I have an empty file and just added it to 001 / Constraints / Other Options / Plugin to demonstrate that callnumber.pl is in fact being used - modified for our use -- and if I remove or rename callnumber.pl the system fails. I haven't found anywhere that callnumber.pl might be "hardcoded" ... perhaps somewhere, I just haven't had time to go beyond a quick grep. Best - Paul

1 0

Books on hold does not displays the Call number and Barcode
by Waqar Azeem 17 Nov '12

17 Nov '12

I have entered the Call Number and Barcode along with books that can be seen from other screens. But search for the list of books checked out (Placed on Holds) by a particular Patron. The resulting list of books on hold does not displays the Call number and Barcode. Both the columns are empty. /w

2 2

Koha's Manual Translation
by Tomas Cohen Arazi 16 Nov '12

16 Nov '12

Yesterday on IRC a Koha user asked about a way to help translating the Koha Manual to spanish. I'm not sure he is subscribed to this list or the spanish-speaking localized one (koha-es on yahoo still). We've set a while ago (and advertised here) a service to accomplish that on http://es.koha-community.org/manual that covers several other languages than just spanish (just take a look at the progress the arab translation has made). As we already tried to express, we are willing to integrate this setup with the current pootle/translation scripts already used in translate.koha-community.org ASAP so we have the most awesome Manual for our users, translated to every language Koha supports. So, santy, if you are reading, just meet bgkriegel or tcohen on IRC. Regards To+

1 0

String Freeze for 3.8.7
by Chris Cormack 15 Nov '12

15 Nov '12

Hi all We are at that time again, a week out from a 3.8.x release. So could the translation manager(s) please generate new files for 3.8.x and could the translaters translate :) Chris -- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand

2 1

Upgrading Koha's license?
by Owen Leonard 15 Nov '12

15 Nov '12

I have been working on incorporating some features of the Bootstrap framework into Koha (http://twitter.github.com/bootstrap) It offers some nice features that can help us finish getting rid of YUI. However, Bootstrap's license is Apache 2.0 which I'm told is incompatible with Koha's GPL2 license. What do we need to do to make inclusion of Bootstrap possible? Thanks Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org

15 21

Bugzilla change proposal
by Paul Poulain 15 Nov '12

15 Nov '12

Hello koha-devel, -first of all, BibLibre is still facing problem with mails on this list: it seems we can post, but don't recieve any mail from it. That's why I missed the "Upgrading Koha license" thread, (I say +1 for GPL 3 of course). So if you answer this mail, would you be kind to add me directly also. - The main reason of this mail are the release notes for Koha 3.10 : I made a lot of work to improve the script generating release notes, and I'm quite happy with the current result. I plan to release the text only notes, but also fancy and nice looking release notes (html & hopefully PDF, with a lot of details for enhancements, including some screenshots) What strikes me is that "Enhancements" mix patches that enhance an existing feature (and sometimes it's a tiny improvement), and patches that add a completely (and major) new feature. For readers I think it would be better to separate "Enhancements of an existing feature" and "New feature". What about adding separating "enhancements" in "enhancement" (of an existing feature) and "New feature" by adding the "new feature" to severity list ? The script generating release notes would be trivial to update to reflect that. Of course that would not be for 3.10, but 3.12+ cheers -- Paul POULAIN - BibLibre http://www.biblibre.com Free & Open Source Softwares for libraries Koha, Drupal, Piwik, Jasper

5 4