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

INSTALL.debian is outdated
by Jonathan Druart 27 Nov '16

27 Nov '16

2015-11-11 22:37 GMT+00:00 Robin Sheat <robin(a)catalyst.net.nz>: > Aparrish schreef op wo 11-11-2015 om 08:13 [-0700]: >> I followed the official instructions: >> http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=INSTALL.debian;hb… > > We need to delete those, they're from 2012 and are super out of date. Shall we 1) delete them, 2)replace them with the content of the wiki page or 3) just put a link to the wiki page?

12 23

Improving Zebra logging
by David Cook 15 Apr '16

15 Apr '16

Hi all: As if you weren't all sick of me going on and on about Zebra. So you may or may not know that the Zebra logs are fairly useless in a package install of Koha. At Prosentient, we don't use package installs much, so I haven't noticed this until now, but here's a tip: If you want to see what requests are being made to Zebra, you can do the following: 1) vi /usr/sbin/koha-start-zebra 2) Under start_zebra_instance, you can change "-v none,fatal,warn" to "-v none,fatal,warn,request" (note that "request" is an undocumented log level but it should work. alternately remove none and requests should appear in the log) 3) sudo koha-zebra-stop 4) sudo koha-zebra-start 5) profit (or at least see the PQF which is sent to the server and whether you're getting errors or OK query responses) This is the kind of additional output you should expect to see: 14:15:00-17/11 zebrasrv(2) [request] Auth idPass kohauser - 14:15:00-17/11 zebrasrv(2) [request] Init OK - ID:81 Name:ZOOM-C/YAZ Version:4.2.30 98864b44c654645bc16b2c54f822dc2e45a93031 14:15:00-17/11 zebrasrv(2) [request] Search biblios OK 0 1 1+0 RPN @attrset Bib-1 @attr 1=1016 @attr 4=6 @attr 5=1 test Anyway, I wouldn't *actually* recommend changing /usr/sbin/koha-start-zebra since that's part of the koha-common package. but maybe someone would be interested in making change to the Zebra commands to allow for different logging levels. Other things to note: koha-zebra-restart isn't the same thing as koha-zebra-stop && koha-zebra-start. If you restart Zebra after changing the flags for daemon or zebrasrv, the changes won't be brought across.it's necessary to stop and start it again. even though the process is actually restarted. it seems to be restarted using the original configuration used when launching daemon in the first place. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007

3 3

Z39.50 marc21 to unimarc
by Andrea Furin 16 Feb '16

16 Feb '16

Hi. I need to import Z39.50 marc21 results in a unimarc database: is it possible? Tia andrea f.

3 2

Koha Hackfest in Berlin?
by Mirko Tietgen 07 Jan '16

07 Jan '16

Hello there, European (and other) Koha devs, I am considering hosting a Koha hackfest in Berlin/ Germany next year. It is not supposed to be a counter event to the Hackfest in Marseille nor the Kohacon, but an additional option to meet and work together. It could maybe take place July 2016 (very preliminary date for very preliminary planning), maybe 3 days or the whole week. Before I spend more time fantasizing about it, I'd like your opinion… - do you think it is a good idea (and you would consider joining)? - do you think it is a good idea (but you know you won't join)? - do you think it is not a good idea (given there is a Hackfest in Marseille and Kohacon already, or for other reasons)? - do you think you would have to decide between Berlin and Marseille? - do you think something completely different? No hard feelings if you say Kohacon + Marseille is enough, that would be very valuable feedback. For obvious reasons I would love to hear opinions from Europe (positive or negative), but if coming to Berlin is an option for people from more distant places, I'd love to hear that too. Cheers, Mirko -- Mirko Tietgen mirko(a)abunchofthings.net http://koha.abunchofthings.net http://meinkoha.de

7 14

DOM indexing performance
by Fridolin SOMERS 11 Dec '15

11 Dec '15

Hie, We have on a machine big performance issues since indexing was changed from GRS1 to DOM. I have made some benchmarks, looks like indexing time is more than twice longer. When there is a lot of circulation, the indexing of zebraqueue can take more than a minute. We know that this machine is not powerful regarding RAM and disk, but it was enough until now. Does anyone have the same problem ? The point is not to come back to obsolete GRS1, but is there a way to optimize DOM indexing ? My tests shows facets indexing does not change a lot. -- Fridolin SOMERS Biblibre - Pôles support et système fridolin.somers(a)biblibre.com

7 6

Proposed "metadata" table for Koha
by David Cook 09 Dec '15

09 Dec '15

