From perlkohacon at gmail.com Fri Aug 4 06:01:19 2023 From: perlkohacon at gmail.com (Perl Koha) Date: Fri, 4 Aug 2023 07:01:19 +0300 Subject: [Koha-devel] Last Day to Register for Helsinki PerlKohaCon 2023: The Perl and Koha Conference! Message-ID: ‼️ TODAY is the LAST DAY for REGISTRATION: https://perlkohacon.fi/Registration.html *On-site visitors registration ends: *Friday, 4th August at noon (GMT+3) *Please register ASAP: *https://perlkohacon.fi/Registration.html For those waiting for "the last day" — that day is today, so please register now! *Registration is MANDATORY, but participation is FREE of charge.* This is required by officials, and due to the need for preparations, we can't extend the deadline. Unregistered individuals will not be accepted at the venue. For those who have already registered and are planning their days in Helsinki: we've updated the* Tourist info and hints *page. *🤗* 🙏 Please share this information and alert your colleagues. We look forward to welcoming you! -- 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomascohen at gmail.com Tue Aug 8 01:39:46 2023 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Mon, 7 Aug 2023 20:39:46 -0300 Subject: [Koha-devel] Koha versions 23.05.02, 22.11.08, 22.05.15 and 21.11.23 released Message-ID: The Koha community is proud to announce the latest releases of the current stable, oldstable, oldoldstable and lts versions of the software. This is a security and maintenance release on all branches, so please update at the earliest opportunity. As always, you can update using the already available packages, or download the release from https://download.koha-community.org Thank you very much to all release maintainers and the whole team involved in this release. Release notes for respective branches are available online now at: * https://koha-community.org/koha-23-05-02-released/ * https://koha-community.org/koha-22-11-08-released/ * https://koha-community.org/koha-22-05-15-released/ * https://koha-community.org/koha-21-11-23-released/ -- Tomás Cohen Arazi Theke Solutions (https://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From nigel at titley.com Tue Aug 8 11:10:45 2023 From: nigel at titley.com (Nigel Titley) Date: Tue, 8 Aug 2023 10:10:45 +0100 Subject: [Koha-devel] [Koha] Where would I put the OpenLibrary ID in the MARC record In-Reply-To: <065401d9bdc3$6eb2bc20$4c183460$@prosentient.com.au> References: <74d9d6e5-a4f9-63eb-0636-afe6360df2df@titley.com> <5d24759a-fd33-b16c-8d80-c7ffc052ea84@titley.com> <16c8a72a-76fa-bb30-3152-714ccbf450f1@titley.com> <065401d9bdc3$6eb2bc20$4c183460$@prosentient.com.au> Message-ID: David Sorry I only just got back to this. Your thinking seems to accord with my own. See comments below On 24/07/2023 01:11, David Cook wrote: > Hi Nigel, > > While it's been a while since I worked in a library myself, I've got the librarian degree, I've been working in the library world for nearly 20 years, and I've been working on Koha for over 10 years. In cases like this, the answer is often "it depends". > > I would be tempted to put the OpenLibrary ID into the 024$a but as you've noted there isn't an easy standard way to indicate that it's an OpenLibrary ID, which is quite important for a case like this. That certainly makes things tricky. > > You could send a request for an "openlibrary" code to be added to the official Standard Identifier Source Codes list: https://www.loc.gov/standards/sourcelist/index.html#maintenance . Honestly, I'm a little surprised there isn't already an entry for it there. I'm sure they'd approve a request for it. I think this might be the proper way forward and I'll kick off a request > > Now here's where "it depends" comes in the most. Are you going to exchange your MARC records with other systems or just use them locally? If it's just locally, you could cheat and use a 024$2 of "openlibrary". Of course, you'd still need to write code to look for a 024$a with a 024$2 of "openlibrary". It would be fine if you kept that code local to your Koha, but the Koha community might not accept it upstream. Having worked for many, many years in the opensource community I'd be very wary of taking this route. Local code changes that aren't folded back into the mainstream always end up going down the rat hole of non-maintainability. > Another option could be to use a 024$2 of "uri" and store the whole OpenLibrary URI like https://openlibrary.org/books/OL49198571M/Analogue_Men. The code could look for URIs with a hostname of "openlibrary.org" and then extract the ID from the URI. There's a growing usage of URIs for identifiers in the MARC world (long story why). You often see these as $0 subfields: https://www.loc.gov/marc/bibliographic/ecbdcntf.html. This would fit within the rules for MARC, but the downside is it would require you to write new code. It's also still arguably unconventional. This is a possibility and it's certainly a route I could go. Writing code isn't out of the question. I've got a Javascript manual glaring at me as I write. > As Jonathan pointed out, Koha only uses the ISBN to get OpenLibrary covers, although it looks like the OpenLibrary API has some options available for things like the OpenLibrary ID. Extending that API usage by Koha would probably involve Javascript, Template Toolkit changes, and maybe Perl changes. Keeping custom code local can be a bit of a headache in the long-run though, as then you can't rely on the regular releases from the Koha community without doing a fair bit of extra work. Agreed > If you're running Koha 23.05+, you could look at writing a Koha plugin, which uses the new "opac_cover_images" hook[1]. This would involve some short-term work, but it would let you implement what you need. Unfortunately I'm stuck with 22.05.13.000 for the moment as the server is shared with a sympa server which has a clash of libraries with koha. I'm getting to the end of my tether with sympa, however, and I may migrate back to mailman. > Going back to "it depends", in the library world we like to follow standards... until they don't work for us. Then we have local policies. Every library has their own way of doing things. (Another thing to notice with MARC is that when you encounter the number "9", it typically stands for a local field/subfield. Koha uses some of these fields/subfields for its own local purposes, and you can always do the same. The limit is just that "9" only makes sense for your library. You could always use a 024$9 of "openlibrary" along with a Koha plugin to achieve your goal. It wouldn't be following the library standards 100% but it's the kind of thing that does get done in the library world. Does that make sense? I really like to stay with standards if possible. I'll go the route of requesting Openlibrary be added to the SISC list and if that gets turned down I'll reconsider options. Many thanks for your help Nigel > > [1] > https://wiki.koha-community.org/wiki/Koha_Plugin_Hooks > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32680 > > > 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 > > -----Original Message----- > From: Koha-devel On Behalf Of Nigel Titley > Sent: Friday, 21 July 2023 11:06 PM > To: Jonathan Druart > Cc: koha at lists.katipo.co.nz; koha-devel > Subject: Re: [Koha-devel] [Koha] Where would I put the OpenLibrary ID in the MARC record > > Understood. > > I'm sure that a Real Librarian (tm) will answer at some point. > > Thanks anyway > > Nigel > > On 21/07/2023 13:20, Jonathan Druart wrote: >> No idea, I'm really just a programmer ;) >> >> Le ven. 21 juil. 2023 à 14:06, Nigel Titley a écrit : >>> >>> Thanks for the response... makes sense to use the ISBN and it >>> explains the observed behaviour. >>> >>> I've had a look at the code. One of these days I'll blow the dust off >>> my JS manuals and see if I can do something to extend the code (JS >>> isn't my favourite language and I've probably not written any for about 15 years). >>> >>> Is my supposition about where it would go in the MARC record correct? >>> >>> Thanks >>> >>> Nigel >>> >>> On 21/07/2023 12:29, Jonathan Druart wrote: >>>> Looks like it's only using the ISBN. The code is in >>>> koha-tmpl/opac-tmpl/bootstrap/js/openlibrary.js >>>> >>>> https://gitlab.com/koha-community/Koha/-/blob/master/koha-tmpl/opac- >>>> tmpl/bootstrap/js/openlibrary.js#L19 >>>> >>>> and opac-results: >>>> 899 [% IF OpenLibraryCovers >>>> %]KOHA.OpenLibrary.GetCoverFromIsbn();[% END %] >>>> >>>> >>>> Le ven. 21 juil. 2023 à 13:03, Nigel Titley a écrit : >>>>> >>>>> 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 at lists.katipo.co.nz >>>>>>> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >>>>>> _______________________________________________ >>>>>> >>>>>> Koha mailing list http://koha-community.org >>>>>> Koha at lists.katipo.co.nz >>>>>> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >>>>> _______________________________________________ >>>>> Koha-devel mailing list >>>>> Koha-devel at lists.koha-community.org >>>>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-deve >>>>> l website : https://www.koha-community.org/ git : >>>>> https://git.koha-community.org/ bugs : >>>>> https://bugs.koha-community.org/ >>>> _______________________________________________ >>>> >>>> Koha mailing list http://koha-community.org Koha at lists.katipo.co.nz >>>> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >> _______________________________________________ >> >> Koha mailing list http://koha-community.org Koha at lists.katipo.co.nz >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > From nigel at titley.com Tue Aug 8 11:58:25 2023 From: nigel at titley.com (Nigel Titley) Date: Tue, 8 Aug 2023 10:58:25 +0100 Subject: [Koha-devel] [Koha] Where would I put the OpenLibrary ID in the MARC record In-Reply-To: <065401d9bdc3$6eb2bc20$4c183460$@prosentient.com.au> References: <74d9d6e5-a4f9-63eb-0636-afe6360df2df@titley.com> <5d24759a-fd33-b16c-8d80-c7ffc052ea84@titley.com> <16c8a72a-76fa-bb30-3152-714ccbf450f1@titley.com> <065401d9bdc3$6eb2bc20$4c183460$@prosentient.com.au> Message-ID: <741a3bc8-a847-d6a9-a783-cfce261af3fd@titley.com> On 24/07/2023 01:11, David Cook wrote: > You could send a request for an "openlibrary" code to be added to the official Standard Identifier Source Codes list: https://www.loc.gov/standards/sourcelist/index.html#maintenance . Honestly, I'm a little surprised there isn't already an entry for it there. I'm sure they'd approve a request for it. I've put in a request to the LOC. We'll see if anything comes of it. They may request (I would do so in their place) that the request comes from the Open Library itself in which case I'll have to chase that route first. Fingers crossed. Nigel From nigel at titley.com Tue Aug 8 12:28:25 2023 From: nigel at titley.com (Nigel Titley) Date: Tue, 8 Aug 2023 11:28:25 +0100 Subject: [Koha-devel] [Koha] Where would I put the OpenLibrary ID in the MARC record In-Reply-To: <065401d9bdc3$6eb2bc20$4c183460$@prosentient.com.au> References: <74d9d6e5-a4f9-63eb-0636-afe6360df2df@titley.com> <5d24759a-fd33-b16c-8d80-c7ffc052ea84@titley.com> <16c8a72a-76fa-bb30-3152-714ccbf450f1@titley.com> <065401d9bdc3$6eb2bc20$4c183460$@prosentient.com.au> Message-ID: David Sorry I only just got back to this. Your thinking seems to accord with my own. See comments below On 24/07/2023 01:11, David Cook wrote: > Hi Nigel, > > While it's been a while since I worked in a library myself, I've got the librarian degree, I've been working in the library world for nearly 20 years, and I've been working on Koha for over 10 years. In cases like this, the answer is often "it depends". > > I would be tempted to put the OpenLibrary ID into the 024$a but as you've noted there isn't an easy standard way to indicate that it's an OpenLibrary ID, which is quite important for a case like this. That certainly makes things tricky. > > You could send a request for an "openlibrary" code to be added to the official Standard Identifier Source Codes list: https://www.loc.gov/standards/sourcelist/index.html#maintenance . Honestly, I'm a little surprised there isn't already an entry for it there. I'm sure they'd approve a request for it. I think this might be the proper way forward and I'll kick off a request > > Now here's where "it depends" comes in the most. Are you going to exchange your MARC records with other systems or just use them locally? If it's just locally, you could cheat and use a 024$2 of "openlibrary". Of course, you'd still need to write code to look for a 024$a with a 024$2 of "openlibrary". It would be fine if you kept that code local to your Koha, but the Koha community might not accept it upstream. Having worked for many, many years in the opensource community I'd be very wary of taking this route. Local code changes that aren't folded back into the mainstream always end up going down the rat hole of non-maintainability. > Another option could be to use a 024$2 of "uri" and store the whole OpenLibrary URI like https://openlibrary.org/books/OL49198571M/Analogue_Men. The code could look for URIs with a hostname of "openlibrary.org" and then extract the ID from the URI. There's a growing usage of URIs for identifiers in the MARC world (long story why). You often see these as $0 subfields: https://www.loc.gov/marc/bibliographic/ecbdcntf.html. This would fit within the rules for MARC, but the downside is it would require you to write new code. It's also still arguably unconventional. This is a possibility and it's certainly a route I could go. Writing code isn't out of the question. I've got a Javascript manual glaring at me as I write. > As Jonathan pointed out, Koha only uses the ISBN to get OpenLibrary covers, although it looks like the OpenLibrary API has some options available for things like the OpenLibrary ID. Extending that API usage by Koha would probably involve Javascript, Template Toolkit changes, and maybe Perl changes. Keeping custom code local can be a bit of a headache in the long-run though, as then you can't rely on the regular releases from the Koha community without doing a fair bit of extra work. Agreed > If you're running Koha 23.05+, you could look at writing a Koha plugin, which uses the new "opac_cover_images" hook[1]. This would involve some short-term work, but it would let you implement what you need. Unfortunately I'm stuck with 22.05.13.000 for the moment as the server is shared with a sympa server which has a clash of libraries with koha. I'm getting to the end of my tether with sympa, however, and I may migrate back to mailman. > Going back to "it depends", in the library world we like to follow standards... until they don't work for us. Then we have local policies. Every library has their own way of doing things. (Another thing to notice with MARC is that when you encounter the number "9", it typically stands for a local field/subfield. Koha uses some of these fields/subfields for its own local purposes, and you can always do the same. The limit is just that "9" only makes sense for your library. You could always use a 024$9 of "openlibrary" along with a Koha plugin to achieve your goal. It wouldn't be following the library standards 100% but it's the kind of thing that does get done in the library world. Does that make sense? I really like to stay with standards if possible. I'll go the route of requesting Openlibrary be added to the SISC list and if that gets turned down I'll reconsider options. Many thanks for your help Nigel > > [1] > https://wiki.koha-community.org/wiki/Koha_Plugin_Hooks > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32680 > > > 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 > > -----Original Message----- > From: Koha-devel On Behalf Of Nigel Titley > Sent: Friday, 21 July 2023 11:06 PM > To: Jonathan Druart > Cc: koha at lists.katipo.co.nz; koha-devel > Subject: Re: [Koha-devel] [Koha] Where would I put the OpenLibrary ID in the MARC record > > Understood. > > I'm sure that a Real Librarian (tm) will answer at some point. > > Thanks anyway > > Nigel > > On 21/07/2023 13:20, Jonathan Druart wrote: >> No idea, I'm really just a programmer ;) >> >> Le ven. 21 juil. 2023 à 14:06, Nigel Titley a écrit : >>> >>> Thanks for the response... makes sense to use the ISBN and it >>> explains the observed behaviour. >>> >>> I've had a look at the code. One of these days I'll blow the dust off >>> my JS manuals and see if I can do something to extend the code (JS >>> isn't my favourite language and I've probably not written any for about 15 years). >>> >>> Is my supposition about where it would go in the MARC record correct? >>> >>> Thanks >>> >>> Nigel >>> >>> On 21/07/2023 12:29, Jonathan Druart wrote: >>>> Looks like it's only using the ISBN. The code is in >>>> koha-tmpl/opac-tmpl/bootstrap/js/openlibrary.js >>>> >>>> https://gitlab.com/koha-community/Koha/-/blob/master/koha-tmpl/opac- >>>> tmpl/bootstrap/js/openlibrary.js#L19 >>>> >>>> and opac-results: >>>> 899 [% IF OpenLibraryCovers >>>> %]KOHA.OpenLibrary.GetCoverFromIsbn();[% END %] >>>> >>>> >>>> Le ven. 21 juil. 2023 à 13:03, Nigel Titley a écrit : >>>>> >>>>> 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 at lists.katipo.co.nz >>>>>>> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >>>>>> _______________________________________________ >>>>>> >>>>>> Koha mailing list http://koha-community.org >>>>>> Koha at lists.katipo.co.nz >>>>>> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >>>>> _______________________________________________ >>>>> Koha-devel mailing list >>>>> Koha-devel at lists.koha-community.org >>>>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-deve >>>>> l website : https://www.koha-community.org/ git : >>>>> https://git.koha-community.org/ bugs : >>>>> https://bugs.koha-community.org/ >>>> _______________________________________________ >>>> >>>> Koha mailing list http://koha-community.org Koha at lists.katipo.co.nz >>>> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >> _______________________________________________ >> >> Koha mailing list http://koha-community.org Koha at lists.katipo.co.nz >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > From nigel at titley.com Tue Aug 8 12:29:02 2023 From: nigel at titley.com (Nigel Titley) Date: Tue, 8 Aug 2023 11:29:02 +0100 Subject: [Koha-devel] [Koha] Where would I put the OpenLibrary ID in the MARC record In-Reply-To: <065401d9bdc3$6eb2bc20$4c183460$@prosentient.com.au> References: <74d9d6e5-a4f9-63eb-0636-afe6360df2df@titley.com> <5d24759a-fd33-b16c-8d80-c7ffc052ea84@titley.com> <16c8a72a-76fa-bb30-3152-714ccbf450f1@titley.com> <065401d9bdc3$6eb2bc20$4c183460$@prosentient.com.au> Message-ID: <66205af3-6faa-e536-1001-44b4f928ce34@titley.com> On 24/07/2023 01:11, David Cook wrote: > You could send a request for an "openlibrary" code to be added to the official Standard Identifier Source Codes list: https://www.loc.gov/standards/sourcelist/index.html#maintenance . Honestly, I'm a little surprised there isn't already an entry for it there. I'm sure they'd approve a request for it. I've put in a request to the LOC. We'll see if anything comes of it. They may request (I would do so in their place) that the request comes from the Open Library itself in which case I'll have to chase that route first. Fingers crossed. Nigel From alexbuckley at catalyst.net.nz Thu Aug 10 07:34:26 2023 From: alexbuckley at catalyst.net.nz (Alex Buckley) Date: Thu, 10 Aug 2023 17:34:26 +1200 Subject: [Koha-devel] Query about a New Book display plugin/widget for the OpacNavRight HTML customisation Message-ID: <54805a13-8937-a6e0-e1ce-825f433c46fd@catalyst.net.nz> Hi everyone, I have a query from one of our partner libraries. Does anyone know of an existing New Book display that could be displayed nicely in the OpacNavRight HTML customisation? This library can't utilise their OpacMainUserBlock HTML customisation as it is already full of content. That being the case we believe the Koha Coverflow plugin may not be the best option in a long narrow area like the OpacNavRight. Any information, or examples, would be gratefully received. I hope to see some of you next week in Helsinki at KohaCon. Kind regards, Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: From nigel at titley.com Thu Aug 10 10:39:33 2023 From: nigel at titley.com (Nigel Titley) Date: Thu, 10 Aug 2023 09:39:33 +0100 Subject: [Koha-devel] [Koha] Where would I put the OpenLibrary ID in the MARC record In-Reply-To: <741a3bc8-a847-d6a9-a783-cfce261af3fd@titley.com> References: <74d9d6e5-a4f9-63eb-0636-afe6360df2df@titley.com> <5d24759a-fd33-b16c-8d80-c7ffc052ea84@titley.com> <16c8a72a-76fa-bb30-3152-714ccbf450f1@titley.com> <065401d9bdc3$6eb2bc20$4c183460$@prosentient.com.au> <741a3bc8-a847-d6a9-a783-cfce261af3fd@titley.com> Message-ID: <7a8efa31-11a5-44ee-068f-3bb31100986d@titley.com> On 08/08/2023 10:58, Nigel Titley wrote: > > > On 24/07/2023 01:11, David Cook wrote: > >> You could send a request for an "openlibrary" code to be added to the >> official Standard Identifier Source Codes list: >> https://www.loc.gov/standards/sourcelist/index.html#maintenance . >> Honestly, I'm a little surprised there isn't already an entry for it >> there. I'm sure they'd approve a request for it. > > I've put in a request to the LOC. We'll see if anything comes of it. > They may request (I would do so in their place) that the request comes > from the Open Library itself in which case I'll have to chase that route > first. Well, to my surprise LOC got back to me today and said they had added Open Library to the SISC list. https://loc.gov/marc/relators/tn230808src.html So we now have a standardised way to add OLIDs to a MARC record 024 7 _ | $2 openlib | $a And that means I can have a look at adding OLIDs to the cover art retrieval from Open Library... which means dusting off my... erk... javascript. Which means sorting out sympa so I can get Koha up to date... Nigel From dcook at prosentient.com.au Fri Aug 11 01:07:27 2023 From: dcook at prosentient.com.au (David Cook) Date: Fri, 11 Aug 2023 09:07:27 +1000 Subject: [Koha-devel] [Koha] Where would I put the OpenLibrary ID in the MARC record In-Reply-To: <7a8efa31-11a5-44ee-068f-3bb31100986d@titley.com> References: <74d9d6e5-a4f9-63eb-0636-afe6360df2df@titley.com> <5d24759a-fd33-b16c-8d80-c7ffc052ea84@titley.com> <16c8a72a-76fa-bb30-3152-714ccbf450f1@titley.com> <065401d9bdc3$6eb2bc20$4c183460$@prosentient.com.au> <741a3bc8-a847-d6a9-a783-cfce261af3fd@titley.com> <7a8efa31-11a5-44ee-068f-3bb31100986d@titley.com> Message-ID: <002601d9cbdf$75fa1710$61ee4530$@prosentient.com.au> That's great news, Nigel! I'm really happy that worked out. Have you looked at koha-testing-docker? https://gitlab.com/koha-community/koha-testing-docker You could do the development work on there and then wait/hope for it to flow down to your version? 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 -----Original Message----- From: Koha-devel On Behalf Of Nigel Titley Sent: Thursday, 10 August 2023 6:40 PM To: koha-devel at lists.koha-community.org Subject: Re: [Koha-devel] [Koha] Where would I put the OpenLibrary ID in the MARC record On 08/08/2023 10:58, Nigel Titley wrote: > > > On 24/07/2023 01:11, David Cook wrote: > >> You could send a request for an "openlibrary" code to be added to the >> official Standard Identifier Source Codes list: >> https://www.loc.gov/standards/sourcelist/index.html#maintenance . >> Honestly, I'm a little surprised there isn't already an entry for it >> there. I'm sure they'd approve a request for it. > > I've put in a request to the LOC. We'll see if anything comes of it. > They may request (I would do so in their place) that the request comes > from the Open Library itself in which case I'll have to chase that > route first. Well, to my surprise LOC got back to me today and said they had added Open Library to the SISC list. https://loc.gov/marc/relators/tn230808src.html So we now have a standardised way to add OLIDs to a MARC record 024 7 _ | $2 openlib | $a And that means I can have a look at adding OLIDs to the cover art retrieval from Open Library... which means dusting off my... erk... javascript. Which means sorting out sympa so I can get Koha up to date... Nigel _______________________________________________ Koha-devel mailing list Koha-devel at 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/ From nigel at titley.com Fri Aug 11 12:01:07 2023 From: nigel at titley.com (Nigel Titley) Date: Fri, 11 Aug 2023 11:01:07 +0100 Subject: [Koha-devel] [Koha] Where would I put the OpenLibrary ID in the MARC record In-Reply-To: <002601d9cbdf$75fa1710$61ee4530$@prosentient.com.au> References: <74d9d6e5-a4f9-63eb-0636-afe6360df2df@titley.com> <5d24759a-fd33-b16c-8d80-c7ffc052ea84@titley.com> <16c8a72a-76fa-bb30-3152-714ccbf450f1@titley.com> <065401d9bdc3$6eb2bc20$4c183460$@prosentient.com.au> <741a3bc8-a847-d6a9-a783-cfce261af3fd@titley.com> <7a8efa31-11a5-44ee-068f-3bb31100986d@titley.com> <002601d9cbdf$75fa1710$61ee4530$@prosentient.com.au> Message-ID: And that, as if by magic, answers what was to be my next question... the koha-testing-docker instructions look comprehensive and I can try them out on my desktop, which seems to meet the requirements. My son, when I was discussing the project with him, said "you should do this in a docker container" and as usual he was right. I presume that once/if I've got it working there's a submission process to get updates back to the main Koha branch. All the best Nigel On 11/08/2023 00:07, David Cook wrote: > That's great news, Nigel! I'm really happy that worked out. > > Have you looked at koha-testing-docker? https://gitlab.com/koha-community/koha-testing-docker > > You could do the development work on there and then wait/hope for it to flow down to your version? > > 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 > > -----Original Message----- > From: Koha-devel On Behalf Of Nigel Titley > Sent: Thursday, 10 August 2023 6:40 PM > To: koha-devel at lists.koha-community.org > Subject: Re: [Koha-devel] [Koha] Where would I put the OpenLibrary ID in the MARC record > > > > On 08/08/2023 10:58, Nigel Titley wrote: >> >> >> On 24/07/2023 01:11, David Cook wrote: >> >>> You could send a request for an "openlibrary" code to be added to the >>> official Standard Identifier Source Codes list: >>> https://www.loc.gov/standards/sourcelist/index.html#maintenance . >>> Honestly, I'm a little surprised there isn't already an entry for it >>> there. I'm sure they'd approve a request for it. >> >> I've put in a request to the LOC. We'll see if anything comes of it. >> They may request (I would do so in their place) that the request comes >> from the Open Library itself in which case I'll have to chase that >> route first. > > Well, to my surprise LOC got back to me today and said they had added Open Library to the SISC list. > > https://loc.gov/marc/relators/tn230808src.html > > So we now have a standardised way to add OLIDs to a MARC record > > 024 7 _ | $2 openlib | $a > > And that means I can have a look at adding OLIDs to the cover art retrieval from Open Library... which means dusting off my... erk... > javascript. Which means sorting out sympa so I can get Koha up to date... > > Nigel > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > From kohanews at gmail.com Sun Aug 13 15:25:25 2023 From: kohanews at gmail.com (Koha Newsletter) Date: Sun, 13 Aug 2023 15:25:25 +0200 Subject: [Koha-devel] Call for news - Newsletter August 2023 Message-ID: Hi I'm collecting news for the August 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Mon Aug 14 03:18:10 2023 From: dcook at prosentient.com.au (David Cook) Date: Mon, 14 Aug 2023 11:18:10 +1000 Subject: [Koha-devel] [Koha] Where would I put the OpenLibrary ID in the MARC record In-Reply-To: References: <74d9d6e5-a4f9-63eb-0636-afe6360df2df@titley.com> <5d24759a-fd33-b16c-8d80-c7ffc052ea84@titley.com> <16c8a72a-76fa-bb30-3152-714ccbf450f1@titley.com> <065401d9bdc3$6eb2bc20$4c183460$@prosentient.com.au> <741a3bc8-a847-d6a9-a783-cfce261af3fd@titley.com> <7a8efa31-11a5-44ee-068f-3bb31100986d@titley.com> <002601d9cbdf$75fa1710$61ee4530$@prosentient.com.au> Message-ID: <007301d9ce4d$35dbef30$a193cd90$@prosentient.com.au> Hi Nigel, "I'm going to do this in a docker container" is what I say for most of my code projects (at home and the office). So long as you're not working with SystemD, it generally makes everything easier. I think this wiki page might describe the process best: https://wiki.koha-community.org/wiki/Development_workflow And for the practical aspect of submitting the patch, you'll want to look at https://wiki.koha-community.org/wiki/Git_bz_configuration Let us know if you have any issues. Once your patch is accepted, you'll also join this list: https://git.koha-community.org/stats/koha-master/authors.html 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 -----Original Message----- From: Nigel Titley Sent: Friday, 11 August 2023 8:01 PM To: David Cook ; koha-devel at lists.koha-community.org Subject: Re: [Koha-devel] [Koha] Where would I put the OpenLibrary ID in the MARC record And that, as if by magic, answers what was to be my next question... the koha-testing-docker instructions look comprehensive and I can try them out on my desktop, which seems to meet the requirements. My son, when I was discussing the project with him, said "you should do this in a docker container" and as usual he was right. I presume that once/if I've got it working there's a submission process to get updates back to the main Koha branch. All the best Nigel On 11/08/2023 00:07, David Cook wrote: > That's great news, Nigel! I'm really happy that worked out. > > Have you looked at koha-testing-docker? > https://gitlab.com/koha-community/koha-testing-docker > > You could do the development work on there and then wait/hope for it to flow down to your version? > > 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 > > -----Original Message----- > From: Koha-devel On > Behalf Of Nigel Titley > Sent: Thursday, 10 August 2023 6:40 PM > To: koha-devel at lists.koha-community.org > Subject: Re: [Koha-devel] [Koha] Where would I put the OpenLibrary ID > in the MARC record > > > > On 08/08/2023 10:58, Nigel Titley wrote: >> >> >> On 24/07/2023 01:11, David Cook wrote: >> >>> You could send a request for an "openlibrary" code to be added to >>> the official Standard Identifier Source Codes list: >>> https://www.loc.gov/standards/sourcelist/index.html#maintenance . >>> Honestly, I'm a little surprised there isn't already an entry for it >>> there. I'm sure they'd approve a request for it. >> >> I've put in a request to the LOC. We'll see if anything comes of it. >> They may request (I would do so in their place) that the request >> comes from the Open Library itself in which case I'll have to chase >> that route first. > > Well, to my surprise LOC got back to me today and said they had added Open Library to the SISC list. > > https://loc.gov/marc/relators/tn230808src.html > > So we now have a standardised way to add OLIDs to a MARC record > > 024 7 _ | $2 openlib | $a > > And that means I can have a look at adding OLIDs to the cover art retrieval from Open Library... which means dusting off my... erk... > javascript. Which means sorting out sympa so I can get Koha up to date... > > Nigel > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > From nigel at titley.com Mon Aug 14 13:40:28 2023 From: nigel at titley.com (Nigel Titley) Date: Mon, 14 Aug 2023 12:40:28 +0100 Subject: [Koha-devel] [Koha] Where would I put the OpenLibrary ID in the MARC record In-Reply-To: <007301d9ce4d$35dbef30$a193cd90$@prosentient.com.au> References: <74d9d6e5-a4f9-63eb-0636-afe6360df2df@titley.com> <5d24759a-fd33-b16c-8d80-c7ffc052ea84@titley.com> <16c8a72a-76fa-bb30-3152-714ccbf450f1@titley.com> <065401d9bdc3$6eb2bc20$4c183460$@prosentient.com.au> <741a3bc8-a847-d6a9-a783-cfce261af3fd@titley.com> <7a8efa31-11a5-44ee-068f-3bb31100986d@titley.com> <002601d9cbdf$75fa1710$61ee4530$@prosentient.com.au> <007301d9ce4d$35dbef30$a193cd90$@prosentient.com.au> Message-ID: Hi David Many thanks. I've read the documentation, created a koha bugzilla account, created an enhancement request and assigned to myself, just to kick this off. However, looks like the original author of the OpenLibrary cover retrieval code (joubu) is still around so they may be better equipped than me to deal with this. I don't want to tread on anyone's toes. If this isn't the right process then please let me know. All the best and thanks to the wonderful koha community for being so helpful. Nigel On 14/08/2023 02:18, David Cook wrote: > Hi Nigel, > > "I'm going to do this in a docker container" is what I say for most of my code projects (at home and the office). So long as you're not working with SystemD, it generally makes everything easier. > > I think this wiki page might describe the process best: https://wiki.koha-community.org/wiki/Development_workflow > > And for the practical aspect of submitting the patch, you'll want to look at https://wiki.koha-community.org/wiki/Git_bz_configuration > > Let us know if you have any issues. > > Once your patch is accepted, you'll also join this list: https://git.koha-community.org/stats/koha-master/authors.html > > 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 > > -----Original Message----- > From: Nigel Titley > Sent: Friday, 11 August 2023 8:01 PM > To: David Cook ; koha-devel at lists.koha-community.org > Subject: Re: [Koha-devel] [Koha] Where would I put the OpenLibrary ID in the MARC record > > And that, as if by magic, answers what was to be my next question... the koha-testing-docker instructions look comprehensive and I can try them out on my desktop, which seems to meet the requirements. My son, when I was discussing the project with him, said "you should do this in a docker container" and as usual he was right. > > I presume that once/if I've got it working there's a submission process to get updates back to the main Koha branch. > > All the best > > Nigel > > On 11/08/2023 00:07, David Cook wrote: >> That's great news, Nigel! I'm really happy that worked out. >> >> Have you looked at koha-testing-docker? >> https://gitlab.com/koha-community/koha-testing-docker >> >> You could do the development work on there and then wait/hope for it to flow down to your version? >> >> 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 >> >> -----Original Message----- >> From: Koha-devel On >> Behalf Of Nigel Titley >> Sent: Thursday, 10 August 2023 6:40 PM >> To: koha-devel at lists.koha-community.org >> Subject: Re: [Koha-devel] [Koha] Where would I put the OpenLibrary ID >> in the MARC record >> >> >> >> On 08/08/2023 10:58, Nigel Titley wrote: >>> >>> >>> On 24/07/2023 01:11, David Cook wrote: >>> >>>> You could send a request for an "openlibrary" code to be added to >>>> the official Standard Identifier Source Codes list: >>>> https://www.loc.gov/standards/sourcelist/index.html#maintenance . >>>> Honestly, I'm a little surprised there isn't already an entry for it >>>> there. I'm sure they'd approve a request for it. >>> >>> I've put in a request to the LOC. We'll see if anything comes of it. >>> They may request (I would do so in their place) that the request >>> comes from the Open Library itself in which case I'll have to chase >>> that route first. >> >> Well, to my surprise LOC got back to me today and said they had added Open Library to the SISC list. >> >> https://loc.gov/marc/relators/tn230808src.html >> >> So we now have a standardised way to add OLIDs to a MARC record >> >> 024 7 _ | $2 openlib | $a >> >> And that means I can have a look at adding OLIDs to the cover art retrieval from Open Library... which means dusting off my... erk... >> javascript. Which means sorting out sympa so I can get Koha up to date... >> >> Nigel >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at 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/ >> > From dcook at prosentient.com.au Tue Aug 15 04:45:27 2023 From: dcook at prosentient.com.au (David Cook) Date: Tue, 15 Aug 2023 12:45:27 +1000 Subject: [Koha-devel] [Koha] Where would I put the OpenLibrary ID in the MARC record In-Reply-To: References: <74d9d6e5-a4f9-63eb-0636-afe6360df2df@titley.com> <5d24759a-fd33-b16c-8d80-c7ffc052ea84@titley.com> <16c8a72a-76fa-bb30-3152-714ccbf450f1@titley.com> <065401d9bdc3$6eb2bc20$4c183460$@prosentient.com.au> <741a3bc8-a847-d6a9-a783-cfce261af3fd@titley.com> <7a8efa31-11a5-44ee-068f-3bb31100986d@titley.com> <002601d9cbdf$75fa1710$61ee4530$@prosentient.com.au> <007301d9ce4d$35dbef30$a193cd90$@prosentient.com.au> Message-ID: <00f301d9cf22$93fcb470$bbf61d50$@prosentient.com.au> Hi Nigel, That's looking good to me. When you're ready with a patch, you can use "git bz" in koha-testing-docker to upload the patch to https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34527 and then testers and QA will take it from there. Joubu (Jonathan Druart) has a lot of work to do, so I'm sure he wouldn't mind you working on this! Being familiar with the original code, you might find he comments on the patch/report at some stage. 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 -----Original Message----- From: Nigel Titley Sent: Monday, 14 August 2023 9:40 PM To: David Cook ; koha-devel at lists.koha-community.org Subject: Re: [Koha-devel] [Koha] Where would I put the OpenLibrary ID in the MARC record Hi David Many thanks. I've read the documentation, created a koha bugzilla account, created an enhancement request and assigned to myself, just to kick this off. However, looks like the original author of the OpenLibrary cover retrieval code (joubu) is still around so they may be better equipped than me to deal with this. I don't want to tread on anyone's toes. If this isn't the right process then please let me know. All the best and thanks to the wonderful koha community for being so helpful. Nigel On 14/08/2023 02:18, David Cook wrote: > Hi Nigel, > > "I'm going to do this in a docker container" is what I say for most of my code projects (at home and the office). So long as you're not working with SystemD, it generally makes everything easier. > > I think this wiki page might describe the process best: > https://wiki.koha-community.org/wiki/Development_workflow > > And for the practical aspect of submitting the patch, you'll want to > look at https://wiki.koha-community.org/wiki/Git_bz_configuration > > Let us know if you have any issues. > > Once your patch is accepted, you'll also join this list: > https://git.koha-community.org/stats/koha-master/authors.html > > 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 > > -----Original Message----- > From: Nigel Titley > Sent: Friday, 11 August 2023 8:01 PM > To: David Cook ; > koha-devel at lists.koha-community.org > Subject: Re: [Koha-devel] [Koha] Where would I put the OpenLibrary ID > in the MARC record > > And that, as if by magic, answers what was to be my next question... the koha-testing-docker instructions look comprehensive and I can try them out on my desktop, which seems to meet the requirements. My son, when I was discussing the project with him, said "you should do this in a docker container" and as usual he was right. > > I presume that once/if I've got it working there's a submission process to get updates back to the main Koha branch. > > All the best > > Nigel > > On 11/08/2023 00:07, David Cook wrote: >> That's great news, Nigel! I'm really happy that worked out. >> >> Have you looked at koha-testing-docker? >> https://gitlab.com/koha-community/koha-testing-docker >> >> You could do the development work on there and then wait/hope for it to flow down to your version? >> >> 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 >> >> -----Original Message----- >> From: Koha-devel On >> Behalf Of Nigel Titley >> Sent: Thursday, 10 August 2023 6:40 PM >> To: koha-devel at lists.koha-community.org >> Subject: Re: [Koha-devel] [Koha] Where would I put the OpenLibrary ID >> in the MARC record >> >> >> >> On 08/08/2023 10:58, Nigel Titley wrote: >>> >>> >>> On 24/07/2023 01:11, David Cook wrote: >>> >>>> You could send a request for an "openlibrary" code to be added to >>>> the official Standard Identifier Source Codes list: >>>> https://www.loc.gov/standards/sourcelist/index.html#maintenance . >>>> Honestly, I'm a little surprised there isn't already an entry for >>>> it there. I'm sure they'd approve a request for it. >>> >>> I've put in a request to the LOC. We'll see if anything comes of it. >>> They may request (I would do so in their place) that the request >>> comes from the Open Library itself in which case I'll have to chase >>> that route first. >> >> Well, to my surprise LOC got back to me today and said they had added Open Library to the SISC list. >> >> https://loc.gov/marc/relators/tn230808src.html >> >> So we now have a standardised way to add OLIDs to a MARC record >> >> 024 7 _ | $2 openlib | $a >> >> And that means I can have a look at adding OLIDs to the cover art retrieval from Open Library... which means dusting off my... erk... >> javascript. Which means sorting out sympa so I can get Koha up to date... >> >> Nigel >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at 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/ >> > From dcook at prosentient.com.au Wed Aug 16 06:35:55 2023 From: dcook at prosentient.com.au (David Cook) Date: Wed, 16 Aug 2023 14:35:55 +1000 Subject: [Koha-devel] WARNING: MYSQL_OPT_RECONNECT is deprecated and will be removed in a future version. Message-ID: <01ad01d9cffb$2755dde0$760199a0$@prosentient.com.au> Hi all, If you're using Ubuntu, you may have noticed this message filling up your logs. It looks like Ubuntu recently released a version of libmysqlclient21 which outputs this warning message if you try to set MYSQL_OPT_RECONNECT. DBD::mysql sets it to false and therein lies the problem: https://github.com/perl5-dbi/DBD-mysql/issues/354 At a glance, the only real short-term option seems to be to downgrade the MySQL client, but keeping my eyes open. 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Fri Aug 18 01:24:34 2023 From: dcook at prosentient.com.au (David Cook) Date: Fri, 18 Aug 2023 09:24:34 +1000 Subject: [Koha-devel] WARNING: MYSQL_OPT_RECONNECT is deprecated and will be removed in a future version. In-Reply-To: <01ad01d9cffb$2755dde0$760199a0$@prosentient.com.au> References: <01ad01d9cffb$2755dde0$760199a0$@prosentient.com.au> Message-ID: <036a01d9d162$01337510$039a5f30$@prosentient.com.au> Letting folks know that Ubuntu have released a patched libdbd-mysql-perl which claims to have fixed the issue. I haven't confirmed that it fixes it myself, but it should be a trivial change, so I imagine that it does. 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 On Behalf Of David Cook Sent: Wednesday, 16 August 2023 2:36 PM To: koha-devel at lists.koha-community.org Subject: [Koha-devel] WARNING: MYSQL_OPT_RECONNECT is deprecated and will be removed in a future version. Hi all, If you're using Ubuntu, you may have noticed this message filling up your logs. It looks like Ubuntu recently released a version of libmysqlclient21 which outputs this warning message if you try to set MYSQL_OPT_RECONNECT. DBD::mysql sets it to false and therein lies the problem: https://github.com/perl5-dbi/DBD-mysql/issues/354 At a glance, the only real short-term option seems to be to downgrade the MySQL client, but keeping my eyes open. 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From fridolin.somers at biblibre.com Mon Aug 21 20:46:50 2023 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Mon, 21 Aug 2023 08:46:50 -1000 Subject: [Koha-devel] WARNING: MYSQL_OPT_RECONNECT is deprecated and will be removed in a future version. In-Reply-To: <036a01d9d162$01337510$039a5f30$@prosentient.com.au> References: <01ad01d9cffb$2755dde0$760199a0$@prosentient.com.au> <036a01d9d162$01337510$039a5f30$@prosentient.com.au> Message-ID: You can see it in changelog : http://changelogs.ubuntu.com/changelogs/pool/universe/libd/libdbd-mysql-perl/libdbd-mysql-perl_4.050-3ubuntu0.2/changelog Le 17/08/2023 à 13:24, David Cook a écrit : > Letting folks know that Ubuntu have released a patched libdbd-mysql-perl > which claims to have fixed the issue. > > I haven’t confirmed that it fixes it myself, but it should be a trivial > change, so I imagine that it does. > > 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 *On > Behalf Of *David Cook > *Sent:* Wednesday, 16 August 2023 2:36 PM > *To:* koha-devel at lists.koha-community.org > *Subject:* [Koha-devel] WARNING: MYSQL_OPT_RECONNECT is deprecated and > will be removed in a future version. > > Hi all, > > If you’re using Ubuntu, you may have noticed this message filling up > your logs. > > It looks like Ubuntu recently released a version of libmysqlclient21 > which outputs this warning message if you try to set MYSQL_OPT_RECONNECT. > > DBD::mysql sets it to false and therein lies the problem: > https://github.com/perl5-dbi/DBD-mysql/issues/354 > > > At a glance, the only real short-term option seems to be to downgrade > the MySQL client, but keeping my eyes open… > > 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 > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ -- Fridolin SOMERS Software and system maintainer 🦄 BibLibre, France From dcook at prosentient.com.au Tue Aug 22 02:38:54 2023 From: dcook at prosentient.com.au (David Cook) Date: Tue, 22 Aug 2023 10:38:54 +1000 Subject: [Koha-devel] WARNING: MYSQL_OPT_RECONNECT is deprecated and will be removed in a future version. In-Reply-To: References: <01ad01d9cffb$2755dde0$760199a0$@prosentient.com.au> <036a01d9d162$01337510$039a5f30$@prosentient.com.au> Message-ID: <053601d9d491$10dd1110$32973330$@prosentient.com.au> I knew that it was "supposed" to fix it. I just haven't personally confirmed that it "definitely" fixes it haha. But there have been lots of people on the Github issue that have said it has fixed it for them so it seems pretty safe. That said, pali (the 2nd biggest contributor to DBD::mysql) has said that the fix used by Ubuntu isn't enough and he has an alternative set of patches to use. Interesting seeing this all play out upstream... 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 -----Original Message----- From: Koha-devel On Behalf Of Fridolin SOMERS Sent: Tuesday, 22 August 2023 4:47 AM To: koha-devel at lists.koha-community.org Subject: Re: [Koha-devel] WARNING: MYSQL_OPT_RECONNECT is deprecated and will be removed in a future version. You can see it in changelog : http://changelogs.ubuntu.com/changelogs/pool/universe/libd/libdbd-mysql-perl/libdbd-mysql-perl_4.050-3ubuntu0.2/changelog Le 17/08/2023 à 13:24, David Cook a écrit : > Letting folks know that Ubuntu have released a patched > libdbd-mysql-perl which claims to have fixed the issue. > > I haven’t confirmed that it fixes it myself, but it should be a > trivial change, so I imagine that it does. > > 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 *On > Behalf Of *David Cook > *Sent:* Wednesday, 16 August 2023 2:36 PM > *To:* koha-devel at lists.koha-community.org > *Subject:* [Koha-devel] WARNING: MYSQL_OPT_RECONNECT is deprecated and > will be removed in a future version. > > Hi all, > > If you’re using Ubuntu, you may have noticed this message filling up > your logs. > > It looks like Ubuntu recently released a version of libmysqlclient21 > which outputs this warning message if you try to set MYSQL_OPT_RECONNECT. > > DBD::mysql sets it to false and therein lies the problem: > https://github.com/perl5-dbi/DBD-mysql/issues/354 > > > At a glance, the only real short-term option seems to be to downgrade > the MySQL client, but keeping my eyes open… > > 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 > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ -- Fridolin SOMERS Software and system maintainer 🦄 BibLibre, France _______________________________________________ Koha-devel mailing list Koha-devel at 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/ From dcook at prosentient.com.au Wed Aug 23 02:19:11 2023 From: dcook at prosentient.com.au (David Cook) Date: Wed, 23 Aug 2023 10:19:11 +1000 Subject: [Koha-devel] DBD::mysql unmaintained Message-ID: <05b701d9d557$77270fe0$65752fa0$@prosentient.com.au> Hi all, Daniël van Eeden, the person who releases DBD::mysql on CPAN and has push privileges to https://github.com/perl5-dbi/DBD-mysql, has said that he is no longer maintaining DBD::mysql. That explains why Ubuntu’s package seems to just be stacking up patches on top of the last release from 2019. (I’m glad I don’t use DBD::mysql from CPAN. I do use DBD::Pg from CPAN but it’s much better maintained.) Anyway, I’m asking for more information about the future of DBD::mysql, and thought I’d keep you all informed. 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexbuckley at catalyst.net.nz Wed Aug 23 02:52:44 2023 From: alexbuckley at catalyst.net.nz (Alex Buckley) Date: Wed, 23 Aug 2023 12:52:44 +1200 Subject: [Koha-devel] Question about an Acquisitions enhancement proposal Message-ID: <2acea717-e066-8ffe-f924-4b1e04848b6f@catalyst.net.nz> Hi Koha community, I really enjoyed meeting many of you at KohaCon in Finland for the first-time in person!! I have a question. We have a partner library who is interested in sponsoring an enhancement so they can change the quantity in order lines of open baskets. Currently, if you click the 'Modify' link for an order line in an open basket and change the value in the Quantity text input a JavaScript popup appears telling you "You can't add a new item, please create a new order line" - see attached screenshot. Looking at the code I can see that JavaScript popup is coming from https://github.com/Koha-Community/Koha/blob/1403fd847a66432efda2c8724f61bcc6e413cda9/koha-tmpl/intranet-tmpl/prog/en/modules/acqui/neworderempty.tt#L144 Before we go any further with starting work on making a bug report and writing this enhancement I wanted to check a few things with the community to make sure we start on the right track: Q1) Is adding the ability to change the quantity of order lines in open baskets a bad idea? Q2) Is there anything we should keep in mind? Q3) Do you have any suggestions of how to approach writing this enhancement? Any feedback, and suggestions, would be much appreciated. Kind regards, Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Current behaviour when modifying quantity of existing order line.png Type: image/png Size: 139923 bytes Desc: not available URL: From dcook at prosentient.com.au Thu Aug 24 08:59:19 2023 From: dcook at prosentient.com.au (David Cook) Date: Thu, 24 Aug 2023 16:59:19 +1000 Subject: [Koha-devel] How did we implement Verovio? Message-ID: <000701d9d658$8ab76080$a0262180$@prosentient.com.au> Hi all, I've gotten auto-blocked on Bugzilla, so I figured I'd go to the listserv while I wait for my access to be restored. I was reading https://book.verovio.org/installing-or-building-from-sources/javascript-and- webassembly.html and it makes me think "koha-tmpl/opac-tmpl/lib/verovio/verovio-toolkit.js" comes from https://github.com/rism-digital/verovio/releases However, it's not clear where "koha-tmpl/opac-tmpl/lib/verovio/midiplayer.js" comes from. After some digging, I found that it comes from here: https://github.com/rism-digital/midi-player/blob/master/player/midiplayer.js I reckon we should include some links on the about.pl to show where we got the code. Anyway, my issue with it was how it dynamically creates HTML with "onclick" event handlers, which aren't compatible with Content-Security-Policy. I'll raise an issue with them. The git repo hasn't been updated in over 2 years but fingers crossed. 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From laurence.rault at biblibre.com Thu Aug 24 10:04:07 2023 From: laurence.rault at biblibre.com (Laurence Rault) Date: Thu, 24 Aug 2023 10:04:07 +0200 Subject: [Koha-devel] Question about an Acquisitions enhancement proposal In-Reply-To: <2acea717-e066-8ffe-f924-4b1e04848b6f@catalyst.net.nz> References: <2acea717-e066-8ffe-f924-4b1e04848b6f@catalyst.net.nz> Message-ID: <1677dfe7-f8dc-2a70-5548-4e0f5c585f15@biblibre.com> Hi Alex, Q1) I think it is a good idea : it is already possible to change quantity when item is created at reception or cataloguing, so it seems consistent that quantity can be changed also when item is created at order. Kind regards, Laurence Rault Le 23/08/2023 à 02:52, Alex Buckley a écrit : > Hi Koha community, > > I really enjoyed meeting many of you at KohaCon in Finland for the > first-time in person!! > > I have a question. We have a partner library who is interested in > sponsoring an enhancement so they can change the quantity in order lines > of open baskets. > > Currently, if you click the 'Modify' link for an order line in an open > basket and change the value in the Quantity text input a JavaScript > popup appears telling you "You can't add a new item, please create a new > order line" - see attached screenshot. > > Looking at the code I can see that JavaScript popup is coming from > https://github.com/Koha-Community/Koha/blob/1403fd847a66432efda2c8724f61bcc6e413cda9/koha-tmpl/intranet-tmpl/prog/en/modules/acqui/neworderempty.tt#L144 > > Before we go any further with starting work on making a bug report and > writing this enhancement I wanted to check a few things with the > community to make sure we start on the right track: > > Q1) Is adding the ability to change the quantity of order lines in open > baskets a bad idea? > > Q2) Is there anything we should keep in mind? > > Q3) Do you have any suggestions of how to approach writing this enhancement? > > Any feedback, and suggestions, would be much appreciated. > > Kind regards, > > Alex > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ -- ------------------------ Laurence Rault Responsable Pôle Développement BibLibre http://www.biblibre.com laurence.rault at biblibre.com p. 06 27 85 46 49 From oleonard at myacpl.org Thu Aug 24 17:31:27 2023 From: oleonard at myacpl.org (Owen Leonard) Date: Thu, 24 Aug 2023 11:31:27 -0400 Subject: [Koha-devel] How did we implement Verovio? In-Reply-To: <000701d9d658$8ab76080$a0262180$@prosentient.com.au> References: <000701d9d658$8ab76080$a0262180$@prosentient.com.au> Message-ID: > I’ll raise an issue with them. The git repo hasn’t been updated in over 2 years but fingers crossed. I'm not optimistic based on the lack of activity in other issues raised there. At the very least we can patch our copy of the library with a simple fix to remove the onclicks. The bigger issue may turn out to be that the library is using outdated browser APIs: https://github.com/rism-digital/midi-player/issues/30. -- Owen -- Web Developer Athens County Public Libraries (740) 737-6006 https://www.myacpl.org From dcook at prosentient.com.au Fri Aug 25 01:25:17 2023 From: dcook at prosentient.com.au (David Cook) Date: Fri, 25 Aug 2023 09:25:17 +1000 Subject: [Koha-devel] How did we implement Verovio? In-Reply-To: References: <000701d9d658$8ab76080$a0262180$@prosentient.com.au> Message-ID: <006e01d9d6e2$482de2e0$d889a8a0$@prosentient.com.au> I was thinking the same thing about the lack of activity. It's interesting since "verovio" was updated just a few days ago. Looks like Agustin got some commits into midi-player back in 2019... I'm down with patching our copy though. The browser API issue is a worry. At some point we might just need a different MIDI player... 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 -----Original Message----- From: Koha-devel On Behalf Of Owen Leonard Sent: Friday, 25 August 2023 1:31 AM To: koha-devel at lists.koha-community.org Subject: Re: [Koha-devel] How did we implement Verovio? > I’ll raise an issue with them. The git repo hasn’t been updated in over 2 years but fingers crossed. I'm not optimistic based on the lack of activity in other issues raised there. At the very least we can patch our copy of the library with a simple fix to remove the onclicks. The bigger issue may turn out to be that the library is using outdated browser APIs: https://github.com/rism-digital/midi-player/issues/30. -- Owen -- Web Developer Athens County Public Libraries (740) 737-6006 https://www.myacpl.org _______________________________________________ Koha-devel mailing list Koha-devel at 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/ From dcook at prosentient.com.au Fri Aug 25 01:46:36 2023 From: dcook at prosentient.com.au (David Cook) Date: Fri, 25 Aug 2023 09:46:36 +1000 Subject: [Koha-devel] Admin access to Bugzilla Message-ID: <007a01d9d6e5$3d241510$b76c3f30$@prosentient.com.au> Hi all, Does anyone but Chris Cormack have admin access to Bugzilla? I've been locked out (due to posting too many links), and it would be great to get access back. I was hoping to do some work on Bugzilla today. 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From katrin.fischer.83 at web.de Fri Aug 25 02:48:40 2023 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Fri, 25 Aug 2023 02:48:40 +0200 Subject: [Koha-devel] Admin access to Bugzilla In-Reply-To: <007a01d9d6e5$3d241510$b76c3f30$@prosentient.com.au> References: <007a01d9d6e5$3d241510$b76c3f30$@prosentient.com.au> Message-ID: <1b6c3e69-3f47-e5bc-f32a-ff9024679a29@web.de> Hi David, I had a look at your account, but couldn't see anything wrong with it. Is it still not working? What is the message you are seeing? Katrin On 25.08.23 01:46, David Cook wrote: > > Hi all, > > Does anyone but Chris Cormack have admin access to Bugzilla? > > I’ve been locked out (due to posting too many links), and it would be > great to get access back. I was hoping to do some work on Bugzilla today. > > 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 > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Fri Aug 25 02:51:11 2023 From: dcook at prosentient.com.au (David Cook) Date: Fri, 25 Aug 2023 10:51:11 +1000 Subject: [Koha-devel] Admin access to Bugzilla In-Reply-To: <1b6c3e69-3f47-e5bc-f32a-ff9024679a29@web.de> References: <007a01d9d6e5$3d241510$b76c3f30$@prosentient.com.au> <1b6c3e69-3f47-e5bc-f32a-ff9024679a29@web.de> Message-ID: <008e01d9d6ee$40c43020$c24c9060$@prosentient.com.au> Thanks, Katrin. Chris unblocked me 20 minutes ago or so, but thanks for taking a look! 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: Katrin Fischer Sent: Friday, 25 August 2023 10:49 AM To: David Cook ; Koha Devel Subject: Re: [Koha-devel] Admin access to Bugzilla Hi David, I had a look at your account, but couldn't see anything wrong with it. Is it still not working? What is the message you are seeing? Katrin On 25.08.23 01:46, David Cook wrote: Hi all, Does anyone but Chris Cormack have admin access to Bugzilla? I’ve been locked out (due to posting too many links), and it would be great to get access back. I was hoping to do some work on Bugzilla today. 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 _______________________________________________ Koha-devel mailing list Koha-devel at 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/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexbuckley at catalyst.net.nz Fri Aug 25 02:56:27 2023 From: alexbuckley at catalyst.net.nz (Alex Buckley) Date: Fri, 25 Aug 2023 12:56:27 +1200 Subject: [Koha-devel] Question about an Acquisitions enhancement proposal In-Reply-To: <1677dfe7-f8dc-2a70-5548-4e0f5c585f15@biblibre.com> References: <2acea717-e066-8ffe-f924-4b1e04848b6f@catalyst.net.nz> <1677dfe7-f8dc-2a70-5548-4e0f5c585f15@biblibre.com> Message-ID: <6406b6d8-08aa-a32d-3349-3eb4a2063ef8@catalyst.net.nz> Hi Laurence, Thanks so much for sharing your thoughts on this I really appreciate it. It's good to know that others think this is a good idea too :) Kind regards, Alex On 24/08/23 20:04, Laurence Rault wrote: > Hi Alex, > > Q1) I think it is a good idea : it is already possible to change > quantity when item is created at reception or cataloguing, so it seems > consistent that quantity can be changed also when item is created at > order. > > Kind regards, > > Laurence Rault > > Le 23/08/2023 à 02:52, Alex Buckley a écrit : >> Hi Koha community, >> >> I really enjoyed meeting many of you at KohaCon in Finland for the >> first-time in person!! >> >> I have a question. We have a partner library who is interested in >> sponsoring an enhancement so they can change the quantity in order >> lines of open baskets. >> >> Currently, if you click the 'Modify' link for an order line in an >> open basket and change the value in the Quantity text input a >> JavaScript popup appears telling you "You can't add a new item, >> please create a new order line" - see attached screenshot. >> >> Looking at the code I can see that JavaScript popup is coming from >> https://github.com/Koha-Community/Koha/blob/1403fd847a66432efda2c8724f61bcc6e413cda9/koha-tmpl/intranet-tmpl/prog/en/modules/acqui/neworderempty.tt#L144 >> >> Before we go any further with starting work on making a bug report >> and writing this enhancement I wanted to check a few things with the >> community to make sure we start on the right track: >> >> Q1) Is adding the ability to change the quantity of order lines in >> open baskets a bad idea? > >> Q2) Is there anything we should keep in mind? >> >> Q3) Do you have any suggestions of how to approach writing this >> enhancement? > >> >> Any feedback, and suggestions, would be much appreciated. >> >> Kind regards, >> >> Alex >> >> >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at 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/ > -- *Alex Buckley (he/him)* Koha Developer | Implementation Lead *Catalyst.Net Limited - Expert Open Source Solutions* *Catalyst.Net Limited - a Catalyst IT group company* www.catalyst.net.nz Follow Catalyst Koha on Twitter | Subscribe to the Catalyst Koha newsletter Catalyst Logo 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From philippe.blouin at inlibro.com Fri Aug 25 16:09:44 2023 From: philippe.blouin at inlibro.com (Philippe Blouin) Date: Fri, 25 Aug 2023 10:09:44 -0400 Subject: [Koha-devel] Importing items with "foreign" branches fails badly Message-ID: <6baefcf5-cfc4-421a-a0e3-51405090d357@inlibro.com> Hello! When importing a marc file where some items homebranch are not matching a branchcode in db, the import fails.  Freeze-fail. Before, it used to just skip those items, but it seems (since 23.05) to just fail silently (with a constraint failure in the log, but nothing for the user).  Is it our install or it's a known issue?  When running "show engin innodb status", I get some row lock. Looking at the bug list, I found nothing.  There are many ways to fix this, and we don't want to head into one to be told "ooh, this should be fixed there instead". * Upstream https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21272 Maybe there could be an option in staging to overwrite the homebranches that do not correspond? * Just ignore the item, as before.  But at least leave some info about it in the result page. * Fail as soon as it happens.  Do not import and tell the user to correct the data ? The first option doesn't solve bulkmarcimport.pl :( Feedbacks would be appreciated. -- Philippe Blouin, Directeur de la technologie Tél.  : (833) 465-4276, poste 230 philippe.blouin at inLibro.com inLibro | pour esprit libre | www.inLibro.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From michael.hafen at washk12.org Fri Aug 25 18:31:55 2023 From: michael.hafen at washk12.org (Michael Hafen) Date: Fri, 25 Aug 2023 10:31:55 -0600 Subject: [Koha-devel] Importing items with "foreign" branches fails badly In-Reply-To: <6baefcf5-cfc4-421a-a0e3-51405090d357@inlibro.com> References: <6baefcf5-cfc4-421a-a0e3-51405090d357@inlibro.com> Message-ID: I was looking at the Patron import yesterday, and liked that I could specify the categorycode and branchcode for an import batch. Maybe something like that would work for staging and bulkmarcimport.pl, where there is a (command line) option to override certain fields while processing records. On Fri, Aug 25, 2023 at 8:09 AM Philippe Blouin wrote: > Hello! > > When importing a marc file where some items homebranch are not matching a > branchcode in db, the import fails. Freeze-fail. > > Before, it used to just skip those items, but it seems (since 23.05) to > just fail silently (with a constraint failure in the log, but nothing for > the user). Is it our install or it's a known issue? When running "show > engin innodb status", I get some row lock. > > Looking at the bug list, I found nothing. There are many ways to fix > this, and we don't want to head into one to be told "ooh, this should be > fixed there instead". > > - Upstream > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21272 Maybe > there could be an option in staging to overwrite the homebranches that do > not correspond? > - Just ignore the item, as before. But at least leave some info about > it in the result page. > - Fail as soon as it happens. Do not import and tell the user to > correct the data ? > > The first option doesn't solve bulkmarcimport.pl :( > > Feedbacks would be appreciated. > -- > Philippe Blouin, > Directeur de la technologie > > Tél. : (833) 465-4276, poste 230 > philippe.blouin at inLibro.com > inLibro | pour esprit libre | www.inLibro.com > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -- Michael Hafen Washington County School District Technology Department Systems Analyst -------------- next part -------------- An HTML attachment was scrubbed... URL: From katrin.fischer.83 at web.de Sat Aug 26 10:13:00 2023 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Sat, 26 Aug 2023 10:13:00 +0200 Subject: [Koha-devel] Importing items with "foreign" branches fails badly In-Reply-To: <6baefcf5-cfc4-421a-a0e3-51405090d357@inlibro.com> References: <6baefcf5-cfc4-421a-a0e3-51405090d357@inlibro.com> Message-ID: <7b77740c-952f-56e9-b106-e0f8726edcf2@web.de> Hi, we had this pop up as a problem on IRC in the last few days too, the silent fail/missing feedback is quite annoying. I am not sure if a default would always fix the issue as you might have files with items from different libraries to import. I think a good problem report would be the most helpful. Not only listing the number of items not imported, but also the errors, especially missing or wrong branchcodes with the wrong branchcodes listed. That would help with debugging the import files immensely. As we can undo an incomplete import, it would probably be ok to skip the items instead of failing. I have no strong opinion on skip vs. fail immediately. Hope this helps, Katrin On 25.08.23 16:09, Philippe Blouin wrote: > > Hello! > > When importing a marc file where some items homebranch are not > matching a branchcode in db, the import fails.  Freeze-fail. > > Before, it used to just skip those items, but it seems (since 23.05) > to just fail silently (with a constraint failure in the log, but > nothing for the user).  Is it our install or it's a known issue?  When > running "show engin innodb status", I get some row lock. > > Looking at the bug list, I found nothing.  There are many ways to fix > this, and we don't want to head into one to be told "ooh, this should > be fixed there instead". > > * Upstream > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21272 > Maybe there could be an option in staging to overwrite the > homebranches that do not correspond? > * Just ignore the item, as before.  But at least leave some info > about it in the result page. > * Fail as soon as it happens.  Do not import and tell the user to > correct the data ? > > The first option doesn't solve bulkmarcimport.pl :( > > Feedbacks would be appreciated. > > -- > Philippe Blouin, > Directeur de la technologie > > Tél.  : (833) 465-4276, poste 230 > philippe.blouin at inLibro.com > > inLibro | pour esprit libre | www.inLibro.com > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From egpetridis at gmail.com Sat Aug 26 10:20:05 2023 From: egpetridis at gmail.com (Manos PETRIDIS) Date: Sat, 26 Aug 2023 11:20:05 +0300 Subject: [Koha-devel] Importing items with "foreign" branches fails badly In-Reply-To: <7b77740c-952f-56e9-b106-e0f8726edcf2@web.de> References: <6baefcf5-cfc4-421a-a0e3-51405090d357@inlibro.com> <7b77740c-952f-56e9-b106-e0f8726edcf2@web.de> Message-ID: I also wonder where was this new behavior introduced and if it was ever discussed. A system should not change "just because", without prior if not consent, at least debate. Manos Στις Σάβ 26 Αυγ 2023 στις 11:13 πμ ο χρήστης Katrin Fischer < katrin.fischer.83 at web.de> έγραψε: > Hi, > > we had this pop up as a problem on IRC in the last few days too, the > silent fail/missing feedback is quite annoying. > > I am not sure if a default would always fix the issue as you might have > files with items from different libraries to import. > > I think a good problem report would be the most helpful. Not only listing > the number of items not imported, but also the errors, especially missing > or wrong branchcodes with the wrong branchcodes listed. That would help > with debugging the import files immensely. > > As we can undo an incomplete import, it would probably be ok to skip the > items instead of failing. I have no strong opinion on skip vs. fail > immediately. > > Hope this helps, > > Katrin > On 25.08.23 16:09, Philippe Blouin wrote: > > Hello! > > When importing a marc file where some items homebranch are not matching a > branchcode in db, the import fails. Freeze-fail. > > Before, it used to just skip those items, but it seems (since 23.05) to > just fail silently (with a constraint failure in the log, but nothing for > the user). Is it our install or it's a known issue? When running "show > engin innodb status", I get some row lock. > > Looking at the bug list, I found nothing. There are many ways to fix > this, and we don't want to head into one to be told "ooh, this should be > fixed there instead". > > - Upstream > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21272 Maybe > there could be an option in staging to overwrite the homebranches that do > not correspond? > - Just ignore the item, as before. But at least leave some info about > it in the result page. > - Fail as soon as it happens. Do not import and tell the user to > correct the data ? > > The first option doesn't solve bulkmarcimport.pl :( > > Feedbacks would be appreciated. > -- > Philippe Blouin, > Directeur de la technologie > > Tél. : (833) 465-4276, poste 230 > philippe.blouin at inLibro.com > inLibro | pour esprit libre | www.inLibro.com > > _______________________________________________ > Koha-devel mailing listKoha-devel at lists.koha-community.orghttps://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/ > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From katrin.fischer.83 at web.de Sat Aug 26 10:29:39 2023 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Sat, 26 Aug 2023 10:29:39 +0200 Subject: [Koha-devel] Question about an Acquisitions enhancement proposal In-Reply-To: <2acea717-e066-8ffe-f924-4b1e04848b6f@catalyst.net.nz> References: <2acea717-e066-8ffe-f924-4b1e04848b6f@catalyst.net.nz> Message-ID: Hi Alex, it was really nice to get to know you in person :) Q1) As others have pointed out, you can already change the quantity if items are created 'on receive' or 'in cataloguing', so it would make sense to extend this to 'on order' as well. I assume it was not implemented initially, because it would have complicated the development. Q2) I was thinking about this one for a bit: * EDIFACT: I am not sure how this would/could affect the EDIFACT ordering process, but as it's already possible now in 2 out of 3 cases, this is probably not a blocker. * Logging: It looks like changing the quantity is already logged as a change on the order line. So that's good. Q3) If we could display the same item form and controls as when creating the order, it would also allow to update and pick specific items to be removed from the order. Also it would give us a consistent GUI. Hope this helps! Katrin On 23.08.23 02:52, Alex Buckley wrote: > > Hi Koha community, > > I really enjoyed meeting many of you at KohaCon in Finland for the > first-time in person!! > > I have a question. We have a partner library who is interested in > sponsoring an enhancement so they can change the quantity in order > lines of open baskets. > > Currently, if you click the 'Modify' link for an order line in an open > basket and change the value in the Quantity text input a JavaScript > popup appears telling you "You can't add a new item, please create a > new order line" - see attached screenshot. > > Looking at the code I can see that JavaScript popup is coming from > https://github.com/Koha-Community/Koha/blob/1403fd847a66432efda2c8724f61bcc6e413cda9/koha-tmpl/intranet-tmpl/prog/en/modules/acqui/neworderempty.tt#L144 > > > Before we go any further with starting work on making a bug report and > writing this enhancement I wanted to check a few things with the > community to make sure we start on the right track: > > Q1) Is adding the ability to change the quantity of order lines in > open baskets a bad idea? > > Q2) Is there anything we should keep in mind? > > Q3) Do you have any suggestions of how to approach writing this > enhancement? > > Any feedback, and suggestions, would be much appreciated. > > Kind regards, > > Alex > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From katrin.fischer.83 at web.de Sat Aug 26 10:32:01 2023 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Sat, 26 Aug 2023 10:32:01 +0200 Subject: [Koha-devel] Importing items with "foreign" branches fails badly In-Reply-To: References: <6baefcf5-cfc4-421a-a0e3-51405090d357@inlibro.com> <7b77740c-952f-56e9-b106-e0f8726edcf2@web.de> Message-ID: <53fccec5-3a9a-97cd-85dc-7843a8ec1511@web.de> I believe this is more likely to be an unintended side affect of some other work done to improve the perfomance and reliability of the import scripts. There was no bug reported as of yet, I suggest to do this as a next step. Katrin On 26.08.23 10:20, Manos PETRIDIS wrote: > I also wonder where was this new behavior introduced and if it was > ever discussed. A system should not change "just because", without > prior if not consent, at least debate. > > Manos > > Στις Σάβ 26 Αυγ 2023 στις 11:13 πμ ο χρήστης Katrin Fischer > έγραψε: > > Hi, > > we had this pop up as a problem on IRC in the last few days too, > the silent fail/missing feedback is quite annoying. > > I am not sure if a default would always fix the issue as you might > have files with items from different libraries to import. > > I think a good problem report would be the most helpful. Not only > listing the number of items not imported, but also the errors, > especially missing or wrong branchcodes with the wrong branchcodes > listed. That would help with debugging the import files immensely. > > As we can undo an incomplete import, it would probably be ok to > skip the items instead of failing. I have no strong opinion on > skip vs. fail immediately. > > Hope this helps, > > Katrin > > On 25.08.23 16:09, Philippe Blouin wrote: >> >> Hello! >> >> When importing a marc file where some items homebranch are not >> matching a branchcode in db, the import fails.  Freeze-fail. >> >> Before, it used to just skip those items, but it seems (since >> 23.05) to just fail silently (with a constraint failure in the >> log, but nothing for the user).  Is it our install or it's a >> known issue?  When running "show engin innodb status", I get some >> row lock. >> >> Looking at the bug list, I found nothing.  There are many ways to >> fix this, and we don't want to head into one to be told "ooh, >> this should be fixed there instead". >> >> * Upstream >> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21272 >> Maybe there could be an option in staging to overwrite the >> homebranches that do not correspond? >> * Just ignore the item, as before.  But at least leave some >> info about it in the result page. >> * Fail as soon as it happens.  Do not import and tell the user >> to correct the data ? >> >> The first option doesn't solve bulkmarcimport.pl >> :( >> >> Feedbacks would be appreciated. >> >> -- >> Philippe Blouin, >> Directeur de la technologie >> >> Tél.  : (833) 465-4276, poste 230 >> philippe.blouin at inLibro.com >> >> inLibro | pour esprit libre | www.inLibro.com >> >> >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at 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/ > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pedro.amorim at ptfs-europe.com Mon Aug 28 16:55:19 2023 From: pedro.amorim at ptfs-europe.com (Amorim, Pedro) Date: Mon, 28 Aug 2023 14:55:19 +0000 Subject: [Koha-devel] Koha 22.11.09 released Message-ID: The Koha community is proud to announce the release of Koha 22.11.09. Koha 22.11.09 is a bugfix/maintenance release. It includes 3 enhancements, 40 bugfixes. The full release notes are available here: https://koha-community.org/koha-22-11-09-released/ Debian packages should be available soon Best regards Pedro Amorim Software Engineer E: pedro.amorim at ptfs-europe.com www.ptfs-europe.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexbuckley at catalyst.net.nz Tue Aug 29 11:06:42 2023 From: alexbuckley at catalyst.net.nz (Alex Buckley) Date: Tue, 29 Aug 2023 21:06:42 +1200 Subject: [Koha-devel] Question about an Acquisitions enhancement proposal In-Reply-To: References: <2acea717-e066-8ffe-f924-4b1e04848b6f@catalyst.net.nz> Message-ID: Hi Katrin, Thanks so much, I look forward to catching up with you in Montreal :) Those are really good points and they are very helpful. I've passed this, and Laurence's, points onto our partner library to check if they would like to proceed with sponsoring this enhancement. As I am about to go on my Italy annual leave Aleisha, or Wainui, will likely write this enhancement so you might see a bug report from them for this in the near future! Thanks again for your response. Kind regards, Alex On 26/08/23 20:29, Katrin Fischer wrote: > > Hi Alex, > > it was really nice to get to know you in person :) > > Q1) As others have pointed out, you can already change the quantity if > items are created 'on receive' or 'in cataloguing', so it would make > sense to extend this to 'on order' as well. I assume it was not > implemented initially, because it would have complicated the development. > > Q2) I was thinking about this one for a bit: > > * EDIFACT: I am not sure how this would/could affect the EDIFACT > ordering process, but as it's already possible now in 2 out of 3 > cases, this is probably not a blocker. > > * Logging: It looks like changing the quantity is already logged as a > change on the order line. So that's good. > > Q3) If we could display the same item form and controls as when > creating the order, it would also allow to update and pick specific > items to be removed from the order. Also it would give us a consistent > GUI. > > Hope this helps! > > Katrin > > > On 23.08.23 02:52, Alex Buckley wrote: >> >> Hi Koha community, >> >> I really enjoyed meeting many of you at KohaCon in Finland for the >> first-time in person!! >> >> I have a question. We have a partner library who is interested in >> sponsoring an enhancement so they can change the quantity in order >> lines of open baskets. >> >> Currently, if you click the 'Modify' link for an order line in an >> open basket and change the value in the Quantity text input a >> JavaScript popup appears telling you "You can't add a new item, >> please create a new order line" - see attached screenshot. >> >> Looking at the code I can see that JavaScript popup is coming from >> https://github.com/Koha-Community/Koha/blob/1403fd847a66432efda2c8724f61bcc6e413cda9/koha-tmpl/intranet-tmpl/prog/en/modules/acqui/neworderempty.tt#L144 >> >> >> Before we go any further with starting work on making a bug report >> and writing this enhancement I wanted to check a few things with the >> community to make sure we start on the right track: >> >> Q1) Is adding the ability to change the quantity of order lines in >> open baskets a bad idea? >> >> Q2) Is there anything we should keep in mind? >> >> Q3) Do you have any suggestions of how to approach writing this >> enhancement? >> >> Any feedback, and suggestions, would be much appreciated. >> >> Kind regards, >> >> Alex >> >> >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at 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/ > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ -- *Alex Buckley (he/him)* Koha Developer | Implementation Lead *Catalyst.Net Limited - Expert Open Source Solutions* *Catalyst.Net Limited - a Catalyst IT group company* www.catalyst.net.nz Follow Catalyst Koha on Twitter | Subscribe to the Catalyst Koha newsletter Catalyst Logo 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fridolin.somers at biblibre.com Tue Aug 29 23:27:40 2023 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Tue, 29 Aug 2023 11:27:40 -1000 Subject: [Koha-devel] Koha 23.05.03 released Message-ID: Hello everyone 🤗 The Koha community is proud to announce the release of Koha 23.05.03. It is a bugfix/maintenance release including 4 enhancements, 43 bugfixes. The full release notes are available here: https://koha-community.org/koha-23-05-03-released/ Debian packages should be available soon 🎁 Best regards 🤓 -- Fridolin SOMERS Software and system maintainer 🦄 BibLibre, France From zahidiqbal.isb at gmail.com Wed Aug 30 11:44:26 2023 From: zahidiqbal.isb at gmail.com (Zahid Iqbal) Date: Wed, 30 Aug 2023 14:44:26 +0500 Subject: [Koha-devel] needed help in koha cataloguing module Message-ID: Dear all, i am using koha 22.11 version i want to disable the indicator box and box for (a) (b) (c) etc so user can not type and change the [a] [b] [c] to [e] [f] [3] etc. On adding/modifying books koha page koha/cataloguing/addbiblio.pl when i click on 245 (*a*) it allow me to change (*a*) i want to disable/readonly [a] and two boxes for indicators so it cannot be changed.is there any system preference value to restrict the user? or any other suggestion? should i look into MARCOverlayRules ? needed help in this problem. Best regards, -- *Zahid* -------------- next part -------------- An HTML attachment was scrubbed... URL: From nigel at titley.com Wed Aug 30 21:05:41 2023 From: nigel at titley.com (Nigel Titley) Date: Wed, 30 Aug 2023 20:05:41 +0100 Subject: [Koha-devel] [Koha] Where would I put the OpenLibrary ID in the MARC record In-Reply-To: References: <74d9d6e5-a4f9-63eb-0636-afe6360df2df@titley.com> <5d24759a-fd33-b16c-8d80-c7ffc052ea84@titley.com> <16c8a72a-76fa-bb30-3152-714ccbf450f1@titley.com> <065401d9bdc3$6eb2bc20$4c183460$@prosentient.com.au> <741a3bc8-a847-d6a9-a783-cfce261af3fd@titley.com> <7a8efa31-11a5-44ee-068f-3bb31100986d@titley.com> <002601d9cbdf$75fa1710$61ee4530$@prosentient.com.au> <007301d9ce4d$35dbef30$a193cd90$@prosentient.com.au> Message-ID: On 30/08/2023 11:49, Jonathan Druart wrote: > For the record, the bug report is 34527. Patch attached. Many thanks for this. I'd not made much progress up to this point. My testing seems to indicate that the patch does indeed work and retrieves covers from OpenLib even when there isn't an ISBN (but there is an OLID in MARC field 024). I've made a couple of notes in a comment to the bug. > Note that I am Joubu but not the original author of the OpenLibrary > cover retrieval code. My apologies. I didn't delve deeply enough into the code history and jumped to conclusions. Mea culpa Nigel From kohanews at gmail.com Thu Aug 31 13:31:07 2023 From: kohanews at gmail.com (Koha Newsletter) Date: Thu, 31 Aug 2023 13:31:07 +0200 Subject: [Koha-devel] Koha Community Newsletter: August 2023 Message-ID: The Koha Community Newsletter for August 2023 is here: https://koha-community.org/koha-community-newsletter-august-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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From philippe.blouin at inlibro.com Thu Aug 31 22:15:07 2023 From: philippe.blouin at inlibro.com (Philippe Blouin) Date: Thu, 31 Aug 2023 16:15:07 -0400 Subject: [Koha-devel] plugins on KohaDevboxes Message-ID: <46ea8041-d885-49a7-aabb-0ffd65f2c1b9@inlibro.com> Hi! Any suggestion onto why our plugin doesn't seem to work on (bywater's) Devboxes while being perfectly fine in 22,23 or master local installs ? The UI of the config is all damaged, like the dropbox not being clickable.  Below first is the devbox version, versus our installations right after. Any hint would be greatly appreciated. Thanks -- Philippe Blouin, Directeur de la technologie Tél.  : (833) 465-4276, poste 230 philippe.blouin at inLibro.com inLibro | pour esprit libre | www.inLibro.com -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot from 2023-08-31 16-13-37.png Type: image/png Size: 16536 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot from 2023-08-31 16-13-08.png Type: image/png Size: 34109 bytes Desc: not available URL: From jonathan.druart at bugs.koha-community.org Thu Aug 31 22:45:56 2023 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Thu, 31 Aug 2023 22:45:56 +0200 Subject: [Koha-devel] plugins on KohaDevboxes In-Reply-To: <46ea8041-d885-49a7-aabb-0ffd65f2c1b9@inlibro.com> References: <46ea8041-d885-49a7-aabb-0ffd65f2c1b9@inlibro.com> Message-ID: Use the non-translated interface or update the French templates (from the admin of the sandboxes, under the actions menu) Le jeudi 31 août 2023, Philippe Blouin a écrit : > Hi! > > Any suggestion onto why our plugin doesn't seem to work on (bywater's) Devboxes while being perfectly fine in 22,23 or master local installs ? > > The UI of the config is all damaged, like the dropbox not being clickable. Below first is the devbox version, versus our installations right after. > > > > > > Any hint would be greatly appreciated. > > Thanks > > -- > Philippe Blouin, > Directeur de la technologie > > Tél. : (833) 465-4276, poste 230 > philippe.blouin at inLibro.com > > inLibro | pour esprit libre | www.inLibro.com -------------- next part -------------- An HTML attachment was scrubbed... URL: