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

How to make self-referential URLs in Koha
by dcook＠prosentient.com.au 30 Jan '23

30 Jan '23

Hi all, With some recent code, I've been using creating self-referential URL in Koha using CGI->url(), and passing it as a value. With CGI, the URL is correct (ie starting with /cgi-bin/koha). With Plack, it's not, because the OPAC is mounted as "/opac". I worked around this by rewriting the self-referential URL in my code, but I was wondering if anyone else had any thoughts on this. I've noticed there are a few places in Koha where we use CGI->url() and I'm guessing we may have unexpected bugs in Plack-enabled Koha as a result. Of course, one workaround would be to have /opac and /intranet aliases or URL rewriting in Apache, so that the self-referential URLs created by Plack still end up resolving. I wonder if that's the easiest path forward. In the past, I have wondered if we could get rid of "/cgi-bin/koha" as a path prefix all together (especially as cgi-bin scares security tools), but it's so deeply embedded in Koha at this point that it seems a huge task to replace it. Anyway, just throwing that out there. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595

6 8

Re: [Koha-devel] [Koha] OAI-PMH harvester
by Arthur Suzuki 23 Jan '23

23 Jan '23

Hello there, If I may suggest a good harvester library, Catmandu may do the job pretty well. I've not used the OAI module but used it to harvest from a JSON source and transform to an UNIMARC file with pretty good success so far. It can export seamlessly to iso2709 or marcxml. https://metacpan.org/dist/Catmandu-OAI Best, Arthur On 2022-11-22 15:57, Mike D. wrote: > Hey. Hey, > I'm really glad to see the OAI-PMH harvester debate going on for Koha. > I > think if we choose a good external harvester with support, we can save > a > lot of energy and resources to implement related activities in the > system. > Shoveling the logs is only part of the story. The easy part. Since the > result of shoveling is a lot of records, most of the time we can't > avoid > post-processing, merging with the records in the local database. For > example, if you need to update records from a source where there are > millions of records, but there are hundreds of thousands in the local > database. Only a slice of that huge amount is relevant. If we design > the > processing workflow wrong, it will take unnecessarily long and burn > valuable resources. > I would hereby like to invite us to be in touch, to debate and share > our > experiences. Let's get this area moving towards a successful finish. > > Take care. > > Michal > > út 22. 11. 2022 v 15:13 odesílatel BOUIS Sonia > <sonia.bouis(a)univ-lyon3.fr> > napsal: > >> Hi, >> Thanks to David, Tomas, Michal and Michael for your replies. >> >> So we have decided to evaluate several external OAI-PMH client that >> could >> be used by Koha and to choose one in the end of January >> There a lot to do after that and we discussed about the background >> jobs >> and cronjobs seems to be appropriate. We thought that the settings in >> the >> koha intranet should be only to define URLs, SETs, or XSLT sheets (for >> example, to transform DC XML in MARCXML). >> >> We are only at the begining of the process 😊 >> >> Kind regards, >> Sonia >> >> ------------------------------ >> >> Message: 2 >> Date: Wed, 26 Oct 2022 10:37:49 +1100 >> From: "David Cook" <dcook(a)prosentient.com.au> >> To: "'Tomas Cohen Arazi'" <tomascohen(a)gmail.com>, "'BOUIS Sonia'" >> <sonia.bouis(a)univ-lyon3.fr> >> Cc: "'koha'" <koha(a)lists.katipo.co.nz>, "'koha-devel'" >> <koha-devel(a)lists.koha-community.org> >> Subject: Re: [Koha-devel] [Koha] OAI-PMH harvester >> Message-ID: <07af01d8e8ca$dfbddef0$9f399cd0$(a)prosentient.com.au> >> Content-Type: text/plain; charset="utf-8" >> >> Hi Sonia, >> >> >> >> I’m excited to hear that KohaLA would like to finance an OAI-PMH >> client in >> Koha! This functionality is always brewing in the back of my mind, >> since I >> first raised 10662 back in 2013. >> >> >> >> As Tomas says, I think that the background jobs are a key component >> for >> processing incoming OAI-PMH records. >> >> >> >> However, the ***missing component right now is the scheduling of the >> OAI-PMH harvesting tasks***, and I think this is where opinions get >> divided. Below, I’ll provide some history and opinions on Koha >> OAI-PMH. >> >> >> >> -- >> >> >> >> With 10662, the sponsored goal was for Koha library staff to schedule >> OAI-PMH harvests through the Web UI. However, Fridolin from BibLibre >> raised >> a point with me at Kohacon18 about how letting library staff control >> the >> timing of harvesting tasks could be a problem for support vendors. If >> too >> many libraries using the same public IP address tried to harvest from >> the >> same OAI-PMH repository, they could be rate limited or blocked. There >> could >> also be server load concerns. So there probably needs to be a balance >> between user configuration and system configuration. If I recall >> correctly, >> this is how DSpace’s OAI-PMH harvester works. Users set up targets and >> can >> start/stop harvests, but things like frequency and concurrency are >> handled >> by the system configuration. >> >> >> >> Based on my experience working on OAI-PMH on and off for nearly 10 >> years >> and as a Koha support vendor, I think my preference would be for >> sysadmins >> to handle most of the OAI-PMH harvesting details. >> >> >> >> The sponsorship for 10662 had certain requirements that many other >> libraries might not have, which is what made me think that it might be >> better to have an external client that connects to Koha. I thought >> maybe I >> could get the ordinary requirements pushed into Koha, and then handle >> extraordinary requirements externally. However, an external harvester >> won’t >> perform as fast as an internal harvester. (The compromise would be to >> write >> the harvester in such a way that people could provide different >> OAI-PMH >> harvester Perl modules that all stage records using the same core Koha >> modules.) >> >> >> >> Even then… the scheduling would depend on a library’s needs. Back in >> 2013, >> I had a Koha OAI-PMH harvester which worked as a cronjob. It would run >> each >> night. However, some libraries want to run OAI-PMH harvests as >> frequently >> as every 3 seconds. A cronjob’s smallest frequency is 60 seconds, so >> that >> wouldn’t work for that requirement. >> >> >> >> If a cronjob isn’t suitable, then I think you’d need a daemon created >> by a >> new command like “koha-oai --start <instance_name>”. It could read a >> configuration file and handle scheduling accordingly. With 10662, I >> used >> the POE module, because I knew it well and it has some timer tools for >> scheduling tasks. If I were to work on it again, I’d probably use >> Mojo::IOLoop instead these days, since Mojolicious is already part of >> Koha >> while POE is not. (That said, using modules like Mojo and POE are >> difficult, because they’re difficult to test using automation. That >> was one >> of the stumbling blocks with 10662. While the 10662 harvester worked >> very >> well, it was difficult to unit test. In hindsight, I should’ve written >> it >> in a way that was easier to unit test, but it had a lot of >> event-driven >> code which made things more difficult.) >> >> >> >> Another option would be to create a generic daemon for task scheduling >> in >> general (e.g. “koha-schedule”). Koha could use this for many things, >> but >> it’s a project in itself. >> >> >> >> -- >> >> >> >> The process of downloading OAI-PMH records and importing MARCXML into >> Koha >> is actually a fairly straightforward process. The difficulty is the >> task >> scheduling and management of tasks (and unit testing). >> >> >> >> I don’t know the answer that will make everyone happy. There’s lots of >> different ways of managing and scheduling the tasks. Based on my >> experience, I’d suggest targeting the simplest approach first, because >> complexity will make it less likely for the project to succeed. >> >> >> >> On that note, I’d be happy to test/QA any OAI-PMH harvester put >> forward. >> When I was writing OAI-PMH harvester patches, I found it really hard >> to get >> QA, so I’m happy to be that resource for someone else. I’ve spent a >> lot of >> time thinking about this topic, so happy to provide advice, warnings, >> emotional support 😉. >> >> >> >> 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 >> >> >> >> From: Koha-devel <koha-devel-bounces(a)lists.koha-community.org> On >> Behalf >> Of Tomas Cohen Arazi >> Sent: Wednesday, 26 October 2022 3:46 AM >> To: BOUIS Sonia <sonia.bouis(a)univ-lyon3.fr> >> Cc: koha <koha(a)lists.katipo.co.nz>; koha-devel < >> koha-devel(a)lists.koha-community.org> >> Subject: Re: [Koha-devel] [Koha] OAI-PMH harvester >> >> >> >> I think with background jobs we have most of the framework that is >> needed >> to deal with this within Koha. >> >> >> >> Best regards >> >> >> >> El mar, 25 oct 2022 7:08, BOUIS Sonia <sonia.bouis(a)univ-lyon3.fr >> <mailto: >> sonia.bouis(a)univ-lyon3.fr> > escribió: >> >> Hi, >> KohaLA would like to finance an OAI-PMH client in Koha but, we have >> questions that we want to raise to the community. >> There was already tries to propose an OAI-PMH client : >> - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10662 : >> it's >> an old project that doesnt seem compatible with the current version of >> Koha >> - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25905 : >> the >> scope is more to use an external OAI-PMH client and to connect it to >> Koha >> >> Our main question is about the way to handle this. Do you think that >> it's >> a better idea to use an external software or PERL routine and to find >> a way >> to connect it to Koha. Or would it be better to a new module in Koha >> from >> scratch and that Koha have his own OAI-PMH client. >> >> Please, let us hear your toughts about this projet. >> >> Kind regards >> >> Sonia >> >> Sonia BOUIS >> ------------------------------------------------------ >> Responsable du Service informatique documentaire Département d'Appui à >> la >> Recherche et aux Projets (DARP) Bibliothèques universitaires >> Université >> Jean Moulin Lyon 3 ADRESSE GÉOGRAPHIQUE > Manufacture des Tabacs | 6 >> cours >> Albert Thomas | LYON 8e ADRESSE POSTALE > Bibliothèque de la >> Manufacture | >> 1C avenue des Frères Lumière | CS 78242 - 69372 LYON CEDEX 08 >> >> Ligne directe : 33 (0)4 78 78 79 03 >> >> http://bu.univ-lyon3.fr<http://bu.univ-lyon3.fr/>| Suivez-nous > >> Facebook< >> https://www.facebook.com/bulyon3/> | >> Twitter<https://twitter.com/bulyon3>| >> Instagram<https://www.instagram.com/bu.lyon3/?hl=fr> >> >> _______________________________________________ >> >> Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz >> <mailto:Koha@lists.katipo.co.nz> >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >> >>

2 1

Koha releases are available 🎁
by Mason James 16 Jan '23

16 Jan '23

kia ora community, the latest Koha packages and tarballs are ready release notes are here... https://koha-community.org/koha-21-11-03-released https://koha-community.org/koha-21-05-11-released https://koha-community.org/koha-20-11-15-released https://koha-community.org/koha-19-11-26-released cheers, Mason

2 2

release-tools
by Tomas Cohen Arazi 28 Nov '22

28 Nov '22

Hi all this is for rmaints mostly, I've just added a new 'tarball' option to koha-release. Please review and comment if you'd prefer some other way to do this. Also, I think we should work on the release tools a bit so all parameters are named and have option switches to simplify the code. Objections? -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

2 2

Koha Community Newsletter: November 2022
by Koha Newsletter 28 Nov '22

28 Nov '22

The Koha Community Newsletter for November 2022 is here: https://koha-community.org/koha-community-newsletter-november-2022/ 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

Koha 22.11.00 Rosalie released
by Tomas Cohen Arazi 25 Nov '22

25 Nov '22

The Koha community is proud to announce the release of Koha 22.11.00. Koha 22.11.00 is a major release, that comes with many new features. It includes 13 new features, 351 enhancements, 3 security fixes, 551 bugfixes. The full release notes are available here: https://koha-community.org/koha-22-11-released/ <https://koha-community.org/koha-22-05-released/> Debian packages should be available soon Best regards -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

