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

Koha 19.11.16 released
by Victor Grousset/tuxayo 24 Mar '21

24 Mar '21

Hello! The Koha Community is happy to announce the release of Koha 19.11.16 The full release notes can be found at: https://koha-community.org/koha-19-11-16-released/ Debian packages will be available shortly. Thanks to everyone involved :) Cheers, -- Victor Grousset/tuxayo

1 0

Release of Koha 20.05.10
by Andrew Fuerste-Henry 23 Mar '21

23 Mar '21

Hi all! The Koha community is pleased to announce the release of Koha 20.05.10. This is a bugfix/maintenance release. It includes 1 enhancements, 40 bugfixes. Full release notes are available here: https://koha-community.org/koha-20-05-10-released/ Thanks! Andrew Andrew Fuerste-Henry Educator (he/him/his) ByWater Solutions bywatersolutions.com Phone:(888)900-8944 <(888)%20900-8944> What is Koha? <http://bywatersolutions.com/what-is-koha/>

1 0

OPAC search by 952$e
by Paul A 23 Mar '21

23 Mar '21

Is it possible in OPAC to search by acqsource 952$e? (no problem in MySQL, admin, reports) -- this email for OPAC query. Background: charitable library, trying to define donor fonds publicly. Disclaimer: using Koha 3.8.24 for ten years or more. I know (some of you might remember me) that we "should upgrade." We are not a lending, nor public library, use Koha very successfully at <https://opac.navalmarinearchive.com/> for cataloguing only, and cannot get later versions to work anywhere near as fast for OPAC / zebra searches. New summer students, IT specialty, coming in this year will try again... Best regards, and please stay safe, Paul

2 1

Time to translate: string freeze to prepare March release
by Fridolin SOMERS 19 Mar '21

19 Mar '21

Hi, String freeze is into effect the 15th. The 20.11.x maintenance branch is preparing for 20.11.04 release. The release is scheduled for around the 23rd. This means it's the right time to head over to the translation platform: https://translate.koha-community.org/projects/ Happy translating 🌎🌍🌏 -- Fridolin SOMERS <fridolin.somers(a)biblibre.com> Software and system maintainer 🦄 BibLibre, France

1 0

FW: [DISCUSS] The future of mod_perl
by dcook＠prosentient.com.au 18 Mar '21

18 Mar '21

Hi all, While the Koha community doesn’t work with mod_perl, I think that there are some of you that use mod_perl for Koha (or other Perl projects), so I thought that I’d share this here. At the moment, it seems like they have only 2 active PMC members. I only have 1 project that uses mod_perl, and it’s a project that will be easy to switch to starman, so I have no real “skin in the game” so to speak. But maybe one of you do. 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 From: Sander Striker <striker(a)apache.org> Sent: Thursday, 18 March 2021 6:41 AM To: dev(a)perl.apache.org; modperl(a)perl.apache.org Subject: [DISCUSS] The future of mod_perl Dear community members, As projects mature, they will naturally reach a point where activity reduces to a level such that the project is no longer sustainable. At Apache, projects reach this stage when there are not at least 3 active PMC members providing oversight. Projects that reach this stage are usually placed in the Attic [1] or absorbed by another Apache project willing to manage its releases. If you are interested in seeing mod_perl remain an active project, and are able to help maintain and provide oversight, please respond in this thread indicating that you are interested in performing the duties of a PMC member[2]. Cheers, Sander Striker Director, The Apache Software Foundation [1] https://attic.apache.org/ [2] https://www.apache.org/dev/pmc.html

1 0

Exporting patron related data in REST API
by Lari Taskula 18 Mar '21

18 Mar '21

Hi devs, I would appreciate your feedback on a couple of issues regarding Bug 20028 that attempts to exportall patron related personal data in one package. I'm having difficulties in choosing the best approach, so the help of fresh minds would be awesome. These are my questions. a) Code-wise, manually define what to include into the export, or automatically select all related objects with the help of DBIx relationships? 1. https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=79381&action=di… and https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20028#c11 2. https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20028#c21 I have written some proof of concept patches for the second approach of fetching related data by DBIx relationships. The idea behind this was that, assuming foreign keys are appropriately defined at database level, it would always return related data without us having to worry when a new patron-related database modification gets introduced. However, then we have to be sure we are not accidentally returning some unwanted columns. Explicitly defining what to include offers more straightforward control, but it's going to be a lot of objects (around 50, these are listed in the Bug), maintenance and the risk of data missing from the export after a database update. In terms of GDPR and good privacy practices in general it would not be nice if something was missing from the export. b) Terminology? What to do with REST API terminology for the response object (i.e. borrower vs patron)? A patron has many, many related objects, so how do we describe those objects in a way that satisfies our terminology requirements. We could use Koha-objects to_api(), or create a new to_public_api() for the purpose of public routes, but for some objects it's currently not possible (such as messaging preferences) because they are in development. Is it even in the scope of this Bug to worry about that? If we chose the manual path of explicitly defining what to export, like what was done in the original patch (see a.1.), terminology issues could perhaps be more easily tackled. If you have a moment, please check out the Bug, add some feedback and let me know which approach you'd prefer. Or perhaps you have even a better solution ;) Bug 20028: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20028 -- Lari Taskula CEO, Hypernova Oy PL 16 80101 Joensuu, Finland

2 1

Re: [Koha-devel] Automated testing Koha-Shibboleth integration
by dcook＠prosentient.com.au 17 Mar '21

17 Mar '21

I don’t have experience with CAS, but I’ve definitely used Keycloak for OpenID Connect and SAML 2. It actually looks like there is an unofficial CAS extension for Keycloak too: https://github.com/jacekkow/keycloak-protocol-cas. This is the Docker image I usually use for testing: https://hub.docker.com/r/jboss/keycloak/. 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 From: Tomas Cohen Arazi <tomascohen(a)theke.io> Sent: Wednesday, 17 March 2021 11:41 AM To: David Cook <dcook(a)prosentient.com.au> Cc: koha-devel <koha-devel(a)lists.koha-community.org>; Renvoize, Martin <martin.renvoize(a)ptfs-europe.com> Subject: Re: Automated testing Koha-Shibboleth integration it would be cool to have keycloak server to aid testers. This way CAS and Shibb bugs would move faster. El mar., 16 mar. 2021 21:26, <dcook(a)prosentient.com.au <mailto:dcook@prosentient.com.au> > escribió: Hi all, Jonathan’s comment about the possibility of a Koha-Shibboleth regression got me thinking (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27555#c3) When we do releases, are we testing the Koha-Shibboleth integration? I have some custom Shibboleth code for Koha, and when I’m testing it I use Keycloak (manually not automatically). I wonder if the community should run a Keycloak node for testing Koha’s Shibboleth integration. I’m curious what 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

1 0

Automated testing Koha-Shibboleth integration
by dcook＠prosentient.com.au 17 Mar '21

17 Mar '21

Hi all, Jonathan's comment about the possibility of a Koha-Shibboleth regression got me thinking (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27555#c3) When we do releases, are we testing the Koha-Shibboleth integration? I have some custom Shibboleth code for Koha, and when I'm testing it I use Keycloak (manually not automatically). I wonder if the community should run a Keycloak node for testing Koha's Shibboleth integration. I'm curious what 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

1 0

Time to translate: string freeze to prepare Koha 19.11.16 has begun
by Victor Grousset/tuxayo 15 Mar '21

15 Mar '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 23th. 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 and 20.11. Otherwise your work will be lost for future versions. Happy translating, -- Victor Grousset/tuxayo

1 0

Call for news - Newsletter March 2021
by Koha Newsletter 13 Mar '21

13 Mar '21

I'm collecting news for this month's newsletter. 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

1 0