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

Build a roadmap for 21.11
by Jonathan Druart 24 May '21

24 May '21

Hi developers! Yes, I know, 21.05 is not there yet, but we can start to think on which different topics we want to work on during the next cycle! It has been a bit abandoned during the end of the 21.05 cycle, but new topics appeared. I have started to list them on a new document - https://annuel.framapad.org/p/koha_21.11_roadmap There are 2 parts: * at the top: the new ones and those I retrieved from 21.05 * at the bottom: the ones from 21.05, if you need ideas. Move them to the top if you want to continue/resurrect them Add your names to the different topics you are willing to work on, and add new topics! Please keep in mind that your time is limited, no need to add your names everywhere :) And remove your names from the topics you won't/cannot work anymore. I added a bit of styling to make the document more friendly and readable. Note that during this next cycle I will spend my time on RM duties (if elected!) and help topics from the roadmap. Cheers, Jonathan

4 4

Koha logging out staff users
by dcook＠prosentient.com.au 20 May '21

20 May '21

Hi all, Does anyone have an issue where staff users are being logged out of Koha? The session timeout threshold is 1d, and AutoLocation and SessionRestrictionByIP are both disabled. I can't think of any reason why they're getting logged out. I also cannot reproduce the problem on my own workstation. So just curious if people have heard of this happening. I've heard it from 2 libraries now. 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

PUT /holds/:hold_id
by Tomas Cohen Arazi 19 May '21

19 May '21

Hi all, I wanted to gather some opinions about the mentioned route. We've made sure all routes have the additionalProperties: false setting, and some routes, like this one, don't have it. In the task to add it we noticed: 1. Theroute doesn't work as expected: the documented attributes don't match the coding guidelines (i.e. terminology hasn't been adjusted on the spec) but it did in the code, it just works because we don't set additionalProperties: false. TL;DR no one following the spec can use it. 2. The route seems to be wrong regarding how our RESTful implementation works in the rest of the routes: PUT should get a Koha::Hold object for updating it. Instead, it only 'accepts': 'priority', 'pickup_library_id' and 'suspended_until'. If we wanted to allow to selectively change those attributes, we should do a PATCH instead. 3. We already have individual routes for changing those things on the hold: PUT /holds/:hold_id/pickup_location PUT /holds/:hold_id/priority POST /holds/:hold_id/suspension The route itself doesn't work now. And any change will break things for people 'using' it. And tests pass only because the spec is loose. The options are: - 'Fix' the route so the attributes match the code, i.e. change the spec as bug 20006 intended to do. - Leave it as-is (probably documenting it should not be used). - Remove the route until we really need to implement that PUT for something. - Make it a PATCH route, in which we could add new attributes without breaking anyone's dev (besides the verb change, that should be advertised) - Fully implement a PUT, making it mandatory to send all the attributes (this would be an important breaking change). I would vote removing it, or making it a PATCH route. But I still don't see the use case in the UI, for the latter. Most places in Koha do atomic updates for priority, pickup location or hold suspension for which we clearly have routes already. Looking forward to your comments. -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

4 3

z3950 responding - accessing when using koha-testing-docker
by David Nind 14 May '21

14 May '21

Does anyone know how to get the Z3950Responder "working" using koha-testing-docker? The service is running and seems to be configured correctly (using koha-z3950-responder package commands) but I can't access/query using 127.0.0.1:2100 - I get *unable to connect* in my browser. Example query from the bug I am trying to test - *Bug 23887* <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23887> - Add support for client-specified sort order in Z3950Responder: http://127.0.01:2100/biblios?version=1.2&operation=searchRetrieve&query=mis… Other steps taken: changed search engine to Elasticsearch and reindexed. Any help would be appreciated! David Nind | david.nind(a)gmail.com PO Box 12367, Thorndon, Wellington, New Zealand 6144 m. +64 21 0537 847

1 0

Time to translate: string freeze to prepare Koha 19.11.18 has begun
by Victor Grousset/tuxayo 14 May '21

14 May '21

Hi, saluton, hola, bonjour, String freeze is into effect as of now for the 19.11.x maintenance branch. The release is scheduled for around the 24th/25th. **If you missed it the upcoming 21.05 release is translatable now.** 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. (We've had a recent significant case of that!) Happy translating, -- Victor Grousset/tuxayo

1 0

Time to translate: string freeze to prepare 20.11.06 release
by Fridolin SOMERS 14 May '21

14 May '21

Hi, String freeze is into effect today 🥶 The 20.11.x maintenance branch is preparing for 20.11.06 release 📦 The release is scheduled for around the 25. This means it's the right time to head over to the translation platform: https://translate.koha-community.org/projects/ Note that nl-NL translation for 20.11 was very low, I've ask them to be reinitialized with merge of files from 19.11. Translation is now around 70%. Keep in mind that translation must be done with priority on higher version 🔥 Happy translating 🌎🌍🌏 -- Fridolin SOMERS <fridolin.somers(a)biblibre.com> Software and system maintainer 🦄 BibLibre, France

1 0

Call for news - Newsletter May 2021
by Michael Kuhn 13 May '21

13 May '21

Hi I'm collecting news for the May 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. For events: * Please include dates for past events. If I can't find dates I may not add it. * Announcements for future events with dates to be announced are fine, e. g. Kohacon. * For past events, one month back is the cut-off. If you are working on an interesting project or development related to Koha, please let me know and I'll include it in the development section. Thank you! Michael Kuhn Editor, Koha Community Newsletter -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 · E mik(a)adminkuhn.ch · W www.adminkuhn.ch

1 0

master not handling errors correctly
by dcook＠prosentient.com.au 12 May '21

12 May '21

Hi all, I was working on https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28325, when I noticed some really weird things going on with Koha's HTTP errors. Look at http://localhost:8081/mojo. While Koha will say it's a 404, it's actually sending back a 200 response. That's not good. (With Bug 28325 I'm having even weirder problems where mounting a new PSGI app within an existing one seems to trigger both a 200 and a 404 within Plack but only return a 200. I don't have the time/energy to deal with that though.) 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

1 0

Help needed to test a bug, knowledge required: running automated tests
by Victor Grousset/tuxayo 11 May '21

11 May '21

Hi :) Here is a bug that I tested and checked for QA. Now a test from someone else is needed. Here is the ticket: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28200 Here is the test plan: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28200#c16 If you have any questions[1] I'll gladly guide you via email or chat (nickname: tuxayo) [1] including setting up a Koha environment from scratch. Cheers, -- Victor Grousset/tuxayo

1 0

API tests broken on master
by Jonathan Druart 11 May '21

11 May '21

Hi, Some of the REST API tests are failing on master, if it's blocking for you you can revert bug 28272 from your local branch. Cheers, Jonathan

1 1