1 0

Next Friday: Patch testing session to help enhancements and bug fixes to be released
by Victor Grousset/tuxayo 25 Nov '22

25 Nov '22

Hi :) This is for the support providers that aren't used to testing patches and any provider that knows libraries where someone could be interested. To be forwarded to librarians, system librarians, educators, devs, sysadmins and other people that could be interested in contributing to Koha. Let's meet at any moment in the following timeframe: 13h-20h UTC&UK / 8h-15h US East / 5h-12h US West The place is https://visio.chapril.org/koha (the text chat can be opened with the 4th button at the bottom: 🗨️) Reminder of the modalities: The idea is to test patches to contribute to Koha. The biggest bottleneck for having more bugs fixes and enhancements is patch testing. Thus this call for getting together as Koha users. No need for particular skills, just basic Koha usage. You can come an leave at any moment, even for a short time it's possible to get simple stuff moving forward. We will use a VoIP call with chat tool to speak and eventually screenshare. It's possible to join without sound and only use chat. So if you are at the front desk and there are not much patrons you can still test patches ^^ So, whichever communication mode is the most convenient for you. No need to have a local Koha instance. Just with a web browser we can use the sandboxes [1] to have temporary Kohas to test most patches and do whatever we want without bad consequences. Here is a resource about how to test patches using sandboxes: https://wiki.koha-community.org/wiki/Sandboxes Cheers, [1] https://wiki.koha-community.org/wiki/Sandboxes -- Victor Grousset/tuxayo

