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

Z39.50 daemon with ElasticSearch
by Zeno Tajoli 24 Jun '21

24 Jun '21

Hi to, I'm trying to use ElasticSearch everywhere with Koha 20.11 I'm working on Debian 10, EleasticSearch 6.8.13, Java openjdk 11 (Debian package) The search on Opac and Intranet is OK. Problems are on z39.50 server. With bug 13937 a z39.50/SRU server is ready also with ES as search back-end. But now the demonization of the script doesn't work. If i do: sudo koha-z3950-responder --start lib and I do a check with: yaz-client Z> open 127.0.0.1:2100/biblios Connecting...OK. Sent initrequest. Target closed connection Z> The result is 'closed connection', ZOOM error: 1004 But if do: sudo koha-z3950-responder --stop lib sudo koha-shell lib /usr/bin/perl /usr/share/koha/bin/z3950_responder.pl -c /etc/koha/sites/lib/z3950 -l /var/log/koha/lib/z3950.log koha@deb:~$ yaz-client Z> open 127.0.0.1:2100/biblios Connecting...OK. Sent initrequest. Connection accepted by v3 target. ID : 81 Name : Koha/GFS/YAZ Version: 20.11.00.000/5.30.3 2af59bc45cf4508d5c84f350ee99804c4354b3b3 Options: search present triggerResourceCtrl namedResultSets Elapsed: 0.012131 Z> f css3 Sent searchRequest. Received SearchResponse. Search was a success. Number of hits: 1, setno 1 records returned: 0 Elapsed: 0.915224 Z> show 1 Sent presentRequest (1+1). Records: 1 []Record type: USmarc 00357nam a22001217a 4500 005 20201208204443.0 008 201208b ||||| |||| 00| 0 eng d 040 $c IFLA 100 $a Tajoli, Zeno 245 $a Node.js e CSS3 ... So the script 'z3950_responder.pl' is working, the transformation into daemon not. Do you have any suggestion/check to fix this situation ? Cheers Zeno Tajoli -- Zeno Tajoli System Librarian

3 4

Release of Koha 21.05.01
by Nick Clemens 24 Jun '21

24 Jun '21

Hi all! The Koha community is pleased to announce the release of Koha 21.05.01! The full release notes can be found here: https://koha-community.org/koha-21-05-01-released/ Thanks! Kyle + Nick -- Nick Clemens ByWater Solutions bywatersolutions.com Phone: (888) 900-8944 Pronouns: (he/him/his) Timezone: Eastern Follow us: <https://www.facebook.com/ByWaterSolutions/> <https://www.instagram.com/bywatersolutions/> <https://www.youtube.com/user/bywatersolutions> <https://twitter.com/ByWaterSolution>

1 0

docker1 needs debian upgrading
by Mason James 20 Jun '21

20 Jun '21

hi folks can someone (possibly bywater) upgrade debian on docker1, pleeese some tests are failing because it's debian is too old thanks, Mason

2 5

plugin won't enabled in 20.11.x and no error in logs
by Julien Sicot 18 Jun '21

18 Jun '21

Hi all, I'm facing an installation problem on a plugin we developed to manage requests for documents from stacks (which is inspired by the article request module). https://github.com/DSI-Universite-Rennes2/koha-plugin-warehouse-request <https://github.com/DSI-Universite-Rennes2/koha-plugin-warehouse-request> Until now it worked fine, but after a koha upgrade in 20.11.x, it is stuck with the status disabled and it won't activate. The plugin seems to compile well and I get no errors in the logs which is a bit tricky for debugging :-( In the database it is considered as enabled and installed which is odd... Only the plugin_methods is not supplied. The « tool » and « configure » parts seems to work but not the contrib API routes… I must be missing something but I can't see what… Thanks for the help Best, Julien Sicot Systems Librarian Université Rennes 2

4 5

Follow-up patches and why not to use them
by Joonas Kylmälä 18 Jun '21

18 Jun '21

Hi, I just bumped in another case of follow-up patch style causing us trouble. In bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28490 I had to spend considerable amount of time just reverting all the problematic patches and making sure I didn't miss any related patches, instead of just reverting one patch and knowing I would be good to go with that. Reverting this many patches also means a lot more review work yet again because you have no commit messages to reference to easily or if you want to use those you have to jump from patch to patch to find out what the change does. And this extra review work needs to be done by two people when reverting such follow-up patch series! If we instead asked the original author to fix the patches then this work would need to be done only ~once. The argument against this I have heard is that it makes the review work harder because you don't know what has changed since the previous version. I think however that is not very useful because the second reviewer doesn't benefit from this at all and makes their work harder and also the first reviewer even sometimes might review the revision after many days by which time they have forgotten already the context so basically they end up in the same situation as the second reviewer and have to jump between patches. Just my two cents, I hope we can stop doing follow-ups and instead have commits which contain one single change to decrease our time spent on review and make sure we don't miss any problems due to having to jump between so many contexts. Joonas

4 5

pqf.properties / Zebra / Z3950
by Marcel de Rooy 18 Jun '21

18 Jun '21

Hi all, Looking at bug 8280. I am wondering why we should have two pqf.properties files. They are already not exactly the same. Could we let the new daemon use the pqf file from the Zebra folder ? Marcel

1 0

Time to translate: string freeze to prepare Koha 20.05.13 has begun
by Victor Grousset/tuxayo 17 Jun '21

17 Jun '21

Hi, saluton, hola, bonjour, String freeze is into effect as of now for the 20.05.x maintenance branch. The minor release is scheduled for around the 22th. This means it's the right time to head over to the translation platform: https://translate.koha-community.org/projects/ Reminder: if you add or change a translation in version 20.05, then you must also copy it to 20.11 and 21.05. Otherwise your work will be lost for future versions. (We've had a recent significant case of that!) Happy translating, -- Victor Grousset/tuxayo

1 0

Perl syntax for strings
by Fridolin SOMERS 16 Jun '21

16 Jun '21

Hi, I see in Perl code some cases where a string in written with a space between q or qq or qw and string. Like : qq /foo bar/ instead of qq/foo bar/ It works, but I dont find it in docs like https://perldoc.perl.org/perlop#Quote-Like-Operators Most of cases are in : use CGI qw ( -utf8 ); There are only 29 other cases : git grep -E ' q[qw]? [/({]' | grep -v 'use CGI qw ' Should we add a coding guideline ? https://wiki.koha-community.org/wiki/Coding_Guidelines I must admint for me it would be better to avoid it because it breaks syntax coloring in my editor (Eclipse with EPIC). But maybe other have the same issue. Best regards, -- Fridolin SOMERS <fridolin.somers(a)biblibre.com> Software and system maintainer 🦄 BibLibre, France

2 2

some thoughts on #28519 regarding lib
by Thomas Klausner 16 Jun '21

16 Jun '21

Hi! without knowing a lot of Koha-internals (still..), I'd strongly prefer to have all the code in a lib dir (as is standard in Perl apps / modules for ages). There are also a lot of tools available to make using code stored `lib` (but not "installed" in the system, i.e. only available in the checkout) easy. The simplest is of course 'lib': https://perldoc.perl.org/lib Or more complex like https://metacpan.org/pod/lib::projectroot (which I wrote some time ago to handle a Monorepo setup; it also includes a comparison of different modules in the SEE ALSO section) OTOH, CGI::Session::Serialize is a cpan module, so technically it should not be checked out into the app code `lib`, but installed as a dependency. There are even more ways to handle installing of dependencies and the finding them, but the currently most comfortable one is https://metacpan.org/pod/Carton. Or (if running everything via Carton is too much of a change), a combination of https://metacpan.org/pod/local::lib and a modern CPAN client (https://metacpan.org/pod/App::cpanminus or https://metacpan.org/pod/App::cpm. I did not want to spam the actuall ticket with this, as I'm not sure if any of this is in fact relevant to the bug, and/or matches the current plans for Koha. Greetings, domm -- #!/usr/bin/perl https://domm.plix.at for(ref bless{},just'another'perl'hacker){s-:+-$"-g&&print$_.$/}

3 3

Sharing installation method with Hea
by dcook＠prosentient.com.au 15 Jun '21

15 Jun '21

Hi all, I was looking at https://hea.koha-community.org/systempreferences to view the different versions of Koha out there, and it got me thinking how it would be nice to know how people install Koha. I imagine that we all think that the majority of people use the Debian packages, but it would be good to know. What do people think? David Cook Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595

2 2