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

Test Suite
by Marcel de Rooy 02 May '16

02 May '16

Thanks for some extensive pushing, Kyle and Brendan. We still have some tests failing. I resolved a few trivial ones: bug 16403, 16404, 16405, 16407 (hardcoded borrowers), 16408 16406 Context.t is a harder one (it should not fail only for not having a cache). I also tested on top of bug 16155. Note that we probably still need some DBIx updates ! With DBIx update and some of the above fixes all TestBuilder related tests pass: All tests successful. Files=69, Tests=1929, 85 wallclock secs ( 0.53 usr 0.13 sys + 75.33 cusr 5.92 csys = 81.91 CPU) Result: PASS And finally what about: Can't locate Catmandu/Importer/MARC.pm Can't locate object method "_convert_marc_to_json" Can't locate Catmandu/Store/ElasticSearch.pm Marcel

2 1

Koha Community Newsletter: April 2016
by kohanews 30 Apr '16

30 Apr '16

Fellow Koha users: The Koha Community Newsletter for April 2016 is here: https://koha-community.org/koha-community-newsletter-april-2016/ Many thanks to the folks who submitted articles and news to this month's newsletter. Please feel free to email me with any corrections or suggestions. Thanks! -- Chad Roseburg Editor, Koha Community Newsletter

1 0

Frameworks / DB constraints
by Tomas Cohen Arazi 29 Apr '16

29 Apr '16

Hi fellows, I noticed (in a production server) that a cataloguing framework was deleted by a user. This raised a problem with records that used that framework: trying to look at the record's detail page ended up in a fatal error. Currently, the framework code is not a FK, so we don't enforce it at DB level. A possible solution is to just add it as a FK, another option would be to fallback to the default framework in the relevant function. Jesse proposed on IRC creating the foreign key with ON DELETE SET NULL. We need to fix this, so: ideas? preferences? vote? -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

5 6

Re: [Koha-devel] Invalid local time for date in time zone: America/Santiago
by Larry Letelier 28 Apr '16

28 Apr '16

