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

Koha 23.11 - Release dates
by Tomas Cohen Arazi 18 Oct '23

18 Oct '23

Hi all, This are the release dates: * Oct 30th - "Soft" feature freeze, nothing big or with high risk of side-effects will be included into the final release if not marked as Passed QA * Nov 5 - "Hard" feature freeze, nothing considered as an improvement will be pushed if not marked as Passed QA * Nov 10th - String freeze, draft of release notes published * Nov 24th - Only bug fixes considered major, critical or blocker will be pushed * Nov 30th - Final release PM me if you have any comments. -- Tomás Cohen Arazi Theke Solutions (https://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

1 0

Next Development Meeting - 18 October 2023, 12:00 UTC
by David Nind 18 Oct '23

18 Oct '23

Apologies for the late notice, it slipped between the cracks 8-( No meeting was held last week for the original scheduled meeting (11 October). However, an informal meeting was held later the same day. A meeting is now scheduled for 18 October 2023, 12:00 UTC. For information on how to attend and the agenda, see: https://wiki.koha-community.org/wiki/Development_Meeting_18_October_2023 Everyone who as available at that time is more than welcome to attend! David Nind | david(a)davidnind.com New Zealand

1 0

Koha Roadmap Link?
by David Cook 16 Oct '23

16 Oct '23

Hi all, The other day folk were talking about the difficulty of keeping track of roadmap bugs, and it reminded me that I often don't know where to find the roadmap. Googling it will often wind up with really old roadmaps or conversations about roadmaps. I'm thinking we could pop a link to the roadmap up on https://dashboard.koha-community.org/ ? I don't know about everyone else, but that's the place I go most often when I want information about Koha. 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

Background jobs in plugins
by David Cook 16 Oct '23

16 Oct '23

Hi all, "Bug 30410 - Add a way for plugins to register background tasks" was pushed in Koha 22.05.00, but I can't figure out how to make it work. Tomas, do you have a plugin where this works? I've gone through the patches, and it looks like I should have it right, but nothing I'm doing is working. When I enqueue the job, background_jobs.pl says "Unknown job type 'plugin_blah_blah'" even though "plugin_blah_blah" exists in Koha::BackgroundJob->new->type_class_mapping and in my plugin background job's "job_type". When I click "View" on the job, I get the following error: "Template process failed: file error - background_jobs/plugin_blah_blah.inc: not found at /kohadevbox/koha/C4/Templates.pm line 127" I'll look next week at providing a simple plugin to illustrate the problem. Thanks, 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 6

Call for news - Newsletter October 2023
by Koha Newsletter 13 Oct '23

13 Oct '23

Hi I'm collecting news for the October 2023 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

Koha::Z3950Responder doesn't support authentication?
by David Cook 11 Oct '23

11 Oct '23

Hi all, Does anyone know if Koha::Z3950Responder supports authentication? As far as I know, it doesn't, so I've raised "Bug 35038 - Koha::Z3950Responder has no authentication" to flag that. Overall, I don't think I see the point of using z3950responder.pl in front of Zebra, but happy to be corrected. 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

Seeking comments on Bug 34745: ThingISBN broken
by Owen Leonard 11 Oct '23

11 Oct '23

I noticed recently that requests to LibraryThing's ThingISBN service are being blocked. Koha tries to access a url like this: https://www.librarything.com/api/thingISBN/0439139600 ...which opens fine in a browser, but triggers the response "WARNING: URL Request Failed 403 Forbidden" when Koha tries it. Koha is currently sending the user agent "libwww-perl/6.52" and if I use Firefox's developer tools to load the page with that set as a custom user agent I get a CloudFlare-generated "access denied" message. I see other CloudFlare customers complaining about this, so it may just be a default. Should we ask LibraryThing to change their configuration? Should we send a less obtrusive user agent with the request? -- Owen -- Web Developer Athens County Public Libraries (740) 737-6006 https://www.myacpl.org

3 3

Keycloak extension for using Koha as user storage backend
by David Cook 11 Oct '23

11 Oct '23

Hi all, Last year, I wrote a Keycloak extension for older Keycloak versions that uses Koha as a user storage backend. It allowed me to set up Keycloak as a shared IdP for Koha and other services, which allowed users to use their Koha credentials to log in. I'm almost finished writing an updated extension that works with the latest Keycloak 22+ (presumably Keycloak 20+ but I tested on Keycloak 22). I had to build a simple custom Docker image for Keycloak to include the extension, but I was able to get it to work in koha-testing-docker. If folk are interested in this work, I would be happy to look at sharing it. I have an increasing number of libraries who want an Identity Provider to provide SSO across Koha and other library services (like EBSCO's EDS), but they don't have an existing organisational Identity Provider. Keycloak fits well, and this extension makes it so easy for libraries and their users, since all the user management stays in Koha. 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

I suggest an update to last version of perltidy
by Zeno Tajoli 10 Oct '23

10 Oct '23

Hi all, I suggest everyone update their version of perltidy to the last one on CPAN. Why ? Because from 20230909 there is this option: Formatting a Limited Range of Lines A command --line-range-tidy=n1:n2 is available to pass just a selected range of lines to perltidy. It is quite useful with our decision on this topic: https://wiki.koha-community.org/wiki/Perltidy#Only_perltidy_modified_code Cheers Zeno Tajoli

1 0

Re: [Koha-devel] REST API and new defaults (Zeno Tajoli)
by Olli-Antti Hypernova 06 Oct '23

06 Oct '23

Good idea. Anything to disband the "SmartUI"-antipattern is good for me. We should add a new endpoint following established nomenclature. eg. PUT /biblios/123/merge/456 (PUT as it is modifying existing records) regarding b) We should separate Mojololicious from Plack, because Plack prevents the use of websockets and more advanced Mojolicious features. It is not such a biggie to implement. We can control two processes from the same koha-plack -script, so the CLI management API doesnt need to change either. On 6.10.2023 13.00, koha-devel-request(a)lists.koha-community.org wrote: > Message: 1 > Date: Fri, 6 Oct 2023 10:01:18 +0200 > From: Zeno Tajoli<ztajoli(a)gmail.com> > To: koha-devel<koha-devel(a)lists.koha-community.org> > Subject: [Koha-devel] REST API and new defaults > Message-ID: > <CACwhcG0R2BUPM+X0NSkiA4d7em2vzgyb0yuWrR-gGpx=rPOEdw(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Hi to all, > thinking about BZ 33036, the basic idea is to change a part of > ../cataloguing/merge.pl > to create a 'merge' verb inside Koha/REST/V1/Biblios.pm then use this > new verb in a new version of ./cataloguing/merge.pl > > But if we use REST inside standard scripts, I think we need to change > those defaults: > a)RESTBasicAuth: from 'Not enabled' to 'Enabled' > b)Plack as mandatory > > As I see also ERM needs those defaults > > So is it a direction to take? > > In .. ../cataloguing/merge.pl I insert a check on the environment. > > Cheers > Zeno Tajoli

3 3