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

Communication - Extra meeting on May 10th, 13UTC
by Jonathan Druart 09 May '17

09 May '17

Hello, I'd like you to take a look at the following pad: https://mensuel.framapad.org/p/build_task_force_Koha_1711 Following what I announced in the RM proposal I will send an email to the different actors of the community. I'd like to get your opinion on the content. I propose to discuss it (quickly because we have patches to test!) for agreement tomorrow May 10th 13UTC https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Developers+I… If we need more time to reach a consensus or if there are strong objections we could rethink the whole thing and vote later. Cheers, Jonathan

1 0

Koha 16.05.12 released
by Mason James 09 May '17

09 May '17

The Koha community is proud to announce the release of Koha 16.05.12. This is a maintenance release of 16.05 and includes 49 bugfixes. The full release notes are available at https://koha-community.org/koha-16-05-12-release/ Packages will be available soon.

2 1

Single character searches are slow when queryfuzzy and/or querystemming are enabled.
by Barton Chittenden 09 May '17

09 May '17

I've got an issue that we've seen periodically at ByWater; I want to file a bug, but I don't have a clear idea of how to replicate the issue, so I'm trying to solicit information from the community on how to narrow the scope of the problem and/or measure the performance problems that I'm seeing. The problem is that keyword searches (as you'd see from an un-modified masthead search on the opac, or the "search the catalog" search on the staff client) are markedly slow on some sites when a) The search term contains single letter words like "a" in "Once Upon A Time" and b) One or both of the QueryFuzzy or QueryStemming system preferences is enabled. We first ran across this issue when we moved a number our Koha instances to slower drives, and found that some (but not all) would time out when searching for "Once upon a time", "A swiftly tilting planet", "Hitchiker's Guide to the Galaxy" (where the 's' after the apostrophe is counted as a single word). I turned on 'request' logging in zebra, here's the query that timed out: find @attrset Bib-1 @or @or @or @or @or @or @attr 1=36 @attr 4=1 @attr 6=3 @attr 9=32 @attr 2=102 "once upon a time" @attr 1=4 @attr 4=1 @attr 6=3 @attr 9=28 @attr 2=102 "once upon a time" @attr 1=36 @attr 4=1 @attr 9=26 @attr 2=102 "once upon a time" @attr 1=4 @attr 4=6 @attr 9=24 @attr 2=102 "once upon a time" @attr 4=6 @attr 5=103 @attr 9=16 @attr 2=102 "once upon a time" @attr 4=6 @attr 5=1 @attr 9=14 @attr 2=102 "onc? upon? a time? " @attr 4=6 @attr 9=14 @attr 2=102 "once upon a time" Sent searchRequest. I ran the PQF in zebra: Z> base biblios Z> find @attrset Bib-1 @or @or @or @or @or @or @attr 1=36 @attr 4=1 @attr 6=3 @attr 9=32 @attr 2=102 "once upon a time" @attr 1=4 @attr 4=1 @attr 6=3 @attr 9=28 @attr 2=102 "once upon a time" @attr 1=36 @attr 4=1 @attr 9=26 @attr 2=102 "once upon a time" @attr 1=4 @attr 4=6 @attr 9=24 @attr 2=102 "once upon a time" @attr 4=6 @attr 5=103 @attr 9=16 @attr 2=102 "once upon a time" @attr 4=6 @attr 5=1 @attr 9=14 @attr 2=102 "onc? upon? a time? " @attr 4=6 @attr 9=14 @attr 2=102 "once upon a time" Sent searchRequest. Received SearchResponse. Search was a success. Number of hits: 119, setno 1 SearchResult-1: term=once upon a time cnt=3, term=once upon a time cnt=5, term=once cnt=94, term=upon cnt=63, term=a cnt=4876, term=time cnt=515, term=once cnt=168, term=upon cnt=125, term=a cnt=19801, term=time cnt=1507, term=once cnt=9830, term=upon cnt=960, term=a cnt=82237, term=time cnt=8524, term=onc cnt=1915, term=upon cnt=914, term=a cnt=82237, term=time cnt=7709, term=once cnt=1302, term=upon cnt=914, term=a cnt=68283, term=time cnt=5442 records returned: 0 Elapsed: 98.163583 The elapsed time is just under 100 seconds; I think Koha times out after 60. We looked at the disk I/O and found that the disk where the searches were occurring was getting hammered, so we migrated the sites that were having issues onto a server that had a much faster drive, and this did, at least solve the time-out issue. The issue keeps on popping up, however -- if not in actual timeouts, then at least in complaints of slowness in search. My hypothesis is that either QueryFuzzy or QueryStemming is expanding the one letter words, i.e. a search for "a" is returning results for either all words that start with "a" or all words contaning "a", and that all of these results are written to disk before any further filtering is done. When we were seeing timeout issues, I'm not clear on which sites were likely to have issues -- sites with a very small number of bibs didn't have issues, but the problem wasn't solely by collection size. So here's what I'd like to know, for the purposes of further testing, and/or to be able to replicate the issue: 1) Is there anyone who knows all about PQF who can tell me why the query above would run so slowly? 2) Is there part of the PQF that seems to be behaving particularly badly? Which parts of the query are returning "term=a cnt=82237", and can we avoid having that called twice? 3) How do I go about constructing a data set that illustrates this problem? 4) What's the best way to measure the performance problems and/or define what the problem is when I file a bug? 5) Are there any work-arounds, given that certain sites really want query stemming and queryfuzzy enabled? Thanks, --Barton

2 1

The interface "winks" when I check out a book after upgrading firefox
by Francois Charbonnier 05 May '17

05 May '17