David, I will review the data on date_due field. Thanks!! for your time ! LOL time.. ;-) tomorrow --Larry 2016-04-28 0:35 GMT-03:00 David Cook <dcook(a)prosentient.com.au>: > Hi Larry, > > > > I find time fascinating, so happy to help : ). > > > > Thanks for that pastebin. That’s really helpful. > > > > We can see the problem is with the following call: > > > > $calendar->days_between( dt_from_string($data->{date_due}),$date_to_run ); > > > > If I follow correctly, $date_to_run should be the time when you run the > script in America/Santiago time. > > > > $data->{date_due} will be from the database… probably the issues table I > think… and I think that’s looking OK, since the following line appears in > the debugger: > > > > Koha::Calendar::days_between('Koha::Calendar=HASH(0x65dcf80)', > 'DateTime=HASH(0x6507b38)', 'DateTime=HASH(0x64e7848)') > > > > We’d have an error earlier if those dates were the ones causing problems… > so I think they’re OK since they’ve been created into objects as evidenced > above. > > > > However… 'DateTime=HASH(0x6507b38)' is cloned in > Koha::Calendar::days_between() and has Koha::Calendar::is_holiday() run on > it… > > > > -- > > > > I have an urgent matter now, but that’s part of the way there. I’m > thinking the problem is with the “date_due” from one of the overdue items! > Possibly something from September if the debug message is correct… > > > > > > David Cook > > Systems Librarian > > > > Prosentient Systems > > 72/330 Wattle St > > Ultimo, NSW 2007 > > > > Office: 02 9212 0899 > > Direct: 02 8005 0595 > > > > *From:* Larry Letelier [mailto:larry@opengeek.cl] > *Sent:* Thursday, 28 April 2016 1:05 PM > *To:* David Cook <dcook(a)prosentient.com.au> > *Cc:* koha-devel(a)lists.koha-community.org > *Subject:* Re: [Koha-devel] Invalid local time for date in time zone: > America/Santiago > > > > Hi David, > > > > Thanks for you reply, > > > > yes your are right, Chile abolished dst, we have a minister with many > earthquakes in him head. > > So, > > > > Here is the “perl -d overdue_notices.pl -t" using "n": > > http://pastebin.com/ZxHkNCK3 > > > > If i run again : > > > > perl overdue_notices.pl -t > > Invalid local time for date in time zone: America/Santiago > > > > Thanks in advance guys, > > > > > *-- Larry Letelier N.* > > *F: **+56 2 3205 2737* > > *F: * > *+56 9 7589 6842* > > > > 2016-04-27 23:53 GMT-03:00 David Cook <dcook(a)prosentient.com.au>: > > Oh, that’s interesting. > > > > I’ve seen this happen on other Perl projects during daylight savings time > changes. > > > > For instance, try the following Perl code: > > > > use DateTime; > > my $dt = DateTime->new( > > year => 2015, > > month => 10, > > day => 4, > > hour => 2, > > minute => 0, > > second => 0, > > time_zone => 'Australia/Sydney', > > ); > > > > You’ll get the message: > > > > “Invalid local time for date in time zone: Australia/Sydney” > > > > If I recall correctly, it’s because 4 October 2015 2:00am Australia/Sydney > didn’t exist. When that time was reached, the clock actually skipped > forward, and it became 4 October 2015 3:00am Australia/Sydney. In effect, > local time went from 1:59:59 to 3:00:00. 2:00:00 through 2:59:59 never > existed. Fascinating, no? > > > > Wikipedia says that Chile stopped observing DST in 2015: > https://en.wikipedia.org/wiki/Daylight_saving_time_in_the_Americas#Chile. > However, I’m guessing that perhaps your server/the Perl module doesn’t know > that? > > > > “Chile currently observes Daylight Saving Time (DST). Instead of turning > the clocks back one hour on Sunday, April 26, 2015 as previously planned, > the Chilean Government has decided to make no further changes to the clock > in future years.” ( > http://www.timeanddate.com/news/time/chile-abolishes-dst-2015.html) > > > > Hmm… I don’t know what date is the problem… > > > > Could you run “perl -d overdue_notices.pl -t" again, but use “n” instead > of “c”? That way, you’ll be able to see what exact call is generating this > error. > > > > I’m guessing it might be one of the lines: > > > > my $today = DateTime->now(time_zone => C4::Context->tz ); > > > > But that’s just a guess. What happens if you try running your overdues > again? You might have had the misfortune of the overdues just running at > the wrong time on the wrong day. > > > > Curious to hear how you go! > > > > David Cook > > Systems Librarian > > > > Prosentient Systems > > 72/330 Wattle St > > Ultimo, NSW 2007 > > > > Office: 02 9212 0899 > > Direct: 02 8005 0595 > > > > *From:* koha-devel-bounces(a)lists.koha-community.org [mailto: > koha-devel-bounces(a)lists.koha-community.org] *On Behalf Of *Larry Letelier > *Sent:* Wednesday, 27 April 2016 3:09 PM > *To:* koha-devel(a)lists.koha-community.org > *Subject:* [Koha-devel] Invalid local time for date in time zone: > America/Santiago > > > > Hi people, > > > > We have a 'little' issue with the overdue aka notifications process. > > > > # pwd > > /usr/share/koha/bin/cronjobs > > > > # ./overdue_notices.pl -t > > Invalid local time for date in time zone: America/Santiago > > > > perl -d overdue_notices.pl -t > > > > Loading DB routines from perl5db.pl version 1.33 > > Editor support available. > > > > Enter h or `h h' for help, or `man perldebug' for more help. > > > > main::(overdue_notices.pl:278): my $dbh = C4::Context->dbh(); > > DB<1> c > > > > Invalid local time for date in time zone: America/Santiago > > > > at /usr/share/perl5/DateTime/TimeZone.pm line 198 > > > DateTime::TimeZone::_span_for_datetime('DateTime::TimeZone::America::Santiago=HASH(0x60cfce8)', > 'local', 'DateTime=HASH(0x617e938)') called at > /usr/share/perl5/DateTime/TimeZone.pm line 157 > > > DateTime::TimeZone::offset_for_local_datetime('DateTime::TimeZone::America::Santiago=HASH(0x60cfce8)', > 'DateTime=HASH(0x617e938)') called at /usr/lib/perl5/DateTime.pm line 930 > > DateTime::_offset_for_local_datetime('DateTime=HASH(0x617e938)') > called at /usr/lib/perl5/DateTime.pm line 375 > > DateTime::_calc_utc_rd('DateTime=HASH(0x617e938)') called at > /usr/lib/perl5/DateTime.pm line 263 > > DateTime::_new('DateTime', 'hour', 20, 'second', 0, 'month', 9, > 'locale', 'DateTime::Locale::en_US=HASH(0x1e7eac8)', ...) called at > /usr/lib/perl5/DateTime.pm line 299 > > DateTime::_new_from_self('DateTime=HASH(0x6183808)', 'hour', 0, > 'minute', 0, 'second', 0, 'month', 9, ...) called at > /usr/lib/perl5/DateTime.pm line 1933 > > DateTime::truncate(undef, 'to', 'day') called at > /usr/share/koha/lib/Koha/Calendar.pm line 214 > > Koha::Calendar::is_holiday('Koha::Calendar=HASH(0x619bc20)', > 'DateTime=HASH(0x6192ad0)') called at /usr/share/koha/lib/Koha/Calendar.pm > line 290 > > Koha::Calendar::days_between('Koha::Calendar=HASH(0x619bc20)', > 'DateTime=HASH(0x61a5b90)', 'DateTime=HASH(0x60a7ce0)') called at > overdue_notices.pl line 538 > > Debugged program terminated. Use q to quit or R to restart, > > use o inhibit_exit to avoid stopping after program termination, > > h q, h R or h o to get additional info. > > DB<1> q > > > > This is a Koha 3.2008000 > > > > In MySQL and in enviroment, tzdata, TZ='America/Santiago' is set. > > > > > > Any idea with this ? > > > > Thanks for read this, > > -Larry > > > > >

1 0

Invalid local time for date in time zone: America/Santiago
by Larry Letelier 28 Apr '16

28 Apr '16

Hi people, We have a 'little' issue with the overdue aka notifications process. # pwd /usr/share/koha/bin/cronjobs # ./overdue_notices.pl -t Invalid local time for date in time zone: America/Santiago perl -d overdue_notices.pl -t Loading DB routines from perl5db.pl version 1.33 Editor support available. Enter h or `h h' for help, or `man perldebug' for more help. main::(overdue_notices.pl:278): my $dbh = C4::Context->dbh(); DB<1> c Invalid local time for date in time zone: America/Santiago at /usr/share/perl5/DateTime/TimeZone.pm line 198 DateTime::TimeZone::_span_for_datetime('DateTime::TimeZone::America::Santiago=HASH(0x60cfce8)', 'local', 'DateTime=HASH(0x617e938)') called at /usr/share/perl5/DateTime/TimeZone.pm line 157 DateTime::TimeZone::offset_for_local_datetime('DateTime::TimeZone::America::Santiago=HASH(0x60cfce8)', 'DateTime=HASH(0x617e938)') called at /usr/lib/perl5/DateTime.pm line 930 DateTime::_offset_for_local_datetime('DateTime=HASH(0x617e938)') called at /usr/lib/perl5/DateTime.pm line 375 DateTime::_calc_utc_rd('DateTime=HASH(0x617e938)') called at /usr/lib/perl5/DateTime.pm line 263 DateTime::_new('DateTime', 'hour', 20, 'second', 0, 'month', 9, 'locale', 'DateTime::Locale::en_US=HASH(0x1e7eac8)', ...) called at /usr/lib/perl5/DateTime.pm line 299 DateTime::_new_from_self('DateTime=HASH(0x6183808)', 'hour', 0, 'minute', 0, 'second', 0, 'month', 9, ...) called at /usr/lib/perl5/DateTime.pm line 1933 DateTime::truncate(undef, 'to', 'day') called at /usr/share/koha/lib/Koha/Calendar.pm line 214 Koha::Calendar::is_holiday('Koha::Calendar=HASH(0x619bc20)', 'DateTime=HASH(0x6192ad0)') called at /usr/share/koha/lib/Koha/Calendar.pm line 290 Koha::Calendar::days_between('Koha::Calendar=HASH(0x619bc20)', 'DateTime=HASH(0x61a5b90)', 'DateTime=HASH(0x60a7ce0)') called at overdue_notices.pl line 538 Debugged program terminated. Use q to quit or R to restart, use o inhibit_exit to avoid stopping after program termination, h q, h R or h o to get additional info. DB<1> q This is a Koha 3.2008000 In MySQL and in enviroment, tzdata, TZ='America/Santiago' is set. Any idea with this ? Thanks for read this, -Larry

2 2

Sign off request...
by Mark Tompsett 26 Apr '16

26 Apr '16

Greetings, A pretty simple sign off: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15086 GPML, Mark Tompsett

1 0

Debian packaging workshop
by Mirko Tietgen 26 Apr '16

26 Apr '16

Hello everyone, I made a tiny survey to get an idea of how many people might want to take part in a Debian packaging workshop at the hackfests in Berlin or Thessaloniki. Please donate 30 seconds of your time. Please just answer for yourself, don't invite your facebook friends and tweet about it. I'm only looking for the number of active Koha devs interested right now and it's not a binding vote or anything. I won't publish your names of course. http://abunchofthings.net/limesurvey/index.php/396251?lang=en Thanks! -- Mirko Tietgen mirko(a)abunchofthings.net http://koha.abunchofthings.net http://meinkoha.de

2 4

Koha Calendar
by Wolfram Schneider 25 Apr '16

25 Apr '16

On the Koha web site is a link "Calendar" https://koha-community.org/calendar/ There are only entries for "Koha Bugfix Release" I miss the KohaConf, Koha Hackfest, IRC meeting etc... I'm wondering if the calendar is still maintained? -Wolfram -- Wolfram Schneider <wosch(a)FreeBSD.org> http://wolfram.schneider.org

1 0

Understanding Zebra SRU
by David Cook 21 Apr '16

21 Apr '16

