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

Re: [Koha-devel] [Koha] Circulation Rules: Parent and Child Item Type
by Ms. Naveen Ali 22 Aug '22

22 Aug '22

Thank you very much Caroline for the response and Katrin for the confirmation. Is it possible to batch update multiple circulation rules of one library? The problem I am facing is that I have around 60+ item types for which lending rule (with hard due date) has to be updated every semester. I just need to update the hard due date. It would be very convenient if I could do it in one go. With best regards, Naveen Ali ITM-JE (EAKL) Inst Representative for HEC Digital Library Resources. NEDUET, Karachi. ----- Original Message ----- From: "Katrin Fischer" <katrin.fischer.83(a)web.de> To: koha(a)lists.katipo.co.nz Sent: Thursday, 18 August, 2022 3:58:03 PM Subject: Re: [Koha] Circulation Rules: Parent and Child Item Type > > As far as I know, the rule for the parent type only applies to > children for the "checkouts allowed" rule. This may have changed > since, but when the parent/child item types were introduced, it was > like this. I believe this is still correct! Katrin _______________________________________________ Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

2 1

Re: [Koha-devel] Mojolicious controllers for Koha plugins
by dcook＠prosentient.com.au 18 Aug '22

18 Aug '22

Thanks, Kyle! Leveraging some past work, I was able to put something together fairly quickly. I’ve posted it to https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31380 It has two dependent bug reports but I’ve posted patches for them too, and they’re fairly straightforward. It should be very easy to test, so hopefully you can have a look and let me know what you think. 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: Kyle Hall <kyle(a)bywatersolutions.com> Sent: Tuesday, 16 August 2022 9:27 PM To: dcook(a)prosentient.com.au Cc: koha-devel(a)lists.koha-community.org; Tomas Cohen Arazi <tomascohen(a)theke.io>; Renvoize, Martin <martin.renvoize(a)ptfs-europe.com> Subject: Re: Mojolicious controllers for Koha plugins That sounds great to me David! I'll 100% assist you with testing and qa! On Tue, Aug 16, 2022 at 3:42 AM <dcook(a)prosentient.com.au <mailto:dcook@prosentient.com.au> > wrote: Hi all, I was just writing a Koha plugin to do a big data export, but I realize that it’s probably going to timeout, because Koha plugins run under Plack::App::CGIBin which buffers the entire response before it returns it to Apache to return to the client browser. It’s the reason Koha uses CGI instead of Plack for export.pl <http://export.pl> While we can use Mojolicious controllers with Koha plugins when it adds REST API endpoints, we can’t do that for Koha plugins themselves. This is a topic that I’ve touched on before, and there are challenges when it comes to Authentication and Templates, but they’re solvable challenges: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26791 “Build Mojolicious controller replacement for export.pl <http://export.pl> ” https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28325 “Build Mojolicious controller replacement for tools-home.pl <http://tools-home.pl> ” We could just start by supporting “tool” and “report” with the Mojolicious controllers, and that would just mean plugins-home.pl <http://plugins-home.pl> detecting that there is Mojolicious support in that plugin, and then building a URL to “/staff/plugins/run” instead of “/cgi-bin/koha/plugins/run.pl <http://run.pl> ” for instance. That Mojolicious controller would really just need to check authentication/authorization, which is very doable with a fairly minor refactor. If I could get the support of just a couple other people, I’d be happy to do a lot of the authoring (or testing or whatever needs to be done just to get it done). By using Mojolicious controllers for select plugins, we’d also be able to shake out any issues without causing any regressions in core Koha, and then hopefully be able to start refactoring core Koha too… Anyways, please give it some consideration, and ask me if you have any questions. I’ll be looking more into export problems tomorrow, so I might end up going a different route for the sake of time in the short-term, but I think we should still be looking at shifting away from CGI and Plack::App::CGIBin due to their limitations… 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 -- Kyle M. Hall Loose Cannon, ByWater Solutions <mailto:kyle@bywatersolutions.com> kyle(a)bywatersolutions.com <http://bywatersolutions.com/> https://bywatersolutions.com <http://bywatersolutions.com/what-is-koha/> What is Koha?

1 0

Re: [Koha-devel] Mojolicious controllers for Koha plugins
by dcook＠prosentient.com.au 17 Aug '22

17 Aug '22

Thanks, Kyle! I’ll look at updating the patches from Bug 28325 and post new work for this at https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31380 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: Kyle Hall <kyle(a)bywatersolutions.com> Sent: Tuesday, 16 August 2022 9:27 PM To: dcook(a)prosentient.com.au Cc: koha-devel(a)lists.koha-community.org; Tomas Cohen Arazi <tomascohen(a)theke.io>; Renvoize, Martin <martin.renvoize(a)ptfs-europe.com> Subject: Re: Mojolicious controllers for Koha plugins That sounds great to me David! I'll 100% assist you with testing and qa! On Tue, Aug 16, 2022 at 3:42 AM <dcook(a)prosentient.com.au <mailto:dcook@prosentient.com.au> > wrote: Hi all, I was just writing a Koha plugin to do a big data export, but I realize that it’s probably going to timeout, because Koha plugins run under Plack::App::CGIBin which buffers the entire response before it returns it to Apache to return to the client browser. It’s the reason Koha uses CGI instead of Plack for export.pl <http://export.pl> While we can use Mojolicious controllers with Koha plugins when it adds REST API endpoints, we can’t do that for Koha plugins themselves. This is a topic that I’ve touched on before, and there are challenges when it comes to Authentication and Templates, but they’re solvable challenges: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26791 “Build Mojolicious controller replacement for export.pl <http://export.pl> ” https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28325 “Build Mojolicious controller replacement for tools-home.pl <http://tools-home.pl> ” We could just start by supporting “tool” and “report” with the Mojolicious controllers, and that would just mean plugins-home.pl <http://plugins-home.pl> detecting that there is Mojolicious support in that plugin, and then building a URL to “/staff/plugins/run” instead of “/cgi-bin/koha/plugins/run.pl <http://run.pl> ” for instance. That Mojolicious controller would really just need to check authentication/authorization, which is very doable with a fairly minor refactor. If I could get the support of just a couple other people, I’d be happy to do a lot of the authoring (or testing or whatever needs to be done just to get it done). By using Mojolicious controllers for select plugins, we’d also be able to shake out any issues without causing any regressions in core Koha, and then hopefully be able to start refactoring core Koha too… Anyways, please give it some consideration, and ask me if you have any questions. I’ll be looking more into export problems tomorrow, so I might end up going a different route for the sake of time in the short-term, but I think we should still be looking at shifting away from CGI and Plack::App::CGIBin due to their limitations… 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 -- Kyle M. Hall Loose Cannon, ByWater Solutions <mailto:kyle@bywatersolutions.com> kyle(a)bywatersolutions.com <http://bywatersolutions.com/> https://bywatersolutions.com <http://bywatersolutions.com/what-is-koha/> What is Koha?

1 0

Mojolicious controllers for Koha plugins
by dcook＠prosentient.com.au 16 Aug '22

16 Aug '22

Hi all, I was just writing a Koha plugin to do a big data export, but I realize that it's probably going to timeout, because Koha plugins run under Plack::App::CGIBin which buffers the entire response before it returns it to Apache to return to the client browser. It's the reason Koha uses CGI instead of Plack for export.pl While we can use Mojolicious controllers with Koha plugins when it adds REST API endpoints, we can't do that for Koha plugins themselves. This is a topic that I've touched on before, and there are challenges when it comes to Authentication and Templates, but they're solvable challenges: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26791 "Build Mojolicious controller replacement for export.pl" https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28325 "Build Mojolicious controller replacement for tools-home.pl" We could just start by supporting "tool" and "report" with the Mojolicious controllers, and that would just mean plugins-home.pl detecting that there is Mojolicious support in that plugin, and then building a URL to "/staff/plugins/run" instead of "/cgi-bin/koha/plugins/run.pl" for instance. That Mojolicious controller would really just need to check authentication/authorization, which is very doable with a fairly minor refactor. If I could get the support of just a couple other people, I'd be happy to do a lot of the authoring (or testing or whatever needs to be done just to get it done). By using Mojolicious controllers for select plugins, we'd also be able to shake out any issues without causing any regressions in core Koha, and then hopefully be able to start refactoring core Koha too. Anyways, please give it some consideration, and ask me if you have any questions. I'll be looking more into export problems tomorrow, so I might end up going a different route for the sake of time in the short-term, but I think we should still be looking at shifting away from CGI and Plack::App::CGIBin due to their limitations. David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595

1 0

Serving Intranet from a subpath
by Thomas Klausner 15 Aug '22

15 Aug '22

