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

Add itemnumber constraint to aqorders_items
by Marcel de Rooy 03 Feb '14

03 Feb '14

Hi, Would you mind putting a FK constraint on itemnumber in aqorders_items (with cascaded delete) ? Please feel free to join the discussion on report http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11617 Thanks, Marcel

1 0

meetings.koha-community.org site - link for 2014 meetings
by David Nind 02 Feb '14

02 Feb '14

I thought I would post this here first - I can log a bug report if that is the right way to do it. For http://meetings.koha-community.org/ there is no link on the main page or sub pages for the 2014 meetings. A folder for 2014 exists though: http://meetings.koha-community.org/2014/ I couldn't find the details of who looks after this site on http://wiki.koha-community.org/wiki/Website_Administration David Nind | david.nind(a)gmail.com PO Box 12367, Thorndon, Wellington, New Zealand 6144 h. +64 4 9720 600 | m. +64 21 0537 847 | w. +64 4 8906 098

2 2

Modules only on CPAN
by Zeno Tajoli 31 Jan '14

31 Jan '14

Hi to all, I check with master the modules that we need to install. Those 4 modules are not present in http://debian.koha-community.org Data::Pagination 0 * 0.44 No HTTPD::Bench::ApacheBench 0 * 0.73 No Test::WWW::Mechanize 0 * 1.44 No Archive::Extract 0.48 * 0.60 No Data::Pagination is used in Solr search Koha/SearchEngine/Solr/Search.pm and opac/search.pl HTTPD::Bench::ApacheBench is used in load_testing/benchmark_circulation.pl and in load_testing/benchmark_staff.pl Test::WWW::Mechanize is used in db_dependent/www/batch.t Archive::Extract is used in plugins/plugins-upload.pl and plugins/plugins-uninstall.pl and t/db_dependent/Plugins.t In my opinion Data::Pagination and Archive::Extract could be packages in http://debian.koha-community.org, the others no (because are only for developer). Cheers Zeno Tajoli -- Dr. Zeno Tajoli Dipartimento Gestione delle Informazioni e della Conoscenza z.tajoli(a)cineca.it fax +39 02 2135520 CINECA - Sede operativa di Segrate

5 7

Re: [Koha-devel] KOHA 3.14.1 Error (Continuing)
by volkan sonmez 31 Jan '14

31 Jan '14

I applied "Bug-11475-Links-are-broken-when-editingdeleting-it.patch" patch to 3.14.1 and tried "Editing items in batch" in 3.14.2. But nothing changed in both versions. Problem still persists. Am I doing something wrong? -----Original Message----- From: koha-devel-bounces(a)lists.koha-community.org [mailto:koha-devel-bounces@lists.koha-community.org] On Behalf Of Owen Leonard Sent: Friday, January 03, 2014 4:59 PM To: koha-devel(a)lists.koha-community.org Subject: Re: [Koha-devel] KOHA 3.14.1 Error Replying to the list, since a direct message to me excludes all the other people on the list who might be interested in the conversation. > Here I will try to describe specific steps which will lead us to the > error 404 screen; > > 1- First we search for records with multiple items (books or serials, > does not matter) > > 2- We open this record we found with multiple items for editing > > 3- We chose "Edit items in batch" option from the "Edit" menu > > 4- We make corrections on the fields under the "Edit item" (For > example we change the collection code as "fiction") > > 5- We save this using "Save button" at the bottom, after we are done. > > 6- Just after we save, there will be a button named "Done" available just under the page, and when we click on "Done" we encounter the Error screen. I have just tested this in master and I get the same results. I have filed a bug report: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11475 -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org _______________________________________________ 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/

2 2

Bootstrap-styled buttons in the staff client
by Owen Leonard 29 Jan '14

29 Jan '14

When we implemented Bootstrap buttons the staff client changes were limited to places where YUI was being used to style a button (mostly in toolbars). We have lots of other buttons in the templates and some patches are starting to add the default "btn" class to non-toolbar buttons. At the moment this is causing display problems because the "btn" class conflicts with the staff client's default class for submit buttons. We have a couple of choices: 1. Stop adding the "btn" class to non-toolbar buttons and remove the class from templates which have been recently modified. 2. Start adding the "btn" class to non-toolbar buttons in ALL cases and adjust the global stylesheet so that the styles don't conflict. If we choose option 2 I would propose that we choose a secondary class as well, for instance btn-primary for submit buttons: http://getbootstrap.com/2.3.2/base-css.html#buttons This would maintain the visual difference between toolbar buttons and submit buttons. I think this is helpful for visually understanding the structure of a page. I would appreciate everyone's opinions. -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org

1 0

Re: [Koha-devel] QueryParser question
by Marcel de Rooy 27 Jan '14

27 Jan '14

