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

SMTP servers requiring XOAUTH2
by David Cook 08 Mar '24

08 Mar '24

Hey folks, Is anyone using Koha with SMTP servers requiring XOAUTH2? It doesn't look like the Perl libraries used by Koha are anywhere near ready for it, but it looks like Postfix has an experimental plugin available: https://github.com/tarickb/sasl-xoauth2 or https://packages.debian.org/experimental/sasl-xoauth2 I think both Gmail and Microsoft require it these days. 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

Choose your preferred dates for a Gloabl Bug Squashing Day in March
by Magnus Enger 07 Mar '24

07 Mar '24

Kia ora! Trying to get another Gloabl Bug Squashing Day (GBSD) going. Which dates would you prefer? https://terminplaner6.dfn.de/en/p/4939a0075ab483d3d337f955859f824f-633050 Please reply by Wednesday 2024-03-13. What's a GBSD, you say? It's fun, that's what it is! See this old page for an example and some more information: https://wiki.koha-community.org/wiki/2020-02-14_Global_bug_squashing_day TL; DR: Get your name as high up the "Signoffs" list on https://dashboard.koha-community.org/ as you can in a given day. (Or the other lists, if you prefer.) Best regards, Magnus Libriotech/imCode

1 0

koha SIP" over HTTPS
by Mark Hofstetter 07 Mar '24

07 Mar '24

Hi, we need (at least I think) SIP2 over https. I found some clues googling but no actual code for koha Is there something, does somebody do it, does it need implementing? thx for hints Mark -- -- Mag. Mark Hofstetter 2452 Mannersdorf Zwischen den Weingärten 3 +43 676 7345660

3 3

REMINDER: Development IRC meeting 6 March 2024
by Fischer, Katrin 06 Mar '24

06 Mar '24

Hi all, just a quick reminder that we have a Development IRC Meeting for today: https://wiki.koha-community.org/wiki/Development_IRC_meeting_6_March_2024 Time converter: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Developers+IR C+Meeting <https://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+Developers+I RC+Meeting&iso=20240306T1300> &iso=20240306T1300 Road map 24.05: . If you are a project lead, please prepare an update on your projects' status . You can also add the roadmap_24_05 now on Bugzilla to highlight any bugs/patches Hope to see you there! Katrin

1 0

PatternFly for design?
by David Cook 04 Mar '24

04 Mar '24

Hi all, Has anyone used PatternFly for designing? https://www.patternfly.org/ 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

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 28 Feb '24

28 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