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

Time to translate: string freeze to prepare Koha 19.11.22 has begun
by Wainui Witika-Park 17 Sep '21

17 Sep '21

Hello, String freeze is into effect as of now for the 19.11.x maintenance branch in preparation for the 19.11.22 release. 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 19.11, then you must also copy it to 20.05, 20.11 and 21.05. Otherwise your work will be lost for future versions. Happy translating! Wainui Witika-Park (she/her)

1 0

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

17 Sep '21

Hi, saluton, hola, bonjour, String freeze is into effect as of now for the 20.05.x maintenance branch. 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. Happy translating :) -- Victor Grousset/tuxayo

1 0

Time to translate: string freeze to prepare 20.11.10 release
by Fridolin SOMERS 16 Sep '21

16 Sep '21

Hi, String freeze is into effect 🥶 The 20.11.x maintenance branch is preparing for 20.11.10 release 📦 This means it's the right time to head over to the translation platform: https://translate.koha-community.org/projects/ Keep in mind that translations must be done with priority on higher version 21.05 🔥 Happy translating 🌎🌍🌏 -- Fridolin SOMERS <fridolin.somers(a)biblibre.com> Software and system maintainer 🦄 BibLibre, France

1 0

Call for news - Newsletter September 2021
by Koha Newsletter 13 Sep '21

13 Sep '21

Hi I'm collecting news for the September 2021 Koha Community Newsletter. Please send anything noteworthy to: kohanews (at) gmail (dot) com News criteria: * News items can be of any length. * Images are fine. * Anything and everything Koha. * Submit by the 26th of the month. Text format criteria: * Just structured plain text, or * HTML text to include tables or similar For events: * Consider adding your event to the Koha Community calendar at https://koha-community.org/calendar/ Thank you! Michael Kuhn Editor, Koha Community Newsletter

1 0

New developers at BibLibre
by Paul Poulain 12 Sep '21

12 Sep '21

Hello koha-devel, 3 new developers are joining the BibLibre team: * Marion Durand, internship for 6 month * Jeremy Breuillard, and Florian Bontemps, both being half time working, half time at school They'll all work on Koha (Marion full time, Jeremy and Florian part-time) -- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries

4 3

Monthly Community Meeting
by Renvoize, Martin 12 Sep '21

12 Sep '21

Hi all, We had our monthly general meeting today, as usual, hosted on IRC. Attendance has been very low for a while now and we mooted the idea of dropping it from our schedule and instead just having perhaps two meetings a year, one for Kohacon votes and a second for a broader annual general meeting should anyone want to raise any points in that formal setting. The next meeting is scheduled for 13th October 2021 at 1400 UTC where we will vote on the new reduced format. We're open to new idea's at any time and I'd be happy to try a video meeting or something if people would prefer. But at this point, we're not discussing much and I don't know if we're missing peoples views or people just don't have many or they have other ways of communicating with the community at large. Hope everyone is well, *Martin Renvoize, MPhys (Hons)* <https://www.ptfs-europe.com> Head of Development and Community Engagement *Phone:* +44 (0) 1483 378728 *Mobile:* +44 (0) 7725 985 636 *Email:* martin.renvoize(a)ptfs-europe.com www.ptfs-europe.com *Sign up for our newsletters here <http://eepurl.com/dPjjkn> or by scanning the QR code* Registered in the United Kingdom No. 06416372 VAT Reg No. 925 7211 30 The information contained in this email message may be privileged, confidential and protected from disclosure. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. If you think that you have received this email message in error, please email the sender at info(a)ptfs-europe.com

3 2

System administration, permissions and the like
by Marcel de Rooy 10 Sep '21

10 Sep '21

Hi all, A discussion on bug 28882 triggered me to open the following reports: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28989 Allow viewing systempreferences only https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28990 Allow changes for a configurable subset of systempreferences by superlibrarian only https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28991 Setting user permissions should be limited by current user permissions If you are interested in the subject, have some ideas about it, please add a comment! Thanks, Marcel

2 2

Listing Zebra (and Elasticsearch) indexes for end-users' benefit
by dcook＠prosentient.com.au 09 Sep '21

09 Sep '21