Hi, I use Koha 16.05 and firefox 53. When I check out an item, the interface "winks". I tried this with firefox 52, the interface stays still. Have you noticed it as well ? Any advice to fix it ? Thanks! -- François Charbonnier, Bibl. prof. / Chef de produits Tél. : (888) 604-2627 francois.charbonnier(a)inLibro.com <mailto:francois.charbonnier@inLibro.com> inLibro | Spécialistes en technologies documentaires | www.inLibro.com <http://www.inLibro.com>

3 4

Koha and xhtml2pdf
by Fridolin SOMERS 05 May '17

05 May '17

Hie. We have some problems with xhtml2pdf on Ubuntu Xenial. This soft is used by misc/cronjobs/printoverdues.sh. First it is strange that the package containing this soft "python-pisa" is not in koha-deps. I see there is "html2pdf" but there is no CSS option. In jessie we have to use the jessie-backports repo and install several packages : python-pisa python3-reportlab python-html5lib python-pypdf python-imaging python-renderpm python-reportlab python-reportlab-accel On ubuntu Xenial, we install those same packages but we have a bug in python call. We found it can be corrected by installing xhtml2pdf from its GIT repo. We would prefere to avoid this. Any help is welcome. Best regards, -- Fridolin SOMERS Biblibre - Pôles support et système fridolin.somers(a)biblibre.com

4 5

Global Bug Squashing Day - Bugs Only Edition! Wednesday, May 10th, 2017
by Nick Clemens 05 May '17

05 May '17

Hi All, A reminder / update - next week will be a GBSD dedicated to squashing bugs for the upcoming 17.05 release. I added a wiki page here: https://wiki.koha-community.org/wiki/2017-05-10_Global_bug_squashing_day_-_… ! I will be adding some bugs there and trying to keep status up to date as I can but please help out, list bugs you want to work on/are working on, add comments/sections or make the page more attractive :-) We want community involvement so if you have been thinking of getting involved this is a great time. I will be available in IRC as long as I can that day, feel free to ping me. If you are a seasoned community member and can help please add your name to the 'hand holders' list on the wiki I hope to see you all around, hear lots of questions, and see lots of squashing :-) -Nick

3 3

Jenkins is down
by Mason James 04 May '17

04 May '17

hi Folks would someone please fix jenkins specifically the debian_8 node https://jenkins.koha-community.org/computer/Debian_8/ thanks, Mason

2 1

Task schedulers and message queues for Koha
by David Cook 04 May '17

04 May '17

Hi all, In 2016, I worked on a Koha task scheduler for downloading and importing records via OAI-PMH. I have code which works, but it's lacking test coverage and I'm unsure that it will make it through QA and be accepted. I recall Chris Cormack suggesting I look at Gearman (http://gearman.org/) instead, and it looks pretty good at a glance, although Andreas and I had talked about having more control over the workers than Gearman seems to offer. Plus, it added another dependency to Koha where people already struggle with dependencies. Martin suggested that there were a lot of other implementations out there, but I haven't really found much else that provides everything we want out of the box. The one I have found is Celery (http://www.celeryproject.org/) which looks like exactly what I want I think, but it requires Python for its server and workers, and it requires a message broker like RabbitMQ or Redis. Lots of extra dependencies. Since my goal is to get our code into Koha, I really want to know what will work for people. Are people happy with a home grown solution? It's not really that complicated. My current version is essentially a task scheduler which forks a worker on demand when it's time to run a task (up to a configurable max of X tasks so you don't kill your server). It lets you submit tasks, tell the scheduler to start/schedule them, and you can even tell in progress tasks to stop (by having the scheduler tell the worker to stop and the worker decides where in its task it checks for stop commands from the scheduler). As I try to add test coverage and make this scheduler more palatable, I find myself thinking about the code more like Koha::Scheduler and Koha::Queue, and using the more scalable worker model used by others. The scheduler daemon would listen on a socket for tasks, it would create a Koha::Scheduler instance which would enqueue tasks to run once that task's time was met or exceeded. Now depending on the architecture. you could have a separate daemon or the same daemon with a Koha::Queue instance. It would accept tasks/messages from the scheduler, and it would dequeue tasks to available workers - which are separate processes - have previously registered against particular queues. In this way, you can have a oaipmh-download queue, oaipmh-import queue, a email-report queue, etc. I suspect that we could make use of Koha::Scheduler and Koha::Queue throughout much of Koha for doing background tasks. If we don't want to reinvent the wheel with Koha::Queue, we could use something like RabbitMQ. But I think we need *something*. I'm open to ideas. I already have the OAI-PMH download and OAI-PMH import handled. That's the easy part. Any worker can do that. The hard part is figuring out how the Koha Community will take up a task scheduler. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

4 8

Koha General IRC Meeting Reminder - May 3, 2017 - 20 UTC
by Nick Clemens 02 May '17

02 May '17

Hi All, Just a reminder that our next general meeting is tomorrow May 3rd in IRC at 20 UTC Link to local date and time conversion: http://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+IRC+General+M… The agenda is here: https://wiki.koha-community.org/wiki/General_IRC_meeting_03_May_2017 This meeting will be elections for 17.11 - you can see candidates for roles here: https://wiki.koha-community.org/wiki/Roles_for_17.11 Feature slush is on Friday, so make some noise tomorrow for anything you want to see moving along. Don't forget, next Wednesday will be a special Bugs Only! Global Bug Squashing Day to get things moving for outstanding bugs before the next release. If you want to get involved meetings and GBSD are good points of entry so hope to see you all there! -Nick

1 0

Koha Community Newsletter: April 2017
by kohanews 01 May '17

01 May '17

Fellow Koha users: The Koha Community Newsletter for April 2017 is here: Koha Community Newsletter: April 2017 <https://koha-community.org/koha-community-newsletter-april-2017/> 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