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

calendar change request on koha-community.org
by Paul Poulain 04 Mar '24

04 Mar '24

Hello all, I don't know who to ask, so asking widely, sorry. The hackfest announcement on https://koha-community.org/calendar/ is correct. However, it points to an old email, could it point to: https://lists.koha-community.org/pipermail/koha-devel/2024-February/048495.… Thanks -- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries

2 1

Z3950 authority server integrated with ElasticSearch
by Hammat Wele 01 Mar '24

01 Mar '24

Hello everyone, I'm currently facing an issue with a new Z3950 authority server integrated with ElasticSearch that I'm trying to set up. My basic searches are functioning properly, but when I attempt to use @attr attributes, it doesn't seem to work. Interestingly, attribute 1=1 (personal name) works fine. I've attempted to address this by adding the attributes in the /etc/z3950/attribute_mappings.yaml file, but unfortunately, that hasn't resolved the issue. This situation has led me to question whether it's possible, with ElasticSearch for authorities, to perform a search on a specific field, such as a title by adding @attr 1=4 on yaz-client command line. In contrast, I haven't encountered this problem with an authority server under ZEBRA. For example, when I use @attr 1=4, it works seamlessly, but with ElasticSearch, it's not functioning as expected. Example with a Z3950 authority server under Zebra $ yaz-client xxx.xxx.xxx.xxx:xxxx/authorities Connecting...OK. Sent initrequest. Connection accepted by v3 target. ID : 81 Name : Zebra Information Server/GFS/YAZ Version: 2.0.44/4.2.69 026ad3d737be4cbba4e98c6b6dc753f8029e3655 Options: search present delSet triggerResourceCtrl scan sort extendedServices namedResultSets Elapsed: 0.446096 Z> f canada Sent searchRequest. Received SearchResponse. Search was a success. Number of hits: 172856, setno 1 SearchResult-1: term=canada cnt=172856 records returned: 0 Elapsed: 0.208821 Z> f @attr 1=4 canada Sent searchRequest. Received SearchResponse. Search was a success. Number of hits: 1920, setno 2 SearchResult-1: term=canada cnt=1920 records returned: 0 Elapsed: 0.858340 Z> With a Z3950 authority server under ElasticSearch $ yaz-client xxx.xxx.xxx.xxx:xxxx/authorities Connecting...OK. Sent initrequest. Connection accepted by v3 target. ID : 81 Name : Koha/GFS/YAZ Version: 21.05.11.000/5.27.1 872b6f92a024bb53bc1c11dfeccd47f065f98238 Options: search present triggerResourceCtrl namedResultSets Elapsed: 0.425683 Z> f canada Sent searchRequest. Received SearchResponse. Search was a success. Number of hits: 56811, setno 1 records returned: 0 Elapsed: 0.478937 Z> f @attr 1=4 canada Sent searchRequest. Received SearchResponse. Search was a success. Number of hits: 56811, setno 2 records returned: 0 Elapsed: 0.261396 Z> Utilizing a Z3950 authority server with ElasticSearch, the yaz-client connects successfully to Koha/GFS/YAZ (Version 21.05.11.000/5.27.1). However, when attempting searches for 'canada' with the attribute '@attr 1=4', the number of results (56811) remains the same, '@attr 1=4' does not have effect. I aim to enable the functionality of attributes to be able to search via these field nameany => '@attr 1=1002 "#term" ', authorany => '@attr 1=1003 "#term" ', authorcorp => '@attr 1=2 "#term" ', authorpersonal => '@attr 1=1 "#term" ', authormeetingcon => '@attr 1=3 "#term" ', subject => '@attr 1=21 "#term" ', subjectsubdiv => '@attr 1=47 "#term" ', title => '@attr 1=4 "#term" ', uniformtitle => '@attr 1=6 "#term" ', srchany => '@attr 1=1016 "#term" ', controlnumber => '@attr 1=12 "#term" ', Do you have any suggestion/check to fix this situation ? Cheers Hammat Wele

3 2

Koha February release with security fixes
by Fridolin SOMERS 01 Mar '24

01 Mar '24

Hello everyone 🤗 The Koha community is proud to announce the release of February version: 23.11.03 23.05.09 22.11.15 22.05.19 It is a bugfix/maintenance release including a lot of security fixes. It is highly recommended to upgrade. The full release notes are available here: https://koha-community.org/koha-23-11-03-released/ https://koha-community.org/koha-23-05-09-released/ https://koha-community.org/koha-22-11-15-released/ https://koha-community.org/koha-22-05-19-released/ Debian packages are available. Best regards 🤓 -- Fridolin SOMERS <fridolin.somers(a)biblibre.com> Software and system maintainer 🦄 BibLibre, France

1 0

Future of mod_security
by David Cook 27 Feb '24

27 Feb '24

Hi all, mod_security has had a troubled existence the past few years, but it looks like the company behind it has transferred it over to OWASP: https://owasp.org/blog/2024/01/09/ModSecurity.html Hopefully this means mod_security starts getting updated more. David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595

1 0

Koha Community Newsletter: February 2024
by Koha Newsletter 27 Feb '24

27 Feb '24

The Koha Community Newsletter for February 2024 is here: https://koha-community.org/koha-community-newsletter-february-2024/ Many thanks to everyone who submitted articles and news to this newsletter! Please feel free to email me with any corrections or suggestions. -- Michael Kuhn Editor, Koha Community Newsletter

1 0

Re: [Koha-devel] Override sysprefs in Apache config
by David Cook 26 Feb '24

26 Feb '24

I think it might be partially broken. As per https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16520 I added the following to the OPAC and the staff interface: RequestHeader add X-Koha-SetEnv "OVERRIDE_SYSPREF_LibraryName Potato\, Potato" It did indeed load into the OPAC. In the past, I think it used to fill in and lock the syspref in the staff interface as well. but maybe not anymore. Maybe because it would just affect the staff interface, and yet sometimes maybe you only want to affect the staff interface. hmm. David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595 From: David Cook <dcook(a)prosentient.com.au> Sent: Friday, 16 February 2024 4:52 PM To: 'koha-devel' <koha-devel(a)lists.koha-community.org> Subject: Override sysprefs in Apache config Hi all, I've read this wiki page and tried this many times, and never ever gotten it to work. Is there something missing from these instructions? https://wiki.koha-community.org/wiki/Override_sysprefs_in_Apache_config David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595

3 4

Override sysprefs in Apache config
by David Cook 26 Feb '24

26 Feb '24

Hi all, I've read this wiki page and tried this many times, and never ever gotten it to work. Is there something missing from these instructions? https://wiki.koha-community.org/wiki/Override_sysprefs_in_Apache_config David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595

2 1

Development IRC meeting 28 February 2024
by Fischer, Katrin 26 Feb '24

26 Feb '24

Hi all, since we missed the meeting in early February, I have now scheduled our next meeting for this Wednesday: https://wiki.koha-community.org/wiki/Development_IRC_meeting_28_February_202 4 Time converter: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Developers+IR C+Meeting&iso=20240228T1200 I know it's a little short notice, but I hope to see you there! Katrin

1 0

DataTables 2.0.0
by David Cook 20 Feb '24

20 Feb '24

Hi all, I do not intend to draw your attention to this in any meaningful way. I just wanted to point out that DataTables 2.0.0 was released on February 15th 2024 (https://cdn.datatables.net/2.0.0/) Just squirrel away that information in the back of your brain for later. David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595

1 0

Session corruption in koha-testing-docker master
by David Cook 13 Feb '24

13 Feb '24

Hi all, The last two days I've noticed that my session is getting corrupted while I'm working on master in koha-testing-docker. I'm not touching the session myself, but seemingly randomly the session gets all kinds of DIBC data stuffed into it, and Koha seems to be parse it and Koha throws a fatal error, which can only be resolved by deleting the problematic session from the table. Just curious if anyone else is seeing this. I really don't think it's related to anything I'm working on, but I also can't reliably reproduce it. David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595

5 4