Hi all: For those not following along at http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10662, weve recently started talking about the possibility of adding a metadata table to Koha. The basic schema I have in mind would be something like: metadata.id, metadata.record_id, metadata.scheme, metadata.qualifier, metadata.value. The row would look like: 1, 1, marc21, 001, 123456789 It might also be necessary to store metadata.record_type so as to know where metadata.record_id points. This obviously has a lot of disadvantages redundant data between metadata rows, no database cascades via foreign keys, etc. However, it might be necessary in the short-term as a temporary measure. Of course, adding yet another place to store metadata might not seem like a great idea. We already store metadata in biblioitems.marcxml (and biblioitems.marc), Zebra, and other biblio/biblioitems/items relational database fields. Do we really need a new place to worry about data? That said, if were ever going to move away from MARC as the internal metadata format, we need to start transitioning to something new. Ive noticed this metadata table model in DSpace and other library systems, and it seems to work reasonable well. I dont know if wed break down the whole record into this structure, or if wed just break down certain fields as defined by a configuration file. In the short term, Id like to use something like this to access a records 001 without going to Zebra, which can be slow to update. I need to be able to query a record using the 001 as soon as its added to the database, and I cant necessarily get that from Zebra. I also need to be able to query a record, even if Zebra is down. Failing the metadata table idea, Im not sure how else wed expose the 001 and any number of other fields without using Zebra. We store the 020 and 022 in biblioitems.isbn and biblioitems.issn, but were putting multiple values in a single field, and thats not so great for searching. We might also want to add the 035 to the fields were searching, so I dont think just adding to the biblio or biblioitems tables will really do especially since were trying to move away from MARC. Anyway, please let me know your thoughts. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007

3 7

Zebra, Query Parsing, Search, All the things
by David Cook 08 Dec '15

08 Dec '15

Hi all: I was getting 0 results when I should've been getting 78 results with the following query: Host-item:Criminology and criminal justice : an international journal I looked in the Zebra logs, and noticed that it was being transformed into the following: @not @and @attr 1=1033 Criminology @and @and @and @and @and criminal justice = an international journal @attr 1=9011 1 If we decompose the RPN, we'll see that it's basically saying: (Host-item=Crimology and ((((criminal and justice) and = ) and international) and journal )) not Suppression=1 The problem is that "=" is going to return 0 results, so the "and" will always be 0. The way to remedy this problem is to add quotes around our Host-item "value": Host-item:"Criminology and criminal justice an international journal" This will produce the following RPN query, which returns 78 results: @not @attr 1=1033 "Criminology and criminal justice = an international journal" @attr 1=9011 1 As far as I can tell, the = symbol is ignored. You can remove it or substitute another symbol and it'll still return the same number of results. Although it looks like using * for truncation doesn't work in double quotation marks... I suppose that's because it's already part of a term so you can't really translate it into RPN separately. I notice sometimes we strip out double quotation marks from queries and sometimes we add them in. we should probably do something consistent. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007

2 1

Start of new release. Some updates.
by Brendan Gallagher 04 Dec '15

04 Dec '15

Now that the release is out, I wanted to give a quick little update for the following release. I will be traveling out of the country from December 1st till December 10th. Really what my plan is that the first few weeks we will not really be pushing new features. We want to concentrate on any bugs that are needed for 3.22.x and master. Kyle will be in the office and handling those needs. He will push and work on those bugs for us. Once I am back and settled in I will concentrate on bugs and new features. I am very open for discussion and I would like to talk with as many of you as I can about the great work that you're doing. Perhaps I will get a chance to speak with each of you about your plans development wise the next few months - so we can have a clear path on timing, getting you help testing your developments, and of course working with the whole team to help QA code. I think as long as we keep our expectations on the same page, we'll have a lot of success helping you meet the goals of a great stable release. Anything that we can do to help promote more initial sign-offs (probably our biggest bottleneck) the better. Let's see what things we can implement to encourage more of us testing the code. I will be encouraging our partner libraries and our staff to be doing as much as we can even with our busy schedules. Be proud! I plan on doing a weekly release newsletter. Thanks and as always don't hesitate to ask some questions. Brendan A. Gallagher

3 2

Benchmarks - prior to the 3.22 release
by Jonathan Druart 01 Dec '15

01 Dec '15

Hi devs, Please have a look at the these benchmarks: http://wiki.koha-community.org/wiki/Benchmark_for_3.22 I let you draw the appropriate conclusions. Cheers, Jonathan

4 12

Debugging in vim
by Barton Chittenden 01 Dec '15

01 Dec '15

Hi, has anyone gotten debugging to work in vim, using the instructions here? http://wiki.koha-community.org/wiki/Debugging_in_VIM I tried it, and ran into dependency hell... If I remember correctly, Komodo-PerlRemoteDebugging-4.4.1 didn't play nicely with https://github.com/joonty/vdebug. If someone *has* gotten this working, I'd like to know how it was done, so that I can update the wiki. Thanks, --Barton

3 2