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

Failed to load external entity docbook.xsl when building Koha package
by Aleisha Amohia 02 Feb '23

02 Feb '23

Hello all We're running into an error when trying to build Koha debian packages. It's toward the end of the build-git-snapshot output and starts with this: xsltproc --output /build/koha-22.11.01.000+xxx+20230117170120.52134d4b/debian/tmp/debian/tmp_docbook/ \ /usr/share/xml/docbook/stylesheet/docbook-xsl-ns/manpages/docbook.xsl \ debian/docs/*.xml warning: failed to load external entity "/usr/share/xml/docbook/stylesheet/docbook-xsl-ns/manpages/docbook.xsl" cannot parse /usr/share/xml/docbook/stylesheet/docbook-xsl-ns/manpages/docbook.xsl debian/rules:17: recipe for target 'override_dh_auto_install' failed make[1]: *** [override_dh_auto_install] Error 4 We're using gitlab runners for these builds, which haven't changed since they were previously working last month. Has anyone seen this before and know what's causing it or what the fix is? Thanks! -- Aleisha Amohia (she/her) Koha Developer Catalyst IT - Expert Open Source Solutions www.catalyst.net.nz CONFIDENTIALITY NOTICE: This email is intended for the named recipients only. It may contain privileged, confidential or copyright information. If you are not the named recipient, any use, reliance upon, disclosure or copying of this email or its attachments is unauthorised. If you have received this email in error, please reply via email or call +64 4 499 2267.

4 6

Trouble for the Gitea project: forked to Forgejo
by Victor Grousset/tuxayo 01 Feb '23

01 Feb '23

Hi :) Thanks David Nind for sharing this info on the last dev meeting: > Use of Gitea: We use Gitea for git.koha-community.org. Gitea was "forked" and is now Forgejo[1] - see the links update and related links[2] (sounds eerily familiar 8-(.. ). The community needs to look at what to do next, such as whether to continue to use Gitea, update to Forgejo, do something else.... (David Nind) > [1] https://forgejo.org/ > [2] https://forgejo.org/2022-12-26-monthly-update Comments during the meeting: > forgejo is the 'good' one? > that's what it looks like ^^ > "After Gitea Ltd confirmed the takeover of the Gitea project on 30 October 2022, a group of people proposed that Codeberg e.V. should become the custodian of a fork of Gitea. The proposal was accepted 16 November 2022" - e.V. is a German thing actually More details: e. V. is the legal form for associations in Germany and Codeberg e. V. is known for their Gitea (well, now Forgejo) instance that became host to a decent number of libre projects in the last two years. (likely they moved away from GitHub and not wanted the not libre GitLab instance at GitLab.com (open-core)) Trivia: > Forgejo (pronounced /forˈd͡ʒe.jo/) is inspired by forĝejo, the Esperanto word for forge. 😃😃😃 I knew the name spelling looked familiar! Cheers, -- Victor Grousset/tuxayo

6 8

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

Koha Community Newsletter: January 2023
by Koha Newsletter 28 Jan '23

28 Jan '23

The Koha Community Newsletter for January 2023 is here: https://koha-community.org/koha-community-newsletter-january-2023/ 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

Still time to register for the Hackfest in Marseille !!!
by Paul Poulain 27 Jan '23

27 Jan '23

Hi guys, There are already more than 40 ppl registered for the hackfest (7 from Germany, 1 from USA, 1 from UK, the rest from France). Please come and join us for a week of work on Koh! There will be coffee, beer (after work ;) ), fun time translating, testing, documenting, developing. And, of course the legendary cheese lunch (on tuesday) Just drop me an email to say you want to come ! [and if you sent me an email and had no feedback, my bad, drop me an email again please] -- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries

1 0

Need to complete coding guidelines about when to use SQL and where.
by Victor Grousset/tuxayo 25 Jan '23

25 Jan '23

Hi :) We need some additions/changes to the SQL 8 guideline https://wiki.koha-community.org/wiki/Coding_Guidelines#SQL8:_SQL_code_in_.p… Like it allows implicitly SQL in .pm doesn't mention DBIC. In last meeting there was a discussion are here are some takeaways (https://ilbot3.kohaaloha.com/koha/2023-01-11#i_2343089) Add in the guidelines: No SQL by default in any place (in new code) except for database upgrades. But if it's not possible to do a query with the ORM or if it's much less readable or a performance bottleneck, then it should be done in a custom subroutine in the relevant DBIC schema class.[1][2] If SQL needed: SQL::Abstract syntax should be used over raw SQL in the /Koha namespace.[3] Syntax: https://metacpan.org/pod/SQL::Abstract::Classic#WHERE-CLAUSES What about command-line scripts? Should new ones/major changes use the ORM by default? Is that easy to access it from a script? SQL8: "SQL is also tolerated for reports" even new report? (assuming that still happens) [1] need more feedback on that last part. [2] Is DBIC schema class the right term? [3] why not everywhere? (except db upgrades) related to the upcoming question about scrips -- Victor Grousset/tuxayo

1 0

Next dev meeting 25 January: errata on hours
by Victor Grousset/tuxayo 25 Jan '23

25 Jan '23

I confused UTC with my local time! :o So it's this: Australia/Sydney Thu Jan 26 10:00:00 2023 AEDT NZ Thu Jan 26 12:00:00 2023 NZDT Pacific/Tahiti Wed Jan 25 13:00:00 2023 -10 America/Los_Angeles Wed Jan 25 15:00:00 2023 PST US/Central Wed Jan 25 17:00:00 2023 CST America/Lima Wed Jan 25 18:00:00 2023 -05 America/New_York Wed Jan 25 18:00:00 2023 EST UTC Wed Jan 25 23:00:00 2023 UTC -- Victor Grousset/tuxayo

1 0

perl modules to upload to debian.org
by Mason James 25 Jan '23

25 Jan '23

hi folks ping me if you have any perl modules that you want uploaded to debian.org ...perhaps excluding koha-common, at this stage :0)

1 0

Next dev meeting 25 January, 23:00 UTC (9 am east Australia, 11:00 Aotearoa/NZ, 12:00 Tahiti, 14:00 US west)
by Victor Grousset/tuxayo 24 Jan '23

24 Jan '23

Hi :) Careful with the International Date Line, it's the 26th for on the west side. https://wiki.koha-community.org/wiki/Next_IRC_meetings Calendar: https://koha-community.org/calendar/ Cheers, -- Victor Grousset/tuxayo

1 0

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