Hi! (I'm sending this to koha-devel because I guess it's too technical for the general list?) We are running running the "Intranet" inside an actual intranet (i.e. inside a VPN). But this Koha instance is also hosting a related Library whose staff cannot access the VPN. For various reasons it is not possible to mount Koha at it's own domain, so we must make it available at a sub-path (something like "https://www.example.com/foo/koha") For the OPAC, I already implemented a hacky Plack Middleware that does some rather ugly rewriting or URLs and HTML (ughh..). While we could do the same for Intranet, I first wanted to check if it is maybe already possible to mount it under a subpath, i.e. have an Apache use something like ProxyPass /foo/koha/index.html ... ProxyPass /foo/koha/cgi-bin/koha ... Now, while this actually works, the pages returned do not, as all the links they contain point to /cgi-bin/koha (i.e., they loose the mount point and generate bad links). The usual way to solve this is via something like https://metacpan.org/pod/Plack::Middleware::ReverseProxyPath But for this work, two things (one small, one not) have to be changed: * the plack app (i.e. Koha) needs to honor some HTTP Header ENV vars (X_FORWARDED_SCRIPT_NAME, X_TRAVERSAL_PATH) * and all links generated by the app need to also honor those vars. The usual way for the latter is to *not* generate links by concatenating path fragments or hardcoded them in templates (which seems to be what Koha is doing), but to use a function/method to generate all links (to html pages, static assets and endpoints) So for example in a template like prog/en/modules/cataloguing/addbooks.tt we find: <a href="/cgi-bin/koha/mainpage.pl">Home</a> This would need to be changed to <a href=uri_for("/cgi-bin/koha/mainpage.pl")>Home</a> and uri_for needs to take a look at the ENV and fix the link accordingly. (The ugly workaround I am using in an OPAC is to use a Middleware to change the HTML after it's generated by Koha but before it is send to the client. shudder...) So on the one hand this seems to be a small change, but to work it needs to touch ALL templates. (and it will be hard to automatically identify all link-ish text in the templates (href, src, maybe sometimes the url is generated in a template, ...) Another approach would be to set the mount-point into <base href="/foo/koha"> https://developer.mozilla.org/en-US/docs/Web/HTML/Element/base But we would still need to change all the links to relative links, as `base` will ignore absolute links, which is what Koha is using now. though maybe the regex to replace the code is a bit easier (s{/cgi-bin}{cgi-bin}) as it does have to fiddle with quotes etc. Our customer is willing to do the work to implement this (probably also in OPAC), but only if the change will be accepted upstream and be usable by the end of this year (i.e. 22.11). Shall we try to tackle this? Or will this massive change never be accepted? If there is interest, I guess the next step is to open a bug... Greetings, domm -- #!/usr/bin/perl https://domm.plix.at for(ref bless{},just'another'perl'hacker){s-:+-$"-g&&print$_.$/}

2 3

Call for news - Newsletter August 2022
by Michael Kuhn 14 Aug '22

14 Aug '22

Hi I'm collecting news for the August 2022 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 -- 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(a)adminkuhn.ch · W www.adminkuhn.ch

1 0

String Freeze Notice
by Joy Nelson 12 Aug '22

12 Aug '22

Greetings! Just a quick note that string freeze will go into effect at the end of day 12/16/2019 for the maintenance branches. Maintenance releases scheduled for the 23rd. Translations can begin on the 17th. Thanks! -- Joy Nelson President, Koha Division ByWater Solutions <http://bywatersolutions.com> Support and Consulting for Open Source Software Phone/Fax (888)900-8944 What is Koha? <http://bywatersolutions.com/what-is-koha/>

3 3

Using Template::Toolkit WRAPPER templates with Koha Plugins
by dcook＠prosentient.com.au 11 Aug '22

11 Aug '22

Hi all, I'm creating a Koha plugin and I'm going to need several different template pages. Rather than copying and pasting boilerplate into each file, I just created 1 wrapper file and then I include that in each of my individual template pages. For the templates and code, you can take a look at https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31339 I think it would be useful to have some wrapper templates in the Koha core code for plugins, but even if folk have to bundle their own wrappers in their own plugins, I think it's a good practice. David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595

1 0

Managing SIP2 connections
by dcook＠prosentient.com.au 08 Aug '22

08 Aug '22

Hi all, Out of the box, the SIP2 server just handles 1 connection at a time. While this might be OK for some libraries, it would be good to update our configuration to make this more explicit. I've got a 1 line change to etc/SIPconfig.xml that does this just so that it's clearer what Koha's SIP server is doing out of the box. It would be great to get a sign off and QA on this one. Should be very fast and easy to do. https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31033 David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595

1 0

Re: [Koha-devel] Getting "count" when using REST API
by dcook＠prosentient.com.au 07 Aug '22

07 Aug '22

Jonathan, you are a champion! That'll work perfectly for me! 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: Jonathan Druart <jonathan.druart(a)gmail.com> Sent: Thursday, 4 August 2022 10:17 PM To: Tomas Cohen Arazi <tomascohen(a)gmail.com> Cc: David Cook <dcook(a)prosentient.com.au>; Koha Devel <koha-devel(a)lists.koha-community.org> Subject: Re: [Koha-devel] Getting "count" when using REST API I needed that for ERM and I did a GET with _page=1 and _per_page=1 (to retrieve only 1 result) then read the X-Total-Count value from the header's response ;) Le jeu. 4 août 2022 à 12:33, Tomas Cohen Arazi <tomascohen(a)gmail.com> a écrit : > > Only with x-koha-embed > > > El jue, 4 ago 2022 3:54, <dcook(a)prosentient.com.au> escribió: >> >> Hi all, >> >> >> >> Is there a method for getting a “count” using the REST API without fetching every record? >> >> >> >> When building a paging lookup outside of Koha, it would be useful to get a total record count and then just fetch the page of records that you need. >> >> >> >> Thanks! >> >> >> >> 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(a)lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : https://www.koha-community.org/ git : > https://git.koha-community.org/ bugs : > https://bugs.koha-community.org/

3 5