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

Re: [Koha-devel] [Koha] Where would I put the OpenLibrary ID in the MARC record
by Nigel Titley 15 Aug '23

15 Aug '23

Furthur on this and reading a bit more into MARC it looks like the information would go into MARC Field 024 with a source of 8. If there was a defined Standard Identifier for Openlibrary then the source would be 7 with the defined Standard Identifier for Openlibrary, but there isn't. I'm straying into Real Librarian Territory here and I'm starting to feel a little lost (I'm really just a programmer). If the person who wrote the code for fetching covers from Openlibrary is around I'd be grateful if they could confirm/deny what their code does (or even point me to where I could look it up myself). To this end I've copied in the Koha Development community. Or I may be barking up an entirely wrong tree. In which case feel free to say "Down boy, down". Nigel On 20/07/2023 23:20, Nigel Titley wrote: > Just to give an example of an OpenLibrary record that I created earlier > today > > https://openlibrary.org/books/OL49198571M/Analogue_Men#details > > If at all possible I'd like to be able to display the cover using the > OLID (OL49198571M) but I'm not sure where to put it. > > Thanks > > Nigel > > On 20/07/2023 22:43, Nigel Titley wrote: >> Gentlefolk >> >> I'm using the Openlibrary cover facility to display covers in my OPAC >> and it generally works very well (in the case where the cover doesn't >> exist in Openlibrary I scan and upload it). However, if the Biblio >> record doesn't have an ISBN or LCCN the cover lookup fails >> (obviously). Is there any way of recording the Openlibrary ID (OLID) >> in a Biblio record so that the cover lookup will work, even if there >> is no ISBN or LCCN? >> >> I've done a (fairly cursory) scan of the documentation but can't find >> and reference to where I should put the OLID so that Koha will look up >> the cover even if there is no ISBN or LCCN. Of course the facility may >> not exist, in which case I'd be grateful for confirmation from Someone >> Who Knows. >> >> Many thanks >> >> Nigel Titley >> >> _______________________________________________ >> >> Koha mailing list http://koha-community.org >> Koha(a)lists.katipo.co.nz >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > _______________________________________________ > > Koha mailing list http://koha-community.org > Koha(a)lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

3 15

Koha Community Newsletter: July 2023
by Koha Newsletter 29 Jul '23

29 Jul '23

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

koha-testing-docker missing koha-conf.xml
by Waylon Robertson 24 Jul '23

24 Jul '23

after doing ktd up, after configuring the database info etc in .env, I am getting koha-koha-1 | Running [PERL5LIB=/kohadevbox/koha:/kohadevbox/koha/lib:/kohadevbox/qa-test-tools perl /kohadevbox/misc4dev/setup_sip.pl --instance=emmaus]...koha-koha-1 | unable to locate Koha configuration file koha-conf.xml at /kohadevbox/koha/C4/Context.pm line 171. etc. What am i missing? Hopefully someone picks this up, as it's needed to be done before next week start. Waylon

4 4

Run Koha plugin method from CLI
by David Cook 21 Jul '23

21 Jul '23

Hi all, Do you ever want to run a Koha plugin method from the CLI? I know I sure do, so I raised this issue and attached a patch: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34335 I was able to upload a simple plugin and run the following: perl misc/run_koha_plugin.pl --class Koha::Plugin::Prosentient::CustomMethodPlugin --method awesome_method --params '{"msg": "this is awesome"}' This could be useful for manual tasks, cronjobs, or whatever really. 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

QA Tools change
by Renvoize, Martin 19 Jul '23

19 Jul '23

Hi all, tl;dr: Changed unit tests now run be default when using the QA test tools. --no-tests can be used to disable this functionality at runtime. The longer version. I recently submitted a merge request for the QA tool to enable running changed unit tests by default and it's just been merged. In the merge request we remove the --run-tests flag we used to require to run tests and instead replace it with a --no-tests option allowed users to skip the tests explicitly. I've also got another merge request open that's being worked on that attempts to identify related unit tests for a patchset and run those too. This will certainly be behind a --more-tests switch to start with whilst we refine the guesswork in identifying such tests. Martin

1 0

Helsinki KohaCon: SCHEDULE + REGISTRATION is here! The Perl and Koha conference'2023
by Perl Koha 17 Jul '23

17 Jul '23