Hi all, As always, a new day brings a new Zebra idea. One of my librarians asked me if there was any way to get a list of Zebra indexes (particularly for Record Matching Rules), and I was all prepared to say no. when I remembered something I read the other day. It turns out you can send the query "@attr exp1 1=1 attributedetails" to the magical database "IR-explain-1", and it will give you a list of all the indexes in that database along with the type of index and how many documents are indexed against that index in the database. I think this is something that we should add to Koha! I'm not familiar with Koha's use of Elasticsearch, but I imagine there is an easy way of getting a list of Elasticsearch indexes? -- Of course, while having a list of indexes is good, it would be nice to know what MARC data is in each of those indexes. I'm thinking about creating a Koha Plugin that parses "biblio-koha-indexdefs.xml" and shows a user-friendly view of what parts of the MARC record are put into which indexes. -- What do folk think about that? I think having a list of Zebra indexes would be very useful for Record Matching Rules, but also for a "Search tips" guide for the Staff Interface and OPAC. While we could provide a static list of indexes, but I think that would be too much of a maintenance burden. I think having a list from Zebra (or Elasticsearch), which we could cache in Memcached, would be the way to go. Ideally, we could have an API route that surfaces this information, so that we could just do an AJAX lookup from a web interface. -- I'm hoping my librarian will sponsor development of a plugin, but I think this would be useful in the core Koha code. 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 5

Help! Plugin's API endpoint validation failing only on customer server
by Isherwood, Andrew 09 Sep '21

09 Sep '21

Hi I've been banging my head against this one for a few hours now, so I'm hoping someone can help! I've developed a Koha ILL backend for RapidILL for a customer. Part of the development was to create a plugin that provides Koha Rest API endpoints that effectively proxies to the RapidILL SOAP API. Everything works perfectly on my development server running koha-testing-docker However, on the customer's Koha instance, all API calls to the plugin fail validation with the following error: { "errors": [ { "message": "Expected object - got null.", "path": "/body" } ], "status": 400 } I'm pretty confident that my plugin and the requests I'm making to it are correct since everything works perfectly on my dev server, however the API spec is here https://github.com/PTFS-Europe/koha-plugin-rapidill/blob/main/Koha/Plugin/C… and a sample request body is: { "requestId": "17900139", "updateAction": "Cancel", "metadata": { "UpdateComment": "TEST PLEASE CANCEL REQUEST" } } The most annoying thing is that I've had this problem a few times before in the past and it's always come down to module dependency versions, though this time, I'm not sure this is the problem. I've aligned versions of the following modules on the customer's server to match the versions on my koha-testing-docker, these have been the problematic modules in the past. But still no luck: JSON - 2.90 JSON::Validator - 3.14 Mojolicious - 8.12 Mojolicious::Plugin::OpenAPI - 2.16 In an attempt to narrow it down, I've been trying to find somewhere else in Koha where a POST API call is made, but haven't found one, any idea? Does anyone have any suggestions where else I could try? Many thanks Andrew ------------------------------- Andrew Isherwood Senior Software Engineer Email: andrew.isherwood(a)ptfs-europe.com www.ptfs-europe.com Registered in the United Kingdom No. 06416372 VAT Reg No. 925 7211 30 The information contained in this email message may be privileged, confidential and protected from disclosure. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. If you think that you have received this email message in error, please email the sender at info(a)ptfs-europe.com

2 1

Security releases for all stable branches - UPGRADE!
by Jonathan Druart 08 Sep '21

08 Sep '21

Hello everybody, Don't ignore this email! Last week a critical security bug was reported on our bug tracker. We fixed it and built debian packages for the four stable releases we currently support. The security flaw can cause a privilege escalation from OPAC users. It can be highly damaging, especially if your staff interface is accessible via login from everywhere without further security measures like IP restrictions in place. How to fix the problem? If you are using a debian-based system you should upgrade using the debian packages: % apt update % apt install koha-common If you are using an older version of Koha (<19.11) you should either upgrade to a newer version, or apply those two patches (they should apply on older versions as well): https://paste.debian.net/hidden/885fb5ec/ https://paste.debian.net/hidden/1184f523/ https://paste.debian.net/plainh/ae9f9f25 You can apply them using the following command: % wget "https://paste.debian.net/plainh/885fb5ec" -O 28929_1.patch % wget "https://paste.debian.net/plainh/1184f523" -O 28929_2.patch % wget "https://paste.debian.net/plainh/ae9f9f25" -O 28947.patch % patch -p1 -d /usr/share/koha/intranet/cgi-bin/ < /kohadevbox/koha/28929_1.patch % patch -p1 -d /usr/share/koha/opac/cgi-bin/ < /kohadevbox/koha/28929_2.patch % patch -d /usr/share/koha/opac/cgi-bin/opac/ < /kohadevbox/koha/28947.patch The two bugs are 28929 and 28947. As they contain information about how to recreate the vulnerability they will stay hidden two more days to let you upgrade your systems. Let us know if you have any questions! Regards, Jonathan

4 3