From dcook at prosentient.com.au Mon May 4 09:06:25 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Mon, 4 May 2020 17:06:25 +1000 Subject: [Koha-devel] Adding fonts to Koha for label creator Message-ID: <05b101d621e2$86ae3e60$940abb20$@prosentient.com.au> Hi all, How does one add fonts to Koha for the label creator? I'm curious about adding "Arial" ( or rather LiberationSans-Regular.ttf as matched by fc-match) and "Arial Bold" (or rather Roboto-Regular.ttf as matched by fc-match) to the Koha label creator. I see we have a hard-coded list of font types in C4/Creators/Lib.pm. There is also a list of TTF files in etc/koha-conf.xml. I could update both places, but I am wondering if that's enough. I've tried to read https://metacpan.org/release/PDF-Reuse/source/lib/PDF/Reuse.pm but the mix of English and Swedish makes progress a bit slow. Based on sub Font in C4/Creators/PDF.pm, I'm guessing that's it? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From ruth.rmgv at gmail.com Mon May 4 09:45:29 2020 From: ruth.rmgv at gmail.com (Rute Mira) Date: Mon, 4 May 2020 08:45:29 +0100 Subject: [Koha-devel] Change display authorities Message-ID: Hello. How did the display change the authorities results page and authorities details page? I would like to put Last Name (comma) Name (space) Date and out hyperlink. Do I have to change any Xslt or via zebra? Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From bgkriegel at gmail.com Mon May 4 12:25:42 2020 From: bgkriegel at gmail.com (Bernardo Gonzalez Kriegel) Date: Mon, 4 May 2020 07:25:42 -0300 Subject: [Koha-devel] Adding fonts to Koha for label creator In-Reply-To: <05b101d621e2$86ae3e60$940abb20$@prosentient.com.au> References: <05b101d621e2$86ae3e60$940abb20$@prosentient.com.au> Message-ID: Hi David, > How does one add fonts to Koha for the label creator? > > > > I’m curious about adding “Arial” ( or rather LiberationSans-Regular.ttf as > matched by fc-match) and “Arial Bold” (or rather Roboto-Regular.ttf as > matched by fc-match) to the Koha label creator. > > > > I see we have a hard-coded list of font types in C4/Creators/Lib.pm. There > is also a list of TTF files in etc/koha-conf.xml. > Changing paths in koha-conf.xml is enough, replacing entries for H and HB or any other. Bernardo -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.nighswonger at gmail.com Mon May 4 14:50:48 2020 From: chris.nighswonger at gmail.com (Christopher Nighswonger) Date: Mon, 4 May 2020 08:50:48 -0400 Subject: [Koha-devel] Adding fonts to Koha for label creator In-Reply-To: References: <05b101d621e2$86ae3e60$940abb20$@prosentient.com.au> Message-ID: On Mon, May 4, 2020 at 6:25 AM Bernardo Gonzalez Kriegel < bgkriegel at gmail.com> wrote: > Hi David, > > >> How does one add fonts to Koha for the label creator? >> >> >> >> I’m curious about adding “Arial” ( or rather LiberationSans-Regular.ttf >> as matched by fc-match) and “Arial Bold” (or rather Roboto-Regular.ttf as >> matched by fc-match) to the Koha label creator. >> >> >> >> I see we have a hard-coded list of font types in C4/Creators/Lib.pm. >> There is also a list of TTF files in etc/koha-conf.xml. >> > > Changing paths in koha-conf.xml is enough, replacing entries for H and HB > or any other. > > Hard-coded fonts are effectively defaults. They are installed by a dependency (I don't recall which atm.). Substituting fonts is done as Bernardo pointed out. Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Tue May 5 01:21:16 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Tue, 5 May 2020 09:21:16 +1000 Subject: [Koha-devel] Adding fonts to Koha for label creator In-Reply-To: References: <05b101d621e2$86ae3e60$940abb20$@prosentient.com.au> Message-ID: <063801d6226a$b60c8580$22259080$@prosentient.com.au> Thanks Chris and Bernardo for getting back to me so quickly. That’s good to know, although from the user experience point of view I don’t think that it’ll be sufficient, since it would still have the old font name in the web UI. I’ll take a deeper look today and report back. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595 From: Christopher Nighswonger Sent: Monday, 4 May 2020 10:51 PM To: Bernardo Gonzalez Kriegel Cc: David Cook ; koha-devel Subject: Re: [Koha-devel] Adding fonts to Koha for label creator On Mon, May 4, 2020 at 6:25 AM Bernardo Gonzalez Kriegel > wrote: Hi David, How does one add fonts to Koha for the label creator? I’m curious about adding “Arial” ( or rather LiberationSans-Regular.ttf as matched by fc-match) and “Arial Bold” (or rather Roboto-Regular.ttf as matched by fc-match) to the Koha label creator. I see we have a hard-coded list of font types in C4/Creators/Lib.pm. There is also a list of TTF files in etc/koha-conf.xml. Changing paths in koha-conf.xml is enough, replacing entries for H and HB or any other. Hard-coded fonts are effectively defaults. They are installed by a dependency (I don't recall which atm.). Substituting fonts is done as Bernardo pointed out. Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From dcook at prosentient.com.au Tue May 5 05:02:31 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Tue, 5 May 2020 13:02:31 +1000 Subject: [Koha-devel] Use Supervisor to manage Koha processes? Message-ID: <065901d62289$9e75c2f0$db6148d0$@prosentient.com.au> Hi all, What do people think about using Supervisor (http://supervisord.org/ ) to manage Koha processes? Actually, as I say that, it looks like Petter Goksøyr Åsen may have already done it years ago: https://gitlab.deichman.no/digibib/koha-docker/commit/9cf892b1ef086d15c634a7 59be51b88ea2f98f75. It might be an easier / more industry way of handling all the different instance-specific Koha component processes. I haven’t tried it, but it’s just a thought. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From dcook at prosentient.com.au Tue May 5 05:41:35 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Tue, 5 May 2020 13:41:35 +1000 Subject: [Koha-devel] Making CGISESSID cookie more secure Message-ID: <067801d6228f$13c23250$3b4696f0$@prosentient.com.au> Hi all, I know it's a tough one to test, but could someone check out https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25360? When using HTTPS, it sets the secure flag on the CGISESSID, so that the cookie can't be sent over an unencrypted HTTP request. It won't break HTTP, but it will make use of HTTPS more secure. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From dcook at prosentient.com.au Wed May 6 03:37:18 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Wed, 6 May 2020 11:37:18 +1000 Subject: [Koha-devel] Adding fonts to Koha for label creator In-Reply-To: <063801d6226a$b60c8580$22259080$@prosentient.com.au> References: <05b101d621e2$86ae3e60$940abb20$@prosentient.com.au> <063801d6226a$b60c8580$22259080$@prosentient.com.au> Message-ID: <07a901d62346$e14f1eb0$a3ed5c10$@prosentient.com.au> Thanks again for your help! I’ve tried your suggestion, and I tried adding options to C4::Creators::Lib with mappings in koha-conf.xml. Both ideas worked. For now, I think I’ll advise people to use your suggestion (and use Javascript to change the labels in the Staff client). I’ve opened a bug report (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25384) to improve this in the future. I think I’ll even have a quick crack at it. Cheers, David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595 From: Koha-devel On Behalf Of dcook at prosentient.com.au Sent: Tuesday, 5 May 2020 9:21 AM To: 'Christopher Nighswonger' ; 'Bernardo Gonzalez Kriegel' Cc: 'koha-devel' Subject: Re: [Koha-devel] Adding fonts to Koha for label creator Thanks Chris and Bernardo for getting back to me so quickly. That’s good to know, although from the user experience point of view I don’t think that it’ll be sufficient, since it would still have the old font name in the web UI. I’ll take a deeper look today and report back. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595 From: Christopher Nighswonger > Sent: Monday, 4 May 2020 10:51 PM To: Bernardo Gonzalez Kriegel > Cc: David Cook >; koha-devel > Subject: Re: [Koha-devel] Adding fonts to Koha for label creator On Mon, May 4, 2020 at 6:25 AM Bernardo Gonzalez Kriegel > wrote: Hi David, How does one add fonts to Koha for the label creator? I’m curious about adding “Arial” ( or rather LiberationSans-Regular.ttf as matched by fc-match) and “Arial Bold” (or rather Roboto-Regular.ttf as matched by fc-match) to the Koha label creator. I see we have a hard-coded list of font types in C4/Creators/Lib.pm. There is also a list of TTF files in etc/koha-conf.xml. Changing paths in koha-conf.xml is enough, replacing entries for H and HB or any other. Hard-coded fonts are effectively defaults. They are installed by a dependency (I don't recall which atm.). Substituting fonts is done as Bernardo pointed out. Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From dcook at prosentient.com.au Wed May 6 05:34:04 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Wed, 6 May 2020 13:34:04 +1000 Subject: [Koha-devel] Adding fonts to Koha for label creator In-Reply-To: <07a901d62346$e14f1eb0$a3ed5c10$@prosentient.com.au> References: <05b101d621e2$86ae3e60$940abb20$@prosentient.com.au> <063801d6226a$b60c8580$22259080$@prosentient.com.au> <07a901d62346$e14f1eb0$a3ed5c10$@prosentient.com.au> Message-ID: <07b701d62357$314f8430$93ee8c90$@prosentient.com.au> Ok I have a patch at https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25384. I haven’t applied it locally, so I’m not super invested in this approach at this point. Open to feedback and testing! (Really I should add some unit tests to t/db_dependent/Creators/Lib.t and t/Creators.t as well to prove the configurability and not just default behaviour. Suppose I wanted to see first if people approved of the approach before finishing it 100%.) David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595 From: Koha-devel On Behalf Of dcook at prosentient.com.au Sent: Wednesday, 6 May 2020 11:37 AM To: 'Christopher Nighswonger' ; 'Bernardo Gonzalez Kriegel' Cc: 'koha-devel' Subject: Re: [Koha-devel] Adding fonts to Koha for label creator Thanks again for your help! I’ve tried your suggestion, and I tried adding options to C4::Creators::Lib with mappings in koha-conf.xml. Both ideas worked. For now, I think I’ll advise people to use your suggestion (and use Javascript to change the labels in the Staff client). I’ve opened a bug report (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25384) to improve this in the future. I think I’ll even have a quick crack at it. Cheers, David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595 From: Koha-devel > On Behalf Of dcook at prosentient.com.au Sent: Tuesday, 5 May 2020 9:21 AM To: 'Christopher Nighswonger' >; 'Bernardo Gonzalez Kriegel' > Cc: 'koha-devel' > Subject: Re: [Koha-devel] Adding fonts to Koha for label creator Thanks Chris and Bernardo for getting back to me so quickly. That’s good to know, although from the user experience point of view I don’t think that it’ll be sufficient, since it would still have the old font name in the web UI. I’ll take a deeper look today and report back. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595 From: Christopher Nighswonger > Sent: Monday, 4 May 2020 10:51 PM To: Bernardo Gonzalez Kriegel > Cc: David Cook >; koha-devel > Subject: Re: [Koha-devel] Adding fonts to Koha for label creator On Mon, May 4, 2020 at 6:25 AM Bernardo Gonzalez Kriegel > wrote: Hi David, How does one add fonts to Koha for the label creator? I’m curious about adding “Arial” ( or rather LiberationSans-Regular.ttf as matched by fc-match) and “Arial Bold” (or rather Roboto-Regular.ttf as matched by fc-match) to the Koha label creator. I see we have a hard-coded list of font types in C4/Creators/Lib.pm. There is also a list of TTF files in etc/koha-conf.xml. Changing paths in koha-conf.xml is enough, replacing entries for H and HB or any other. Hard-coded fonts are effectively defaults. They are installed by a dependency (I don't recall which atm.). Substituting fonts is done as Bernardo pointed out. Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From chris.nighswonger at gmail.com Wed May 6 14:35:54 2020 From: chris.nighswonger at gmail.com (Christopher Nighswonger) Date: Wed, 6 May 2020 08:35:54 -0400 Subject: [Koha-devel] Adding fonts to Koha for label creator In-Reply-To: <07a901d62346$e14f1eb0$a3ed5c10$@prosentient.com.au> References: <05b101d621e2$86ae3e60$940abb20$@prosentient.com.au> <063801d6226a$b60c8580$22259080$@prosentient.com.au> <07a901d62346$e14f1eb0$a3ed5c10$@prosentient.com.au> Message-ID: The concept of your patch looks great, David. I'm sorry I can't test it at the moment. I did add a comment on your description in order to clarify the purpose of the 12 default fonts. Kind regards, Chris On Tue, May 5, 2020 at 9:37 PM wrote: > Thanks again for your help! > > > > I’ve tried your suggestion, and I tried adding options to > C4::Creators::Lib with mappings in koha-conf.xml. Both ideas worked. > > > > For now, I think I’ll advise people to use your suggestion (and use > Javascript to change the labels in the Staff client). > > > > I’ve opened a bug report ( > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25384) to > improve this in the future. I think I’ll even have a quick crack at it. > > > > Cheers, > > > > David Cook > > Systems Librarian > > Prosentient Systems > > 72/330 Wattle St > > Ultimo, NSW 2007 > > Australia > > > > Office: 02 9212 0899 > > Online: 02 8005 0595 > > > > *From:* Koha-devel *On > Behalf Of *dcook at prosentient.com.au > *Sent:* Tuesday, 5 May 2020 9:21 AM > *To:* 'Christopher Nighswonger' ; 'Bernardo > Gonzalez Kriegel' > *Cc:* 'koha-devel' > *Subject:* Re: [Koha-devel] Adding fonts to Koha for label creator > > > > Thanks Chris and Bernardo for getting back to me so quickly. > > > > That’s good to know, although from the user experience point of view I > don’t think that it’ll be sufficient, since it would still have the old > font name in the web UI. > > > > I’ll take a deeper look today and report back. > > > > David Cook > > Systems Librarian > > Prosentient Systems > > 72/330 Wattle St > > Ultimo, NSW 2007 > > Australia > > > > Office: 02 9212 0899 > > Online: 02 8005 0595 > > > > *From:* Christopher Nighswonger > *Sent:* Monday, 4 May 2020 10:51 PM > *To:* Bernardo Gonzalez Kriegel > *Cc:* David Cook ; koha-devel < > koha-devel at lists.koha-community.org> > *Subject:* Re: [Koha-devel] Adding fonts to Koha for label creator > > > > > > On Mon, May 4, 2020 at 6:25 AM Bernardo Gonzalez Kriegel < > bgkriegel at gmail.com> wrote: > > Hi David, > > > > How does one add fonts to Koha for the label creator? > > > > I’m curious about adding “Arial” ( or rather LiberationSans-Regular.ttf as > matched by fc-match) and “Arial Bold” (or rather Roboto-Regular.ttf as > matched by fc-match) to the Koha label creator. > > > > I see we have a hard-coded list of font types in C4/Creators/Lib.pm. There > is also a list of TTF files in etc/koha-conf.xml. > > > > Changing paths in koha-conf.xml is enough, replacing entries for H and HB > or any other. > > > > > > Hard-coded fonts are effectively defaults. They are installed by a > dependency (I don't recall which atm.). > > > > Substituting fonts is done as Bernardo pointed out. > > > > Chris > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomascohen at gmail.com Thu May 7 02:46:12 2020 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Wed, 6 May 2020 21:46:12 -0300 Subject: [Koha-devel] KTD: ES6 as default, support for ES7 Message-ID: Hi. As discussed on today's dev meeting, I moved forward a pushed a series of patches for koha-testing-docker that: - Update the ES docker images we use (official+icu-analysis plugin) to the latest version - Create a koha/elasticsearch-icu:7.x image - Set ES 6 as the new default for KTD - Added an alias to be able to still test ES 5 - Added an alias to be able to test ES 7 That was my TODO from the dev meeting. Looking forward to address any issues this could cause. PS: The discussion involved setting SearchEngine to Elasticsearch on misc4dev by default, but I'm not sure there was consensus on that. People present on the meeting, please answer this email with your perceptions. -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Thu May 7 02:59:46 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Thu, 7 May 2020 10:59:46 +1000 Subject: [Koha-devel] KTD: ES6 as default, support for ES7 In-Reply-To: References: Message-ID: <083e01d6240a$cd730b30$68592190$@prosentient.com.au> I wasn’t at the meeting, but that all sounds good to me. I’d love to see progress on the Elasticsearch front. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595 From: Koha-devel On Behalf Of Tomas Cohen Arazi Sent: Thursday, 7 May 2020 10:46 AM To: koha-devel Subject: [Koha-devel] KTD: ES6 as default, support for ES7 Hi. As discussed on today's dev meeting, I moved forward a pushed a series of patches for koha-testing-docker that: - Update the ES docker images we use (official+icu-analysis plugin) to the latest version - Create a koha/elasticsearch-icu:7.x image - Set ES 6 as the new default for KTD - Added an alias to be able to still test ES 5 - Added an alias to be able to test ES 7 That was my TODO from the dev meeting. Looking forward to address any issues this could cause. PS: The discussion involved setting SearchEngine to Elasticsearch on misc4dev by default, but I'm not sure there was consensus on that. People present on the meeting, please answer this email with your perceptions. -- Tomás Cohen Arazi Theke Solutions (http://theke.io ) ✆ +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From dcook at prosentient.com.au Thu May 7 03:12:53 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Thu, 7 May 2020 11:12:53 +1000 Subject: [Koha-devel] Adding fonts to Koha for label creator In-Reply-To: References: <05b101d621e2$86ae3e60$940abb20$@prosentient.com.au> <063801d6226a$b60c8580$22259080$@prosentient.com.au> <07a901d62346$e14f1eb0$a3ed5c10$@prosentient.com.au> Message-ID: <084a01d6240c$a2562390$e7026ab0$@prosentient.com.au> Thanks for reviewing the patch and adding that comment, Chris. It is very appreciated. Perhaps Bernardo or someone else will be able to test and sign off. Happy to do more work on this one if necessary. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595 From: Christopher Nighswonger Sent: Wednesday, 6 May 2020 10:36 PM To: David Cook Cc: Bernardo Gonzalez Kriegel ; koha-devel Subject: Re: [Koha-devel] Adding fonts to Koha for label creator The concept of your patch looks great, David. I'm sorry I can't test it at the moment. I did add a comment on your description in order to clarify the purpose of the 12 default fonts. Kind regards, Chris On Tue, May 5, 2020 at 9:37 PM > wrote: Thanks again for your help! I’ve tried your suggestion, and I tried adding options to C4::Creators::Lib with mappings in koha-conf.xml. Both ideas worked. For now, I think I’ll advise people to use your suggestion (and use Javascript to change the labels in the Staff client). I’ve opened a bug report (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25384) to improve this in the future. I think I’ll even have a quick crack at it. Cheers, David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595 From: Koha-devel > On Behalf Of dcook at prosentient.com.au Sent: Tuesday, 5 May 2020 9:21 AM To: 'Christopher Nighswonger' >; 'Bernardo Gonzalez Kriegel' > Cc: 'koha-devel' > Subject: Re: [Koha-devel] Adding fonts to Koha for label creator Thanks Chris and Bernardo for getting back to me so quickly. That’s good to know, although from the user experience point of view I don’t think that it’ll be sufficient, since it would still have the old font name in the web UI. I’ll take a deeper look today and report back. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595 From: Christopher Nighswonger > Sent: Monday, 4 May 2020 10:51 PM To: Bernardo Gonzalez Kriegel > Cc: David Cook >; koha-devel > Subject: Re: [Koha-devel] Adding fonts to Koha for label creator On Mon, May 4, 2020 at 6:25 AM Bernardo Gonzalez Kriegel > wrote: Hi David, How does one add fonts to Koha for the label creator? I’m curious about adding “Arial” ( or rather LiberationSans-Regular.ttf as matched by fc-match) and “Arial Bold” (or rather Roboto-Regular.ttf as matched by fc-match) to the Koha label creator. I see we have a hard-coded list of font types in C4/Creators/Lib.pm. There is also a list of TTF files in etc/koha-conf.xml. Changing paths in koha-conf.xml is enough, replacing entries for H and HB or any other. Hard-coded fonts are effectively defaults. They are installed by a dependency (I don't recall which atm.). Substituting fonts is done as Bernardo pointed out. Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From victor at tuxayo.net Thu May 7 21:42:31 2020 From: victor at tuxayo.net (Victor Grousset/tuxayo) Date: Thu, 7 May 2020 21:42:31 +0200 Subject: [Koha-devel] KTD: ES6 as default, support for ES7 In-Reply-To: References: Message-ID: On 20-05-07 02:46, Tomas Cohen Arazi wrote: > - Update the ES docker images we use (official+icu-analysis plugin) to > the latest version > - Create a koha/elasticsearch-icu:7.x image > - Set ES 6 as the new default for KTD > - Added an alias to be able to still test ES 5 > - Added an alias to be able to test ES 7 tchohen++ :D > PS: The discussion involved setting SearchEngine to Elasticsearch on > misc4dev by default, but I'm not sure there was consensus on that. > People present on the meeting, please answer this email with your > perceptions. Indexing ES by default in KTD: yes Maybe only on ku-es* ? That might add a burden to the setup conf & scripts. About the syspref, let me reread the discussion. Beginning @19:58:17 https://meetings.koha-community.org/2020/development_irc_meeting_6_may_2020.2020-05-06-19.10.log.html So, it seems that we have a mixed usage of ES and Zebra so it's not critical to have ES by default. It was not decided to have ES by default. I forgot to ask if that would still be useful despite not being critical ^^" Maybe I'll bring that back in a future meeting :P Anyway, even without SearchEngine=Elasticsearch when running "ku" is that possible to have that when running ku-es* ? IIUC ku is now the same as ku-es6 So we could make a difference on the syspref. (Is that feasible without too much hassle on the setup conf & scripts? I can take a look.) Then ku will be a sort of ku-zebra compared to ku-es* And ku-es6 will be turn key ES, so it wouldn't be an extra effort to constantly be on ES. Cheers, -- Victor Grousset/tuxayo From dcook at prosentient.com.au Fri May 8 07:19:49 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Fri, 8 May 2020 15:19:49 +1000 Subject: [Koha-devel] limit in subquery causing issues with SQL report? Message-ID: <093701d624f8$4c089ad0$e419d070$@prosentient.com.au> Hi all, I haven't investigated this deep enough to open a Bugzilla report, but has anyone else had the experience of a limit in a subquery causing issues with the surrounding SQL query? I had a subquery in the select statement with a limit of 1, and it was causing my output to only display 1 row, and broke the paging. This was on an older version of Koha. Haven't tried with a newer one yet. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From victor at tuxayo.net Mon May 11 17:08:32 2020 From: victor at tuxayo.net (Victor Grousset/tuxayo) Date: Mon, 11 May 2020 17:08:32 +0200 Subject: [Koha-devel] KTD: Set syspref SearchEngine=Elasticsearch with ku-es* (related also to auto-indexing ES with ku-es*) In-Reply-To: References: Message-ID: <1b63b82e-6f64-e675-9e2d-e5db2c0541b9@tuxayo.net> Hi, Follow up of topic «[Koha-devel] KTD: ES6 as default, support for ES7» A ticket was opened: https://gitlab.com/koha-community/koha-testing-docker/-/issues/176 Feedback welcome on the goals or implementation plan. Otherwise it's just to keep everyone in touch with these things ^^ Cheers, -- Victor Grousset/tuxayo From tomascohen at gmail.com Wed May 13 01:44:10 2020 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Tue, 12 May 2020 20:44:10 -0300 Subject: [Koha-devel] KTD: elasticsearch-icu images Message-ID: The docker images that koha-testing-docker uses for Elastic were manually built until yesterday. >From now on, their build is handled through CI on this new Gitlab project: https://gitlab.com/koha-community/docker/koha-elasticsearch-icu Official base elastic images are not tagged like 5.x, but with specific versions like in 5.6.1. So if you feel some of the versions we handle has been left behind (5.x was 5.5.1 until yesterday) you should send a pull request for the specific branch or file am issue on the mentioned gitlab project. This also applies for other tweaks this images might need, as disabling x-pack or other 'features'. Pull requests and suggestions are welcome :-D Best regards -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From joy at bywatersolutions.com Wed May 13 17:39:12 2020 From: joy at bywatersolutions.com (Joy Nelson) Date: Wed, 13 May 2020 09:39:12 -0600 Subject: [Koha-devel] Maintenance Branches - String Freeze Message-ID: Hello all! String Freeze will go into effect on Friday, May 15, 2020 for the 19.11, 19.05, 18.11 branches. Monthly releases for those branches will be out on Friday, May 22, 2020. Thank you! -- Joy Nelson President, Koha Division ByWater Solutions Support and Consulting for Open Source Software Phone/Fax (888)900-8944 What is Koha? -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Thu May 14 04:43:56 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Thu, 14 May 2020 12:43:56 +1000 Subject: [Koha-devel] Improving usability of Tools > Upload feature w/ Copy Link button Message-ID: <0c3701d62999$8395b550$8ac11ff0$@prosentient.com.au> Hi all, Just sharing that I've posted a patch that adds a "Copy link" button the Tools > Upload feature, which makes it easier to link to files that have been uploaded into Koha. For example, uploading a photo of the library via "Tools > Upload" and then copying the link and pasting it into OpacMainuserBlock in an img element. The patch shows the file URL in a modal so you can manually copy and paste, plus it uses feature detection to see if it can use the Clipboard API (available in modern browsers like Chrome, Firefox, Edge - but not newer IE) to just copy it directly to your browser clipboard. https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25475 Would love to get some feedback on this one. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From kohanews at gmail.com Thu May 14 16:30:21 2020 From: kohanews at gmail.com (Koha Newsletter) Date: Thu, 14 May 2020 07:30:21 -0700 Subject: [Koha-devel] Call for news: April 2020 Koha Newsletter Message-ID: <5A6891C3-B62D-42B9-BD4A-18ED1D644369@gmail.com> I'm collecting news for the April newsletter. Send anything noteworthy to: k o h a news AT gmail dot com News criteria: --------------------------- ** For events **: - Please include dates for past events. If I can't find dates I may not add it. - Announcements for future events with dates T.B.A. are fine ...Eg., Kohacon - For past events , **** one month back is the cut-off ****. * News items can be of any length. * Images are fine * Anything and everything Koha. * Submit by the 26th of the month. If you are working on an interesting project or development related to Koha, please let me know and I'll include it in the development section. Thank you! -- Chad Roseburg Editor, Koha Community Newsletter From dcook at prosentient.com.au Fri May 15 05:45:57 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Fri, 15 May 2020 13:45:57 +1000 Subject: [Koha-devel] Bad koha-common.postinst in 19.11.05 Message-ID: <00cb01d62a6b$578639d0$0692ad70$@prosentient.com.au> Hi all, Anyone else getting this in their 19.11.05 upgrade output: /var/lib/dpkg/info/koha-common.postinst: 155: [: !log4perl_component: unexpected operator Looks like a little typo David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From alexbuckley at catalyst.net.nz Mon May 18 06:34:11 2020 From: alexbuckley at catalyst.net.nz (Alex Buckley) Date: Mon, 18 May 2020 16:34:11 +1200 Subject: [Koha-devel] Bug 19361 - Linking an authorised value category to a field can lose data Message-ID: <14fa8908-160d-dd13-5cc0-ac54b525181b@catalyst.net.nz> Hi all, I'm interested to hear thoughts on bug 19361 ( https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19361 ).  i.e. when a free entry MARC subfield contains data and you link an authorised value category to that subfield then upon editing the bibliographic record the data is lost. Do you think this behaviour should be kept (i.e. when a MARC subfield is linked to an authorised value category then the subfield value must thereafter be an authorised value) or should be fixed to keep the original value? Any thoughts much appreciated! Many thanks, Alex -- Alex Buckley Koha Developer Catalyst IT - Expert Open Source Solutions DDI: +64 4 803 2378 | Mob: +64 22 429 6157 | www.catalyst.net.nz CONFIDENTIALITY NOTICE: This email is intended for the named recipients only. It may contain privileged, confidential or copyright information. If you are not the named recipient, any use, reliance upon, disclosure or copying of this email or its attachments is unauthorised. If you have received this email in error, please reply via email or call +64 4 499 2267. From dcook at prosentient.com.au Mon May 18 09:20:02 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Mon, 18 May 2020 17:20:02 +1000 Subject: [Koha-devel] Debian packaging problems for master and 19.11 Message-ID: <020901d62ce4$bf12bc10$3d383430$@prosentient.com.au> Hi all, You may or may not have noticed, but there are a few outstanding bugs for the Debian packaging for master and 19.11. I've contributed patches to all of them, so I can't really move them forward, but it would be great if other folk could take a look at these ASAP. I know packaging bugs are tough to test. I've spent almost a whole day writing code and testing. But here are some options: https://wiki.koha-community.org/wiki/Building_Debian_Packages_-_The_Easy_Way https://hub.docker.com/r/koha/koha-dpkg https://gitlab.com/minusdavid/koha-deb-builder-docker Bugs: master: Bug 25068 - koha-common build error caused by missing /etc/searchengine https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25068 19.11 (and possibly older versions although I haven't checked): Bug 25485 - TinyMCE broken in Debian package installs https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25485 Bug 25510 - Typo in koha-common.postinst causing shell errors https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25510 Bug 25524 - Debian packages always append to /etc/koha/sites/$site/log4perl.conf https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25524 Cheers, David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From dcook at prosentient.com.au Tue May 19 04:18:30 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Tue, 19 May 2020 12:18:30 +1000 Subject: [Koha-devel] How to make self-referential URLs in Koha Message-ID: <02f601d62d83$c9eb8730$5dc29590$@prosentient.com.au> Hi all, With some recent code, I've been using creating self-referential URL in Koha using CGI->url(), and passing it as a value. With CGI, the URL is correct (ie starting with /cgi-bin/koha). With Plack, it's not, because the OPAC is mounted as "/opac". I worked around this by rewriting the self-referential URL in my code, but I was wondering if anyone else had any thoughts on this. I've noticed there are a few places in Koha where we use CGI->url() and I'm guessing we may have unexpected bugs in Plack-enabled Koha as a result. Of course, one workaround would be to have /opac and /intranet aliases or URL rewriting in Apache, so that the self-referential URLs created by Plack still end up resolving. I wonder if that's the easiest path forward. In the past, I have wondered if we could get rid of "/cgi-bin/koha" as a path prefix all together (especially as cgi-bin scares security tools), but it's so deeply embedded in Koha at this point that it seems a huge task to replace it. Anyway, just throwing that out there. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From oleonard at myacpl.org Tue May 19 15:07:43 2020 From: oleonard at myacpl.org (Owen Leonard) Date: Tue, 19 May 2020 09:07:43 -0400 Subject: [Koha-devel] How to make self-referential URLs in Koha In-Reply-To: <02f601d62d83$c9eb8730$5dc29590$@prosentient.com.au> References: <02f601d62d83$c9eb8730$5dc29590$@prosentient.com.au> Message-ID: > In the past, I have wondered if we could get rid of “/cgi-bin/koha” as a path prefix all together No idea what that would involve (other than search-and-replace in the templates), but from the user's point of view I think it would be a nice improvement. -- Owen -- Web Developer Athens County Public Libraries (740) 737-6006 https://www.myacpl.org From kyle.m.hall at gmail.com Tue May 19 15:19:58 2020 From: kyle.m.hall at gmail.com (Kyle Hall) Date: Tue, 19 May 2020 09:19:58 -0400 Subject: [Koha-devel] How to make self-referential URLs in Koha In-Reply-To: References: <02f601d62d83$c9eb8730$5dc29590$@prosentient.com.au> Message-ID: I think that would also me a great cosmetic enhancement. At the risk of scope creep, we could go a step further by mapping the perl scripts to paths as well, so /cgi-bin/koha/circ/circulation-home.pl could become /circulation/home ( or even just /circulation ) for example. Kyle --- http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) On Tue, May 19, 2020 at 9:08 AM Owen Leonard wrote: > > In the past, I have wondered if we could get rid of “/cgi-bin/koha” as a > path prefix all together > > No idea what that would involve (other than search-and-replace in the > templates), but from the user's point of view I think it would be a > nice improvement. > > -- 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 : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Wed May 20 03:40:17 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Wed, 20 May 2020 11:40:17 +1000 Subject: [Koha-devel] How to make self-referential URLs in Koha In-Reply-To: References: <02f601d62d83$c9eb8730$5dc29590$@prosentient.com.au> Message-ID: <048901d62e47$9d8f53a0$d8adfae0$@prosentient.com.au> So happy to see responses to this ^_^ Owen: It looks like we’d need to do a search and replace in the templates and the code. So I think it could involve a lot of kicking of tires. That said, we could do it incrementally. We could work through it all module by module, and then remove the “/cgi-bin/koha” once we’re sure it’s not referenced anywhere. Kyle: I’m glad you like the idea. I’d like to use the same paths in Apache and Plack (for the sake of the self-referential URLs), so I was thinking “/opac/opac-detail.pl” and “/intranet/circ” (or “/intranet/circulation”). David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595 From: Koha-devel On Behalf Of Kyle Hall Sent: Tuesday, 19 May 2020 11:20 PM To: Owen Leonard Cc: koha-devel Subject: Re: [Koha-devel] How to make self-referential URLs in Koha I think that would also me a great cosmetic enhancement. At the risk of scope creep, we could go a step further by mapping the perl scripts to paths as well, so /cgi-bin/koha/circ/circulation-home.pl could become /circulation/home ( or even just /circulation ) for example. Kyle --- http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) On Tue, May 19, 2020 at 9:08 AM Owen Leonard > wrote: > In the past, I have wondered if we could get rid of “/cgi-bin/koha” as a path prefix all together No idea what that would involve (other than search-and-replace in the templates), but from the user's point of view I think it would be a nice improvement. -- 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 : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From joy at bywatersolutions.com Fri May 22 00:58:21 2020 From: joy at bywatersolutions.com (Joy Nelson) Date: Thu, 21 May 2020 16:58:21 -0600 Subject: [Koha-devel] Koha release 19.11.06 Message-ID: Greetings! The Koha community is proud to announce the release of Koha 19.11.06. It includes 23 enhancements and 122 bug fixes. The full release notes are available at https://koha-community.org/koha-19-11-06-release/ Debian packages will be updated within a few days. -- Joy Nelson President, Koha Division ByWater Solutions Support and Consulting for Open Source Software Phone/Fax (888)900-8944 What is Koha? -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Fri May 22 03:05:18 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Fri, 22 May 2020 11:05:18 +1000 Subject: [Koha-devel] Plugin Security, Plugin Repositories, etc Message-ID: <064801d62fd5$0f449260$2dcdb720$@prosentient.com.au> Hi all, I was doing my morning reading, and noticed that Microsoft have a Windows Package Manager in the works (https://www.theverge.com/2020/5/20/21264739/microsoft-windows-package-manag er-preview-download). While that might not be newsworthy for many people interested in FOSS, you might reconsider when you look at what they're doing for a community metadata repository: https://github.com/microsoft/winget-pkgs Here's an example of a metadata file for 7-zip in that repository: https://github.com/microsoft/winget-pkgs/blob/master/manifests/7Zip/7Zip/19. 0.0.yaml. It includes a URL to the installer and a SHA256 hash for integrity checking. Now according to https://github.com/microsoft/winget-cli, it doesn't look like they're using that Github repository as *the* metadata source repository. Indeed after a bit of digging it appears that the actual default metadata source is https://winget.azureedge.net/cache/source.msix, which contains a SQLite database of metadata (index.db). I think that's an interesting model. We could use http://gitlab.com/koha-community/plugins like https://github.com/microsoft/winget-pkgs where people could submit pull requests to get plugin metadata added to the repository. That would enable there to be a basic level of curation. We could then use something like https://plugins.koha-community.org/ to serve actual metadata (in whatever standardish format we want) to either the Koha web UI (and a Debian package Koha CLI tool like "koha-plugin-get" which make plugin deployment and maintenance potentially easier for sysadmins). There could be an automated process for updating plugins.koha-community.org from http://gitlab.com/koha-community/plugins too. People would be free to point to other plugin metadata repositories (e.g. vendor-specific repos), but by default it would be set up for the Koha Community plugin metadata repository. In terms of security, we could mimic Debian's Apt model of signing the plugin metadata manifest. That way, when setting up a plugin metadata repository in Koha, all you need to do is import a public key/cert to get trusted access to the repo. With the Koha Community repository, we could bake that public key/cert into Koha releases, so it would be seamless for end users. The hardest part of this process would be settling on what metadata manifest format to use for https://plugins.koha-community.org/. Actually, the hardest part would be trying to maintain some kind of backward compatibility. Maybe that's best done by rebranding the current plugin model as "Legacy Plugins" or "Manual Plugins" and then just building a separate web UI for the Repository model. We could re-use the same internals. We could also have separate controls for enabling/disabling "Manual Plugins" vs "Repository Plugins", so that vendors could provide access to plugins via a repository but prevent people from uploading random plugins from the Internet. Anyway, food for thought. I'm happy to do a lot of this work (probably in my personal time rather than work time), but I'd want to make sure there is some buy-in from other vendors and Koha plugin creators first. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From martin.renvoize at ptfs-europe.com Fri May 22 14:45:21 2020 From: martin.renvoize at ptfs-europe.com (Renvoize, Martin) Date: Fri, 22 May 2020 13:45:21 +0100 Subject: [Koha-devel] 20.05.00 Alpha release Message-ID: Hi all, As we've got a number of improvements in the translations and packaging processes in this release I have built an alpha to test prior to a full release in the coming days. If you have time to work through any test upgrades/installs using the nightly Debian repository it would be greatly appreciated to get your feedback. The repository is available at http://apt.kohaaloha.com/koha-nightly/. Things to look out for: * Debian 10 Support! * Installer process and translations of default data * Circulation rules being added correctly during onboarding * Logging and log file permissions Any feedback given over the next few days will be taken into consideration before I build the release notes and officially release to the wider world. Many thanks, *Martin Renvoize* Development Team Manager Community Release Manager (19.11, 20.05) *Phone:* +44 (0) 1483 378728 *Mobile:* +44 (0) 7725 985 636 *Email:* martin.renvoize at ptfs-europe.com *Fax:* +44 (0) 800 756 6384 www.ptfs-europe.com Registered in the United Kingdom No. 06416372 VAT Reg No. 925 7211 30 The information contained in this email message may be privileged, confidential and protected from disclosure. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. If you think that you have received this email message in error, please email the sender at info at ptfs-europe.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From martin.renvoize at ptfs-europe.com Fri May 22 14:50:10 2020 From: martin.renvoize at ptfs-europe.com (Renvoize, Martin) Date: Fri, 22 May 2020 13:50:10 +0100 Subject: [Koha-devel] 20.05.00 Alpha release In-Reply-To: References: Message-ID: As a side note to the above, This is the last call for any release notes improvements.. the draft is available at https://gitlab.com/koha-community/koha-release-notes/-/blob/master/release_notes_20_05_00.md . Please feedback if you spot any omissions or places where clarification is needed. Sponsorship and Mentorship details are welcome additions as I've attempted to go through and add all cases but would not be surprised if I have missed some. Please feedback here before the 27th if you wish to have anything added/updated. Many thanks, *Martin Renvoize* Development Team Manager Community Release Manager (19.11, 20.05) *Phone:* +44 (0) 1483 378728 *Mobile:* +44 (0) 7725 985 636 *Email:* martin.renvoize at ptfs-europe.com *Fax:* +44 (0) 800 756 6384 www.ptfs-europe.com Registered in the United Kingdom No. 06416372 VAT Reg No. 925 7211 30 The information contained in this email message may be privileged, confidential and protected from disclosure. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. If you think that you have received this email message in error, please email the sender at info at ptfs-europe.com On Fri, 22 May 2020 at 13:45, Renvoize, Martin < martin.renvoize at ptfs-europe.com> wrote: > Hi all, > > As we've got a number of improvements in the translations and packaging > processes in this release I have built an alpha to test prior to a full > release in the coming days. > > If you have time to work through any test upgrades/installs using > the nightly Debian repository it would be greatly appreciated to get your > feedback. > > The repository is available at http://apt.kohaaloha.com/koha-nightly/. > > Things to look out for: > > * Debian 10 Support! > * Installer process and translations of default data > * Circulation rules being added correctly during onboarding > * Logging and log file permissions > > Any feedback given over the next few days will be taken into consideration > before I build the release notes and officially release to the wider world. > > Many thanks, > > *Martin Renvoize* > > > > Development Team Manager > > Community Release Manager (19.11, 20.05) > > > *Phone:* +44 (0) 1483 378728 > > *Mobile:* +44 (0) 7725 985 636 > > *Email:* martin.renvoize at ptfs-europe.com > > *Fax:* +44 (0) 800 756 6384 > > > www.ptfs-europe.com > > > > > > > > Registered in the United Kingdom No. 06416372 VAT Reg No. 925 7211 30 > > The information contained in this email message may be privileged, > confidential and protected from disclosure. If you are not the intended > recipient, any dissemination, distribution or copying is strictly > prohibited. If you think that you have received this email message in > error, please email the sender at info at ptfs-europe.com > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonathan.druart at bugs.koha-community.org Fri May 22 15:01:42 2020 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Fri, 22 May 2020 15:01:42 +0200 Subject: [Koha-devel] 20.05.00 Alpha release In-Reply-To: References: Message-ID: If you find a bug the placing a hold on, it's a known bug that will be fixed soon, see bug 25556. Le ven. 22 mai 2020 à 14:45, Renvoize, Martin < martin.renvoize at ptfs-europe.com> a écrit : > Hi all, > > As we've got a number of improvements in the translations and packaging > processes in this release I have built an alpha to test prior to a full > release in the coming days. > > If you have time to work through any test upgrades/installs using > the nightly Debian repository it would be greatly appreciated to get your > feedback. > > The repository is available at http://apt.kohaaloha.com/koha-nightly/. > > Things to look out for: > > * Debian 10 Support! > * Installer process and translations of default data > * Circulation rules being added correctly during onboarding > * Logging and log file permissions > > Any feedback given over the next few days will be taken into consideration > before I build the release notes and officially release to the wider world. > > Many thanks, > > *Martin Renvoize* > > > > Development Team Manager > > Community Release Manager (19.11, 20.05) > > > *Phone:* +44 (0) 1483 378728 > > *Mobile:* +44 (0) 7725 985 636 > > *Email:* martin.renvoize at ptfs-europe.com > > *Fax:* +44 (0) 800 756 6384 > > > www.ptfs-europe.com > > > > > > > > Registered in the United Kingdom No. 06416372 VAT Reg No. 925 7211 30 > > The information contained in this email message may be privileged, > confidential and protected from disclosure. If you are not the intended > recipient, any dissemination, distribution or copying is strictly > prohibited. If you think that you have received this email message in > error, please email the sender at info at ptfs-europe.com > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mik at adminkuhn.ch Wed May 27 14:28:31 2020 From: mik at adminkuhn.ch (Michael Kuhn) Date: Wed, 27 May 2020 14:28:31 +0200 Subject: [Koha-devel] Bad koha-common.postinst in 19.11.05 In-Reply-To: <00cb01d62a6b$578639d0$0692ad70$@prosentient.com.au> References: <00cb01d62a6b$578639d0$0692ad70$@prosentient.com.au> Message-ID: <52ee51e9-8e60-7d67-9fb4-a4665f6aa5d8@adminkuhn.ch> Hi David > Anyone else getting this in their 19.11.05 upgrade output: > > /var/lib/dpkg/info/koha-common.postinst: 155: [: !log4perl_component: > unexpected operator > > Looks like a little typo Yes, when updating from Koha 18.11.01 to 19.11.05 using "apt-get install koha-common" I just got the following lines at the end of the screen output: ... Connection to the memcached servers '__MEMCACHED_SERVERS__' failed. Are the unix socket permissions set properly? Is the host reachable? If you ignore this warning, you will face performance issues Updated the de-DE translations. /var/lib/dpkg/info/koha-common.postinst: 155: [: !log4perl_component: unexpected operator /var/lib/dpkg/info/koha-common.postinst: 155: [: !log4perl_component: unexpected operator insserv: warning: current start runlevel(s) (empty) of script `koha-common' overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `koha-common' overrides LSB defaults (0 1 6). Processing triggers for systemd (232-25+deb9u12) ... Use of uninitialized value in concatenation (.) or string at /usr/share/perl5/NeedRestart/Interp/Perl.pm line 170. Use of uninitialized value in list assignment at /usr/share/perl5/NeedRestart/Interp/Perl.pm line 170. Scanning processes... Scanning linux images... Running kernel seems to be up-to-date. No services need to be restarted. No containers need to be restarted. No user sessions are running outdated binaries. Though, I don't know what it means or if I should do something about it. Best wishes: Michael -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 · E mik at adminkuhn.ch · W www.adminkuhn.ch From jonathan.druart at bugs.koha-community.org Wed May 27 14:36:16 2020 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Wed, 27 May 2020 14:36:16 +0200 Subject: [Koha-devel] Bad koha-common.postinst in 19.11.05 In-Reply-To: <52ee51e9-8e60-7d67-9fb4-a4665f6aa5d8@adminkuhn.ch> References: <00cb01d62a6b$578639d0$0692ad70$@prosentient.com.au> <52ee51e9-8e60-7d67-9fb4-a4665f6aa5d8@adminkuhn.ch> Message-ID: > /var/lib/dpkg/info/koha-common.postinst: 155: [: !log4perl_component: unexpected operator It's a know bug (25510), it is fixed in the next stable releases. The memcached warning can be ignored (see bug 22217, not fixed yet). Le mer. 27 mai 2020 à 14:28, Michael Kuhn a écrit : > > Hi David > > > Anyone else getting this in their 19.11.05 upgrade output: > > > > /var/lib/dpkg/info/koha-common.postinst: 155: [: !log4perl_component: > > unexpected operator > > > > Looks like a little typo > > Yes, when updating from Koha 18.11.01 to 19.11.05 using "apt-get install > koha-common" I just got the following lines at the end of the screen output: > > ... > Connection to the memcached servers '__MEMCACHED_SERVERS__' failed. Are > the unix socket permissions set properly? Is the host reachable? > If you ignore this warning, you will face performance issues > Updated the de-DE translations. > /var/lib/dpkg/info/koha-common.postinst: 155: [: !log4perl_component: > unexpected operator > /var/lib/dpkg/info/koha-common.postinst: 155: [: !log4perl_component: > unexpected operator > insserv: warning: current start runlevel(s) (empty) of script > `koha-common' overrides LSB defaults (2 3 4 5). > insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script > `koha-common' overrides LSB defaults (0 1 6). > Processing triggers for systemd (232-25+deb9u12) ... > Use of uninitialized value in concatenation (.) or string at > /usr/share/perl5/NeedRestart/Interp/Perl.pm line 170. > Use of uninitialized value in list assignment at > /usr/share/perl5/NeedRestart/Interp/Perl.pm line 170. > Scanning processes... > > Scanning linux images... > > Running kernel seems to be up-to-date. > No services need to be restarted. > No containers need to be restarted. > No user sessions are running outdated binaries. > > Though, I don't know what it means or if I should do something about it. > > Best wishes: Michael > -- > Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis > Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz > T 0041 (0)61 261 55 61 · E mik at adminkuhn.ch · W www.adminkuhn.ch > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ From dcook at prosentient.com.au Thu May 28 01:34:44 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Thu, 28 May 2020 09:34:44 +1000 Subject: [Koha-devel] Alerting users to breaking changes / backwards incompatibility Message-ID: <0a0801d6347f$66d6c350$348449f0$@prosentient.com.au> Hi all, I was just thinking how a lot of SQL reports will return unexpected results when we merge the deleted* tables with their live/active counterparts. What do people think about a modal popup in the reports (on a per user basis) alerting them to how they may need to update their reports following an upgrade which changes reporting behaviour? I'm not 100% sure how we'd do it, but it's something we could re-use through much of the Koha staff client. Or maybe we could raise a flag in the borrower row during an upgrade, and when they log into the staff client, they're presented with a "You need to know." kind of page. After all, users aren't going to be reading release notes, and sysadmins doing upgrades aren't necessarily going to do the best job communicating to every single staff user about what they need to know in an upgrade. But that's easier said than done too, especially when you're upgrading past multiple versions. Anyway, just putting it out there. As you can see, I haven't thought about it too deeply yet. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From tomascohen at gmail.com Thu May 28 01:53:27 2020 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Wed, 27 May 2020 20:53:27 -0300 Subject: [Koha-devel] Alerting users to breaking changes / backwards incompatibility In-Reply-To: <0a0801d6347f$66d6c350$348449f0$@prosentient.com.au> References: <0a0801d6347f$66d6c350$348449f0$@prosentient.com.au> Message-ID: We already do something similar with the biblio_metadata table. El mié., 27 de mayo de 2020 20:35, escribió: > Hi all, > > > > I was just thinking how a lot of SQL reports will return unexpected > results when we merge the deleted* tables with their live/active > counterparts. > > > > What do people think about a modal popup in the reports (on a per user > basis) alerting them to how they may need to update their reports following > an upgrade which changes reporting behaviour? > > I’m not 100% sure how we’d do it, but it’s something we could re-use > through much of the Koha staff client. > > > > Or maybe we could raise a flag in the borrower row during an upgrade, and > when they log into the staff client, they’re presented with a “You need to > know…” kind of page. After all, users aren’t going to be reading release > notes, and sysadmins doing upgrades aren’t necessarily going to do the best > job communicating to every single staff user about what they need to know > in an upgrade. > > > > But that’s easier said than done too, especially when you’re upgrading > past multiple versions. > > > > Anyway, just putting it out there. As you can see, I haven’t thought about > it too deeply yet. > > > > David Cook > > Systems Librarian > > Prosentient Systems > > 72/330 Wattle St > > Ultimo, NSW 2007 > > 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 : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Thu May 28 02:23:05 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Thu, 28 May 2020 10:23:05 +1000 Subject: [Koha-devel] Alerting users to breaking changes / backwards incompatibility In-Reply-To: References: <0a0801d6347f$66d6c350$348449f0$@prosentient.com.au> Message-ID: <0a1601d63486$27e947b0$77bbd710$@prosentient.com.au> Oh great. I don’t think I’ve seen that? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595 From: Tomas Cohen Arazi Sent: Thursday, 28 May 2020 9:53 AM To: David Cook Cc: koha-devel Subject: Re: [Koha-devel] Alerting users to breaking changes / backwards incompatibility We already do something similar with the biblio_metadata table. El mié., 27 de mayo de 2020 20:35, > escribió: Hi all, I was just thinking how a lot of SQL reports will return unexpected results when we merge the deleted* tables with their live/active counterparts. What do people think about a modal popup in the reports (on a per user basis) alerting them to how they may need to update their reports following an upgrade which changes reporting behaviour? I’m not 100% sure how we’d do it, but it’s something we could re-use through much of the Koha staff client. Or maybe we could raise a flag in the borrower row during an upgrade, and when they log into the staff client, they’re presented with a “You need to know…” kind of page. After all, users aren’t going to be reading release notes, and sysadmins doing upgrades aren’t necessarily going to do the best job communicating to every single staff user about what they need to know in an upgrade. But that’s easier said than done too, especially when you’re upgrading past multiple versions. Anyway, just putting it out there. As you can see, I haven’t thought about it too deeply yet. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 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 : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From mtj at kohaaloha.com Thu May 28 05:59:52 2020 From: mtj at kohaaloha.com (Mason James) Date: Thu, 28 May 2020 15:59:52 +1200 Subject: [Koha-devel] Bad koha-common.postinst in 19.11.05 In-Reply-To: References: <00cb01d62a6b$578639d0$0692ad70$@prosentient.com.au> <52ee51e9-8e60-7d67-9fb4-a4665f6aa5d8@adminkuhn.ch> Message-ID: <8493abde-fb20-0707-35b9-0e65b171b00b@kohaaloha.com> hi Michael Koha 19.11.06 contains the fix (bz-25510), and is now available On 28/05/20 12:36 am, Jonathan Druart wrote: >> /var/lib/dpkg/info/koha-common.postinst: 155: [: !log4perl_component: unexpected operator > It's a know bug (25510), it is fixed in the next stable releases. > > The memcached warning can be ignored (see bug 22217, not fixed yet). > > > Le mer. 27 mai 2020 à 14:28, Michael Kuhn a écrit : >> Hi David >> >> > Anyone else getting this in their 19.11.05 upgrade output: >> > >> > /var/lib/dpkg/info/koha-common.postinst: 155: [: !log4perl_component: >> > unexpected operator >> > >> > Looks like a little typo >> >> Yes, when updating from Koha 18.11.01 to 19.11.05 using "apt-get install >> koha-common" I just got the following lines at the end of the screen output: >> >> ... >> Connection to the memcached servers '__MEMCACHED_SERVERS__' failed. Are >> the unix socket permissions set properly? Is the host reachable? >> If you ignore this warning, you will face performance issues >> Updated the de-DE translations. >> /var/lib/dpkg/info/koha-common.postinst: 155: [: !log4perl_component: >> unexpected operator >> /var/lib/dpkg/info/koha-common.postinst: 155: [: !log4perl_component: >> unexpected operator >> insserv: warning: current start runlevel(s) (empty) of script >> `koha-common' overrides LSB defaults (2 3 4 5). >> insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script >> `koha-common' overrides LSB defaults (0 1 6). >> Processing triggers for systemd (232-25+deb9u12) ... >> Use of uninitialized value in concatenation (.) or string at >> /usr/share/perl5/NeedRestart/Interp/Perl.pm line 170. >> Use of uninitialized value in list assignment at >> /usr/share/perl5/NeedRestart/Interp/Perl.pm line 170. >> Scanning processes... >> >> Scanning linux images... >> >> Running kernel seems to be up-to-date. >> No services need to be restarted. >> No containers need to be restarted. >> No user sessions are running outdated binaries. >> >> Though, I don't know what it means or if I should do something about it. >> >> Best wishes: Michael >> -- >> Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis >> Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz >> T 0041 (0)61 261 55 61 · E mik at adminkuhn.ch · W www.adminkuhn.ch >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at lists.koha-community.org >> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >> website : http://www.koha-community.org/ >> git : http://git.koha-community.org/ >> bugs : http://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 : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ From michael.hafen at washk12.org Thu May 28 20:51:57 2020 From: michael.hafen at washk12.org (Michael Hafen (TECH)) Date: Thu, 28 May 2020 12:51:57 -0600 Subject: [Koha-devel] Alerting users to breaking changes / backwards incompatibility In-Reply-To: <0a1601d63486$27e947b0$77bbd710$@prosentient.com.au> References: <0a0801d6347f$66d6c350$348449f0$@prosentient.com.au> <0a1601d63486$27e947b0$77bbd710$@prosentient.com.au> Message-ID: What about the upgrade offering to add a news entry to the staff interface? I'm all for using existing functions :) On Wed, May 27, 2020 at 6:23 PM wrote: > Oh great. I don’t think I’ve seen that? > > > > David Cook > > Systems Librarian > > Prosentient Systems > > 72/330 Wattle St > > Ultimo, NSW 2007 > > Australia > > > > Office: 02 9212 0899 > > Online: 02 8005 0595 > > > > *From:* Tomas Cohen Arazi > *Sent:* Thursday, 28 May 2020 9:53 AM > *To:* David Cook > *Cc:* koha-devel > *Subject:* Re: [Koha-devel] Alerting users to breaking changes / > backwards incompatibility > > > > We already do something similar with the biblio_metadata table. > > > > El mié., 27 de mayo de 2020 20:35, escribió: > > Hi all, > > > > I was just thinking how a lot of SQL reports will return unexpected > results when we merge the deleted* tables with their live/active > counterparts. > > > > What do people think about a modal popup in the reports (on a per user > basis) alerting them to how they may need to update their reports following > an upgrade which changes reporting behaviour? > > I’m not 100% sure how we’d do it, but it’s something we could re-use > through much of the Koha staff client. > > > > Or maybe we could raise a flag in the borrower row during an upgrade, and > when they log into the staff client, they’re presented with a “You need to > know…” kind of page. After all, users aren’t going to be reading release > notes, and sysadmins doing upgrades aren’t necessarily going to do the best > job communicating to every single staff user about what they need to know > in an upgrade. > > > > But that’s easier said than done too, especially when you’re upgrading > past multiple versions. > > > > Anyway, just putting it out there. As you can see, I haven’t thought about > it too deeply yet. > > > > David Cook > > Systems Librarian > > Prosentient Systems > > 72/330 Wattle St > > Ultimo, NSW 2007 > > 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 : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://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 : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > -- Michael Hafen Washington County School District Technology Department Systems Analyst -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomascohen at gmail.com Thu May 28 22:39:15 2020 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Thu, 28 May 2020 17:39:15 -0300 Subject: [Koha-devel] Alerting users to breaking changes / backwards incompatibility In-Reply-To: <0a1601d63486$27e947b0$77bbd710$@prosentient.com.au> References: <0a0801d6347f$66d6c350$348449f0$@prosentient.com.au> <0a1601d63486$27e947b0$77bbd710$@prosentient.com.au> Message-ID: Create an SQL report with the following query: SELECT COUNT(marcxml) FROM biblioitems; And then go to the reports list. You will notice it tells you this: https://snipboard.io/5wjCUc.jpg El mié., 27 may. 2020 a las 21:23, escribió: > Oh great. I don’t think I’ve seen that? > > > > David Cook > > Systems Librarian > > Prosentient Systems > > 72/330 Wattle St > > Ultimo, NSW 2007 > > Australia > > > > Office: 02 9212 0899 > > Online: 02 8005 0595 > > > > *From:* Tomas Cohen Arazi > *Sent:* Thursday, 28 May 2020 9:53 AM > *To:* David Cook > *Cc:* koha-devel > *Subject:* Re: [Koha-devel] Alerting users to breaking changes / > backwards incompatibility > > > > We already do something similar with the biblio_metadata table. > > > > El mié., 27 de mayo de 2020 20:35, escribió: > > Hi all, > > > > I was just thinking how a lot of SQL reports will return unexpected > results when we merge the deleted* tables with their live/active > counterparts. > > > > What do people think about a modal popup in the reports (on a per user > basis) alerting them to how they may need to update their reports following > an upgrade which changes reporting behaviour? > > I’m not 100% sure how we’d do it, but it’s something we could re-use > through much of the Koha staff client. > > > > Or maybe we could raise a flag in the borrower row during an upgrade, and > when they log into the staff client, they’re presented with a “You need to > know…” kind of page. After all, users aren’t going to be reading release > notes, and sysadmins doing upgrades aren’t necessarily going to do the best > job communicating to every single staff user about what they need to know > in an upgrade. > > > > But that’s easier said than done too, especially when you’re upgrading > past multiple versions. > > > > Anyway, just putting it out there. As you can see, I haven’t thought about > it too deeply yet. > > > > David Cook > > Systems Librarian > > Prosentient Systems > > 72/330 Wattle St > > Ultimo, NSW 2007 > > 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 : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > > -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Fri May 29 01:03:17 2020 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Fri, 29 May 2020 09:03:17 +1000 Subject: [Koha-devel] Alerting users to breaking changes / backwards incompatibility In-Reply-To: References: <0a0801d6347f$66d6c350$348449f0$@prosentient.com.au> <0a1601d63486$27e947b0$77bbd710$@prosentient.com.au> Message-ID: <005501d63544$2cd31e90$86795bb0$@prosentient.com.au> Wonderful! Y’all are way ahead of me. Glad it’s already been done. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595 From: Tomas Cohen Arazi Sent: Friday, 29 May 2020 6:39 AM To: David Cook Cc: koha-devel Subject: Re: [Koha-devel] Alerting users to breaking changes / backwards incompatibility Create an SQL report with the following query: SELECT COUNT(marcxml) FROM biblioitems; And then go to the reports list. You will notice it tells you this: https://snipboard.io/5wjCUc.jpg El mié., 27 may. 2020 a las 21:23, > escribió: Oh great. I don’t think I’ve seen that? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595 From: Tomas Cohen Arazi > Sent: Thursday, 28 May 2020 9:53 AM To: David Cook > Cc: koha-devel > Subject: Re: [Koha-devel] Alerting users to breaking changes / backwards incompatibility We already do something similar with the biblio_metadata table. El mié., 27 de mayo de 2020 20:35, > escribió: Hi all, I was just thinking how a lot of SQL reports will return unexpected results when we merge the deleted* tables with their live/active counterparts. What do people think about a modal popup in the reports (on a per user basis) alerting them to how they may need to update their reports following an upgrade which changes reporting behaviour? I’m not 100% sure how we’d do it, but it’s something we could re-use through much of the Koha staff client. Or maybe we could raise a flag in the borrower row during an upgrade, and when they log into the staff client, they’re presented with a “You need to know…” kind of page. After all, users aren’t going to be reading release notes, and sysadmins doing upgrades aren’t necessarily going to do the best job communicating to every single staff user about what they need to know in an upgrade. But that’s easier said than done too, especially when you’re upgrading past multiple versions. Anyway, just putting it out there. As you can see, I haven’t thought about it too deeply yet. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 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 : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ -- Tomás Cohen Arazi Theke Solutions (http://theke.io ) ✆ +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 484 bytes Desc: not available URL: From kohanews at gmail.com Sat May 30 04:29:44 2020 From: kohanews at gmail.com (Koha Newsletter) Date: Fri, 29 May 2020 19:29:44 -0700 Subject: [Koha-devel] Koha Community Newsletter: May 2020 Message-ID: <01C10530-EEFC-4248-B0B4-EBE45D280151@gmail.com> The Koha Community Newsletter for May 2020 is here: https://koha-community.org/koha-community-newsletter-may-2020/ Many thanks to the folks who submitted articles and news to this month's newsletter. Please feel free to email me with any corrections or suggestions. -- Chad Roseburg Editor, Koha Community Newsletter From martin.renvoize at ptfs-europe.com Sun May 31 23:31:56 2020 From: martin.renvoize at ptfs-europe.com (Renvoize, Martin) Date: Sun, 31 May 2020 22:31:56 +0100 Subject: [Koha-devel] Koha 20.05.00 Released Message-ID: Hello Everyone, It is with great pleasure I am able to announce the release of Koha 20.05, a major release of the Koha open source integrated library system. This release includes 13 new features, 275 enhancements, 592 bugfixes. Please see the release notes for further details: https://koha-community.org/koha-20-05-released/ It is the work of many librarians, developers and community members who have donated a huge number of hours to keep the project moving forward. My thanks go out to all who contributed. This is my final release as a release manager and I'd like to extend my personal thanks to a fantastic team. Special thanks go out to Mason James, Tomas Cohen and Jonathan Druart, all who stepped in during the final weeks of the cycle to ensure the packaging would work as expected for Debian 10 as well as finding and fixing bugs right up to the very end of the cycle. I cannot overstate what a great team I've had behind me this cycle and I feel we have achieved a huge amount. Debian packages, will be available on the standard community repositories soon having been tested via our beta channels for the past two weeks. Many thanks, *Martin Renvoize* Development Team Manager Community Release Manager (19.11, 20.05) *Phone:* +44 (0) 1483 378728 *Mobile:* +44 (0) 7725 985 636 *Email:* martin.renvoize at ptfs-europe.com *Fax:* +44 (0) 800 756 6384 www.ptfs-europe.com Registered in the United Kingdom No. 06416372 VAT Reg No. 925 7211 30 The information contained in this email message may be privileged, confidential and protected from disclosure. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. If you think that you have received this email message in error, please email the sender at info at ptfs-europe.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From hagud at orex.es Sun May 31 23:36:41 2020 From: hagud at orex.es (Hugo Agud Andreu) Date: Sun, 31 May 2020 21:36:41 +0000 Subject: [Koha-devel] Koha 20.05.00 Released In-Reply-To: References: Message-ID: Awesome! Congrats!!! Obtener Outlook para iOS ________________________________ De: Koha-devel en nombre de Renvoize, Martin Enviado: Sunday, May 31, 2020 11:31:56 PM Para: Koha ; Koha Devel Asunto: [Koha-devel] Koha 20.05.00 Released Hello Everyone, It is with great pleasure I am able to announce the release of Koha 20.05, a major release of the Koha open source integrated library system. This release includes 13 new features, 275 enhancements, 592 bugfixes. Please see the release notes for further details: https://koha-community.org/koha-20-05-released/ It is the work of many librarians, developers and community members who have donated a huge number of hours to keep the project moving forward. My thanks go out to all who contributed. This is my final release as a release manager and I'd like to extend my personal thanks to a fantastic team. Special thanks go out to Mason James, Tomas Cohen and Jonathan Druart, all who stepped in during the final weeks of the cycle to ensure the packaging would work as expected for Debian 10 as well as finding and fixing bugs right up to the very end of the cycle. I cannot overstate what a great team I've had behind me this cycle and I feel we have achieved a huge amount. Debian packages, will be available on the standard community repositories soon having been tested via our beta channels for the past two weeks. Many thanks, Martin Renvoize [https://www.ptfs-europe.com/wp-content/uploads/2018/10/ptfs-logo-full-email-sig.png] Development Team Manager Community Release Manager (19.11, 20.05) Phone: +44 (0) 1483 378728 Mobile: +44 (0) 7725 985 636 Email: martin.renvoize at ptfs-europe.com Fax: +44 (0) 800 756 6384 www.ptfs-europe.com Registered in the United Kingdom No. 06416372 VAT Reg No. 925 7211 30 The information contained in this email message may be privileged, confidential and protected from disclosure. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. If you think that you have received this email message in error, please email the sender at info at ptfs-europe.com -------------- next part -------------- An HTML attachment was scrubbed... URL: