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

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

Final stretch before the next release (3.24 | 16.05)
by Jonathan Druart 21 Apr '16

21 Apr '16

Hi devs, The next Koha release will arrive soon and the feature freeze is coming in 2 weeks! I'd like to mention some works we really should have in this release: 1/ Speed improvements * Koha::Cache Interesting ideas have been implemented recently, but only few have been pushed. We can expect a real gain of performances, our cache system (Koha::Cache) has been improved with bug 11998 and 16044 but is not perfect yet. To make it great, we absolutely need patches from 16221 (Use Storable::dclone() instead of Clone::clone() for L1 cache deep-copying mode), and then 16140 (Only clear L1 cache when needed) and 16166 (Improve L1 cache performance). Bug 16105 (Cache::Memory is loaded even if memcache is used) is also cache-related. * Search There are 3 bug reports blocking bug 15262 (Run Koha Run. Koha search should be fast again) : bug 15263 (XSLT display fetches sysprefs for every result processed) is waiting for QA but 16041 is waiting for signoff. Note that I have opened 16167 to discuss about the possible removal of authorised value images. If you know someone using them, please add a comment on the bug report. To have an overview of what has been done around the performance optimisation during the last months or still need to be done, have a look at the bug 15342 (Performance 3.22 - Omnibus). 2/ Elastic Search A testing day is organised soon (today and tomorrow), stay tuned! 3/ Rewrite/refactoring I have worked a lot on refactoring some parts of Koha the last months. There are 5 left waiting for love: Bug 15801 - Move the framework related code to Koha::BiblioFramework[s] - part 2 Bug 15758 - Move the C4::Branch related code to Koha::Libraries - part 4 Bug 15407 - Move the patron categories related code to Koha::Patron::Categories - part 2 Bug 15498 - Replace ExportWithCsvProfile with ExportCircHistory Bug 15451 - Move the CSV related code to Koha::CsvProfile[s] I really would like to see them included into the next release. For the first 3, it's the continuation of parts already pushed, it would make sense to have them too. 4/ jQuery upgrade Owen suggested to upgrade our jQuery on bug 15883, it is a nice to have for the next release. 5/ Bug fixes * CGI->multi_param You have certainly notice the "CGI::param called in list context" warnings in the logs. We are going to get rid of them with bug 16154 - Replace CGI->param with CGI->multi_param in list context * Regression on currency This will become a blocker if not signed off soon. See bug 16227 - The currencies of vendor and order do not display correctly * The OPAC is not accessible if JS is disabled (blocker)! See bug 16210 (Bug 15111 breaks the OPAC if JavaScript is disabled) for a fix 6/ Versioning change It seems that we voted [1] for changing the versioning to be date based. Does someone work on that? There are adjustments to do to the codebase to make it work. But we also need to decide how to number the 2 annual major versions and the minors. Feel free to add more if you think about something. Note: please sort by severity when you are searching for a bug to sign off [2], blocker, critical and major have to be signoff before cosmetic bugs ;) Cheers, Jonathan PS: Note that there are 5 points before the 6th! [1] http://meetings.koha-community.org/2016/genereal_irc_meeting_9_march_2016.2…) [2] https://bugs.koha-community.org/bugzilla3/buglist.cgi?bug_status=Needs%20Si…

4 3

Re: [Koha-devel] Signoff request
by Marcel de Rooy 20 Apr '16

20 Apr '16

Thanks a lot. Will have a look at 16155 very soon.. ________________________________ Van: Bernardo Gonzalez Kriegel <bgkriegel(a)gmail.com> Verzonden: woensdag 20 april 2016 16:46 Aan: Marcel de Rooy Onderwerp: Re: [Koha-devel] Signoff request Hi Marcel, 14834 and 15543 are done. 16155 has some problems. Bernardo -- Bernardo Gonzalez Kriegel bgkriegel(a)gmail.com<mailto:bgkriegel@gmail.com> On Wed, Apr 20, 2016 at 10:00 AM, Marcel de Rooy <M.de.Rooy(a)rijksmuseum.nl<mailto:M.de.Rooy@rijksmuseum.nl>> wrote: Hi all, In view of the coming freeze date, I could also use a signoff on a few reports, mentioning two devs : Bug 16155 Changes to TestBuilder Bug 14834/Bug 15543 Extensions to membership expiry feature This runs fine in our production environment. Thanks, Marcel _______________________________________________ Koha-devel mailing list Koha-devel(a)lists.koha-community.org<mailto:Koha-devel@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/

1 0

Signoff request
by Marcel de Rooy 20 Apr '16

20 Apr '16

Hi all, In view of the coming freeze date, I could also use a signoff on a few reports, mentioning two devs : Bug 16155 Changes to TestBuilder Bug 14834/Bug 15543 Extensions to membership expiry feature This runs fine in our production environment. Thanks, Marcel

1 0

Nominations and elections for the 16.11 release team
by Katrin Fischer 19 Apr '16

19 Apr '16

Hi all, time flies and while the release of 16.05 comes close, we need to start planning for 16.11! So a nomination page has been added to the wiki: https://wiki.koha-community.org/wiki/Roles_for_16.11 Please add your name on the wiki page if you are interested in taking on one of the roles. We aim to hold elections at the next general IRC meeting which is scheduled for May 4, 20 UTC: https://wiki.koha-community.org/wiki/General_IRC_meeting_4_May_2016 Katrin

1 0

Reminder: Koha Developer Meeting - 20 April 2016, 15 UTC
by Katrin Fischer 19 Apr '16

19 Apr '16

Hello all, it's me again - sending another meeting reminder: https://wiki.koha-community.org/wiki/Development_IRC_meeting_20_April_2016 Please add the topics you want to talk about to the meeting agenda on the wiki. This will also be the last developer meeting before feature freeze on April 28! Hope to see you there, Katrin

1 0

kohadevbox:ansible update: custom repositories
by Tomas Cohen Arazi 19 Apr '16

19 Apr '16

I have updated kohadevbox:ansible so it can be set to use custom repositories. This is really important when it comes to testing package-related patches. This way the patch creator can build a package on a repo and ease testers' lives. Regards -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

2 1

Who all are purposing Koha as an Union Catalog?
by Indranil Das Gupta 18 Apr '16

18 Apr '16

Hi all, At a recent conference here, there was discussions about utilizing Koha as an Union catalog. I would like to know how many / if anyone here is using Koha in that manner. And what is the experience so far, the extent of custom development etc thanks -- Indranil Das Gupta Phone : +91-98300-20971 Blog : http://indradg.randomink.org/blog IRC : indradg on irc://irc.freenode.net Twitter : indradg -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=- Please exchange editable Office documents only in ODF Format. No other format is acceptable. Support Open Standards. For a free editor supporting ODF, please visit LibreOffice - http://www.documentfoundation.org

2 3