Hi all, Who all is using SRU with Zebra? I know that Marcel has been interested in Zebra's SRU since at least 2009, but information is a bit bare out there. I recently received an off-list email asking about Zebra and SRU, especially relevance searching and sorting. I admitted that I only knew about Zebra's Z39.50 functionality, so naturally I started looking into SRU and CQL. I found this webpage to be extremely helpful (alas I only found it after a day or two of experimentation): https://www.loc.gov/standards/sru/cql/spec.html I started by experimenting with CQL in yaz-client. That's as simple as "querytype cql" and "set_cqlfile /home/koha/koha-dev/etc/zebradb/pqf.properties". It took a few minutes to get me head around pqf.properties and that it defaults to using the "dc" set. For all other sets like "bath", you have to prefix with the set name (e.g. bath.name). Z> find title=brand Sent searchRequest. Received SearchResponse. Search was a success. Number of hits: 12, setno 1 SearchResult-1: term=brand cnt=12 records returned: 0 Elapsed: 0.019602 Z> find bath.name=randy Sent searchRequest. Received SearchResponse. Search was a success. Number of hits: 2, setno 2 SearchResult-1: term=randy cnt=2 records returned: 0 Elapsed: 0.020180 I seem to be able to get relevance ranking with the following (= is the relation, and relevant is the relation modifier): Z> find title=/relevant brand Sent searchRequest. Received SearchResponse. Search was a success. Number of hits: 12, setno 9 SearchResult-1: term=brand cnt=12 records returned: 0 Elapsed: 0.001049 Then a A-Z title sort with the following: Z> find title=brand sortby title/sort.ascending Sent searchRequest. Received SearchResponse. Search was a success. Number of hits: 12, setno 11 SearchResult-1: term=brand cnt=12 records returned: 0 Elapsed: 0.001210 So that's CQL in yaz-client, and you can use SRU or Z39.50 for the same result there. So I made the following change to my koha-conf.xml:  <listen id="biblioserver" >tcp:@:9999</listen> Restarted Zebra and started making SRU requests: wget "http://localhost:9999/biblios?version=1.1&operation=searchRetrieve&query=ti tle cql.eq brand&startRecord=1&maximumRecords=10&recordSchema=marcxml" Records in ascending order by biblionumber wget "http://localhost:9999/biblios?version=1.1&operation=searchRetrieve&query=ti tle cql.eq brand sortBy dc.title/sort.ascending&startRecord=1&maximumRecords=10&recordSchema=marcxml " Records in ascending order by dc.title wget "http://localhost:9999/biblios?version=1.1&operation=searchRetrieve&query=ti tle cql.eq/relevant brand&startRecord=1&maximumRecords=10&recordSchema=marcxml" Records in descending order by relevance. This one can be harder to test at a glance. but "format xml" and "elements zebra::meta" will reveal the relevance score of our records in yaz-client! Z> find any=/relevant brand Sent searchRequest. Received SearchResponse. Search was a success. Number of hits: 12, setno 10 SearchResult-1: term=brand cnt=12 records returned: 0 Elapsed: 0.001298 Z> format xml Z> elements zebra::meta Z> show 1 Sent presentRequest (1+1). Records: 1 Record type: XML <record xmlns="http://www.indexdata.com/zebra/" sysno="153" base="biblios" file="/tmp/2LUzuP3K56/upd_biblio/exported_records" type="dom./home/koha/koha-dev/etc/zebradb/biblios/etc/dom-config.xml" score="631" rank="0" size="2881" set="zebra::meta"/> nextResultSetPosition = 2 Elapsed: 0.028276 Z> Sent presentRequest (2+1). Records: 1 Record type: XML <record xmlns="http://www.indexdata.com/zebra/" sysno="50" base="biblios" file="/tmp/2LUzuP3K56/upd_biblio/exported_records" type="dom./home/koha/koha-dev/etc/zebradb/biblios/etc/dom-config.xml" score="612" rank="0" size="2570" set="zebra::meta"/> nextResultSetPosition = 3 Elapsed: 0.000612 You'd think that "rank" would provide useful info, but I think that just relates to static rank (see http://www.indexdata.com/zebra/doc/special-retrieval.html) Score is what we want here. Note that score appears to only appear for relevance queries. Anyway. I hope that info is useful to some of you, and I'd be curious if others have any neat tips for using SRU. I don't know if I'll be using it any time soon, but it's interesting to think about, even in anticipation of ElasticSearch. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Office: 02 9212 0899 Direct: 02 8005 0595

3 2

Updating Koha manual documenation
by David Cook 21 Apr '16

21 Apr '16

Hey all, What's the procedure for updating Koha manual documentation? I'd like to expand on http://manual.koha-community.org/3.20/en/sru.html#sru_search. I see there is a kohadocs.git to which Nicole contributes (http://git.koha-community.org/gitweb/?p=kohadocs.git;a=summary) but do those changes still go through Bugzilla? Does one clone the repository and just post the patches to Bugzilla and mark it as documentation? And then Nicole/RM does the merging from there? I basically just want to add that searching "title" will use "index.dc.title" because the default set in pqf.properties is "dc", and that you can use other sets by adding the prefix like "f bath.keyTitle=test" in yaz-client when using "querytype cql". But there's heaps of other search documentation that I'd like to edit, so I figure I may as well get up to speed on the procedure! I've been saying for years that I should contribute to the documentation, so maybe I should put my words where my... words are! David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Office: 02 9212 0899 Direct: 02 8005 0595

5 4