1 0

Re: [Koha-devel] [Koha] OAI-PMH harvester
by BOUIS Sonia 22 Nov '22

22 Nov '22

Hi, Thanks to David, Tomas, Michal and Michael for your replies. So we have decided to evaluate several external OAI-PMH client that could be used by Koha and to choose one in the end of January There a lot to do after that and we discussed about the background jobs and cronjobs seems to be appropriate. We thought that the settings in the koha intranet should be only to define URLs, SETs, or XSLT sheets (for example, to transform DC XML in MARCXML). We are only at the begining of the process 😊 Kind regards, Sonia ------------------------------ Message: 2 Date: Wed, 26 Oct 2022 10:37:49 +1100 From: "David Cook" <dcook(a)prosentient.com.au> To: "'Tomas Cohen Arazi'" <tomascohen(a)gmail.com>, "'BOUIS Sonia'" <sonia.bouis(a)univ-lyon3.fr> Cc: "'koha'" <koha(a)lists.katipo.co.nz>, "'koha-devel'" <koha-devel(a)lists.koha-community.org> Subject: Re: [Koha-devel] [Koha] OAI-PMH harvester Message-ID: <07af01d8e8ca$dfbddef0$9f399cd0$(a)prosentient.com.au> Content-Type: text/plain; charset="utf-8" Hi Sonia, I’m excited to hear that KohaLA would like to finance an OAI-PMH client in Koha! This functionality is always brewing in the back of my mind, since I first raised 10662 back in 2013. As Tomas says, I think that the background jobs are a key component for processing incoming OAI-PMH records. However, the ***missing component right now is the scheduling of the OAI-PMH harvesting tasks***, and I think this is where opinions get divided. Below, I’ll provide some history and opinions on Koha OAI-PMH. -- With 10662, the sponsored goal was for Koha library staff to schedule OAI-PMH harvests through the Web UI. However, Fridolin from BibLibre raised a point with me at Kohacon18 about how letting library staff control the timing of harvesting tasks could be a problem for support vendors. If too many libraries using the same public IP address tried to harvest from the same OAI-PMH repository, they could be rate limited or blocked. There could also be server load concerns. So there probably needs to be a balance between user configuration and system configuration. If I recall correctly, this is how DSpace’s OAI-PMH harvester works. Users set up targets and can start/stop harvests, but things like frequency and concurrency are handled by the system configuration. Based on my experience working on OAI-PMH on and off for nearly 10 years and as a Koha support vendor, I think my preference would be for sysadmins to handle most of the OAI-PMH harvesting details. The sponsorship for 10662 had certain requirements that many other libraries might not have, which is what made me think that it might be better to have an external client that connects to Koha. I thought maybe I could get the ordinary requirements pushed into Koha, and then handle extraordinary requirements externally. However, an external harvester won’t perform as fast as an internal harvester. (The compromise would be to write the harvester in such a way that people could provide different OAI-PMH harvester Perl modules that all stage records using the same core Koha modules.) Even then… the scheduling would depend on a library’s needs. Back in 2013, I had a Koha OAI-PMH harvester which worked as a cronjob. It would run each night. However, some libraries want to run OAI-PMH harvests as frequently as every 3 seconds. A cronjob’s smallest frequency is 60 seconds, so that wouldn’t work for that requirement. If a cronjob isn’t suitable, then I think you’d need a daemon created by a new command like “koha-oai --start <instance_name>”. It could read a configuration file and handle scheduling accordingly. With 10662, I used the POE module, because I knew it well and it has some timer tools for scheduling tasks. If I were to work on it again, I’d probably use Mojo::IOLoop instead these days, since Mojolicious is already part of Koha while POE is not. (That said, using modules like Mojo and POE are difficult, because they’re difficult to test using automation. That was one of the stumbling blocks with 10662. While the 10662 harvester worked very well, it was difficult to unit test. In hindsight, I should’ve written it in a way that was easier to unit test, but it had a lot of event-driven code which made things more difficult.) Another option would be to create a generic daemon for task scheduling in general (e.g. “koha-schedule”). Koha could use this for many things, but it’s a project in itself. -- The process of downloading OAI-PMH records and importing MARCXML into Koha is actually a fairly straightforward process. The difficulty is the task scheduling and management of tasks (and unit testing). I don’t know the answer that will make everyone happy. There’s lots of different ways of managing and scheduling the tasks. Based on my experience, I’d suggest targeting the simplest approach first, because complexity will make it less likely for the project to succeed. On that note, I’d be happy to test/QA any OAI-PMH harvester put forward. When I was writing OAI-PMH harvester patches, I found it really hard to get QA, so I’m happy to be that resource for someone else. I’ve spent a lot of time thinking about this topic, so happy to provide advice, warnings, emotional support 😉. 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 From: Koha-devel <koha-devel-bounces(a)lists.koha-community.org> On Behalf Of Tomas Cohen Arazi Sent: Wednesday, 26 October 2022 3:46 AM To: BOUIS Sonia <sonia.bouis(a)univ-lyon3.fr> Cc: koha <koha(a)lists.katipo.co.nz>; koha-devel <koha-devel(a)lists.koha-community.org> Subject: Re: [Koha-devel] [Koha] OAI-PMH harvester I think with background jobs we have most of the framework that is needed to deal with this within Koha. Best regards El mar, 25 oct 2022 7:08, BOUIS Sonia <sonia.bouis(a)univ-lyon3.fr <mailto:sonia.bouis@univ-lyon3.fr> > escribió: Hi, KohaLA would like to finance an OAI-PMH client in Koha but, we have questions that we want to raise to the community. There was already tries to propose an OAI-PMH client : - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10662 : it's an old project that doesnt seem compatible with the current version of Koha - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25905 : the scope is more to use an external OAI-PMH client and to connect it to Koha Our main question is about the way to handle this. Do you think that it's a better idea to use an external software or PERL routine and to find a way to connect it to Koha. Or would it be better to a new module in Koha from scratch and that Koha have his own OAI-PMH client. Please, let us hear your toughts about this projet. Kind regards Sonia Sonia BOUIS ------------------------------------------------------ Responsable du Service informatique documentaire Département d'Appui à la Recherche et aux Projets (DARP) Bibliothèques universitaires Université Jean Moulin Lyon 3 ADRESSE GÉOGRAPHIQUE > Manufacture des Tabacs | 6 cours Albert Thomas | LYON 8e ADRESSE POSTALE > Bibliothèque de la Manufacture | 1C avenue des Frères Lumière | CS 78242 - 69372 LYON CEDEX 08 Ligne directe : 33 (0)4 78 78 79 03 http://bu.univ-lyon3.fr<http://bu.univ-lyon3.fr/>| Suivez-nous > Facebook<https://www.facebook.com/bulyon3/> | Twitter<https://twitter.com/bulyon3>| Instagram<https://www.instagram.com/bu.lyon3/?hl=fr> _______________________________________________ Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20221026/d…> ------------------------------ Subject: Digest Footer _______________________________________________ Koha-devel mailing list Koha-devel(a)lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : https://www.koha-community.org/ git : https://git.koha-community.org/ bugs : https://bugs.koha-community.org/ ------------------------------ End of Koha-devel Digest, Vol 203, Issue 15 *******************************************

1 0

translation issues fix script for Release Maintainers
by Arthur Suzuki 22 Nov '22

22 Nov '22

Hello Koha Folks, RMaint fellows, Struggling with translation issues at each release I've started to write a script to fix "most" small translation issues. The script is to be executed in Koha's source folder after merging the translation branch. Best, Arthur -- Arthur Suzuki, 🌈🏔️ Développeur @BibLibre

3 3

Some very sad news.
by Chris Cormack 22 Nov '22

22 Nov '22

Tēnā koutou It is with great sadness that I pass on to you all the news that Rosalie Blake has passed away. Rosalie was the Head Librarian at Horowhenua Library Trust when Koha was started and without her Koha would not exist. But more than this Rosalie was an amazing person, a librarian who always thought outside the box, a gifted potter, a friend to many and a beloved mother and grandmother. Details around the funeral and memorial note should be available tomorrow. But I am sure you will all join me holding Rosalie's family and friends in your thoughts. Tiwhatiwha te pō, tiwhatiwha te ao. Chris

8 8