Thanks, Jared. Just to be more complete: I meant with an uppercase variant in this case the variant starting with only the first character in uc (like Number-local-acquisition). I scrolled through the QueryParser code and came at the lines 855-857 of OpenILS/QueryParser.pm where three regexes are used to search for fields and aliases. Is it an idea to make these regexes case insensitive? This would make QueryParser behave case insensitive as to index names, just like C4/Search.pm now is when you disable QueryParser. (compare BZ 6786) As an example, the Number-local-acquisition index of BZ 10544 could be mentioned. QueryParser does not recognize the index name with capital N, but since it prefixes the string with pqf=, C4/Search will not change it either. Copying dev list for additional feedback? Marcel Van: Jared Camins-Esakov [mailto:jcamins@cpbibliography.com] Verzonden: donderdag 23 januari 2014 16:02 Aan: Marcel de Rooy Onderwerp: Re: QueryParser question Marcel, Upper-case indexes seem odd to me, but it would be easy to add them. For example, the following change in Koha/QueryParser/Driver/PQF.pm: 97 $self->add_search_field_alias( $class => $field => uc $field ); Regards, Jared On Thu, Jan 23, 2014 at 8:32 AM, Marcel de Rooy <M.de.Rooy(a)rijksmuseum.nl<mailto:M.de.Rooy@rijksmuseum.nl>> wrote: Hi Jared, This question came up when looking at report http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10544 The index names in the config file seem to be lower case. Upper case variants do not seem to work. Is it possible to add uppercase names? Or is it possible to have all variants work in some case insensitive manner? Thanks, Marcel -- Jared Camins-Esakov Bibliographer, C & P Bibliography Services, LLC (phone) +1 (917) 727-3445 (e-mail) jcamins(a)cpbibliography.com<mailto:jcamins@cpbibliography.com> (web) http://www.cpbibliography.com/

2 1

News from BibLibre
by Paul Poulain 27 Jan '14

27 Jan '14

Hi, Most of you probably saw it on twitter or google+, but for the others, there's an important announcement for BibLibre: http://www.biblibre.com/en/blog/afi-and-biblibre-are-getting-closer There won't be any visible change for the Koha community, except, maybe, some new developers submitting or testing patches, which is always good ;-) For libraries that could be interested in our services, that's an important change though: with a larger company, we can manage larger contracts. Until now, we focused on French libraries. 2014 will be the year where we focus on EU libraries. The 1st contract 2014 has been with a Swedish institute in Roma. Others coming soon, hopefully, so stay tuned ;-) Have a good day PS: AFI has some OpenSource (GPL v3) tools& softwares, french-centric, that we plan to promote after making them less french-centric ;-) Stay tuned here as well ! -- Paul POULAIN - BibLibre http://www.biblibre.com Free & Open Source Softwares for libraries Koha, Piwik, Jasper

1 0

git bz: UnicodeDecodeError
by Holger Meissner 24 Jan '14

24 Jan '14

Dear Koha devs, I just tried to attach a patch to a bug with git bz and got this error: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 561: ordinal not in range (128) How can I fix this? Thanks Holger

2 1

opac error logs filled with messages about 'UNIVERSAL->import is deprecated ...'
by Doug Kingston 24 Jan '14

24 Jan '14

Messages like this are appears nearly constantly from both 3.12 and 3.14 version of Koha. I checked cpan and it claims I have the latest version of Memoize::Memcached. Anyone else seeing this? [Mon Jan 20 17:42:32 2014] [error] [client 127.0.0.1] [Mon Jan 20 17:42:32 2014] Memcached.pm: UNIVERSAL->import is deprecated and will be removed in a future perl at /usr/local/share/perl/5.14.2/Memoize/Memcached.pm line 6., referer: http://catalogue.efdss.org/cgi-bin/koha/opac-basket.pl?bib_list=62755/63336/ Regards, -Doug-

2 1

Re: [Koha-devel] [Koha] Problems with frameworks
by Marcel de Rooy 23 Jan '14

23 Jan '14

It seems to me that 541$e should not map to an item field (in the first place). I checked my data, i do not have it mapped to a koha field. I have 952$i mapped to stocknumber (although we do not use it). Note also that there is a patch for stocknumber (bugzilla 10544) -----Oorspronkelijk bericht----- Van: koha-bounces(a)lists.katipo.co.nz [mailto:koha-bounces@lists.katipo.co.nz] Namens Mark Tompsett Verzonden: woensdag 22 januari 2014 18:14 Aan: koha(a)lists.katipo.co.nz Onderwerp: [Koha] Problems with frameworks Greetings, I am use 3.14.x and master, though I think this problem goes back a bit further. I am using MARC21. I log into the staff client. I click Koha administration. I click MARC bibliographic framework. In the left hand side, I scroll down to find MARC bibliographic framework test. I click it. I am then shown a pretty table, which tells me “You have 1 error(s) in your MARC configuration. Please fix them before using Koha”. I have back end access, so I figured I’d try to make sense of the message. I see it ran http://192.168.45.28:8080/cgi-bin/koha/admin/checkmarc.pl, so I take a look at the source for admin/checkmarc.pl to see if I can determine how the error was triggered. The second line in the table says “item fields”, so I figure it is talking about lines 87 to 110 in master. I see the SQL is: select tagfield,tab,kohafield from marc_subfield_structure where kohafield like "items.%" and tab >=0; So, I try running that in my backend mysql client. There are 447 rows, and most are on tab 10, but tag 541 isn’t always? It’s items.stocknumber and so I try a different query: select tagfield,tagsubfield, tab,kohafield,frameworkcode from marc_subfield_structure where kohafield like "items.stocknumber"; And here in begins the confusion. I see that 952$i and 541$e are sometimes mapping to the same kohafield items.stocknumber, and occasionally they are not. I also see 541$e sometimes on tag 5, 9, or 10. So, can anyone clear up what they should map to, if anything, and what tab they are supposed to be on? GPML, Mark Tompsett _______________________________________________ Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha

2 1