🗓️ *The Schedule is complete* now: http://perlkohacon.fi/Schedule.html - 3 days of talks and 2 days for workshops, all in three streams of various Perl and Koha, many for developers, some for end-users and librarians. It's when the product meets the language, and users meet developers. - But *we need some more 5 minutes lightning talks*, so feel free to prepare something (tell us by form https://perlkohacon.fi/cft or by email) 🎉 REGISTRATION is open now: https://perlkohacon.fi/Registration.html - we have the conference free, *but registration is mandatory*. ‼️ *We need to know that you will come:* Some great social events (🚢!) are planned, thus ✍ PLEASE DO! ✈️🏨 We added hints about hotels, trip, Helsinki: http://perlkohacon.fi ... 🙏 share, and Welcome! -- Warm Regards, Conference Organizers Team Perl and Koha Conference in Helsinki, 2023. *YAPC::Europe* and *KohaCon* together: when Perl and Koha united once and forever. Schedule: https://perlkohacon.fi/Schedule.html Registration: https://perlkohacon.fi/Registration.html Find full info here: https://perlkohacon.fi Our social news channels for sharing our where is more convenient: - Telegram: http://t.me/PerlKohaCon - Mastodon: https://fosstodon.org/@perlkohacon - Twitter: http://twitter.com/PerlKohaCon - Facebook: http://facebook.com/PerlKohaCon - LinkedIn: http://linkedin.com/showcase/PerlKohaCon - Instagram: http://instagram.com/PerlKohaCon

1 0

Net::Netmask gotcha for ILS-DI:AuthorizedIPs
by David Cook 17 Jul '23

17 Jul '23

Hi all, I've recently noticed that Net::Netmask 2.000+ no longer supports abbreviated IPv4 netblocks (e.g. 216.240). If your Koha libraries have used this in their configurations, they'll no longer work. They need to use one of the supported methods like CIDR format: 216.240.0.0/16. Just FYI! 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

Call for news - Newsletter July 2023
by Koha Newsletter 14 Jul '23

14 Jul '23

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

Signoff please
by Marcel de Rooy 14 Jul '23

14 Jul '23

Hi, My patches below are waiting since May in the NSO queue. Could you have a look plese? Checked if they still apply just yet. 33837 Koha Architec m.de.rooy(a)rijksmuseum.nl Need --- enh Objects->filter_by_last_update: Does not allow time comparison 2023-05-26 33843 Koha Architec m.de.rooy(a)rijksmuseum.nl Need --- enh Use filter_by_last_update in Koha::Notice::Util 2023-05-26 33245 Koha Architec m.de.rooy(a)rijksmuseum.nl Need --- enh Add $patron->is_active 2023-05-30 33869 Koha Test Sui m.de.rooy(a)rijksmuseum.nl Need --- enh Move Matcher.t to db_dependent 2023-05-31 33870 Koha Test Sui m.de.rooy(a)rijksmuseum.nl Need --- enh Remove T::D::C from Sitemapper.t 2023-05-31 33871 Koha Command- m.de.rooy(a)rijksmuseum.nl Need --- enh Add where parameter to sitemap.pl 2023-05-31 Thanks ! Marcel

1 0

Tidy your code! And run the QA script!
by Tomas Cohen Arazi 14 Jul '23

14 Jul '23

Hi all. I've been trying to push as much as I can from the PQA queue, and I'm finding that most of the patches haven't been tidied up yet or have trivially caught issues (maybe not most, but a lot). For example, this is what I find when I run an up to date KTD and the code is not tidy: ``` kohadev-koha@kohadevbox:koha(master)$ qa -c 1 --run-tests testing 1 commit(s) (applied to e0df163 'fcf Bug 33933: Only show use restrict') Processing files before patches |========================>| 2 / 2 (100.00%) Processing files after patches |========================>| 2 / 2 (100.00%) WARN Koha/Recalls.pm WARN tidiness The file is less tidy than before (bad/messy lines before: 41, now: 42) WARN t/db_dependent/Koha/Recalls.t WARN tidiness The file is less tidy than before (bad/messy lines before: 100, now: 101) Processing additional checks OK! Running tests (1) * Proving /kohadevbox/koha/t/db_dependent/Koha/Recalls.t OK! ``` This is probably because they were submitted *before* we decided to enforce it on the QA tools, and it is understandable that, in some cases, it was not caught by a not-up-to-date QA command. As all testers and QA team members are encouraged to run the `qa` script before signing patches, I assume the underlying problem is that their KTD images are old and don't contain the latest QA tools version. So please make sure your KTD images or qa-test-tools clone is up to date. And run the tool, all the time! So, to sumarize: - Patch authors need to tidy the new blocks of code they introduce, or modify. - Instructions on setting perltidy on your favourite editor can be found on the wiki [1]. If your editor is missing, ask for help on IRC, the mailing list, or just use one from the documented ones. - QA members need to run the QA scripts. - You need to build the habit of pulling the latest KTD images every now and then. In case important things changed. And also run `docker system prune -a` (while KTD is running, so only the old images are cleared) - The RM will start failing patches that the QA script says have issues. Both authors and testers have the ability to run the script before submission. Every extra minute it takes to be gentle and fix the patch inline makes us have less time to push your next stuff! If you read all this, thank you! You are awesome! And I'm really glad to be working on this side-by-side with you! And I hope to share some beers and cookies in Helsinki soon! Cheers! [1] https://wiki.koha-community.org/wiki/Perltidy -- Tomás Cohen Arazi Theke Solutions (https://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

2 1