<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body>A new request with request id 8841 has been created by koha-devel-request@lists.koha-community.org. Short info on the request is : <br><br>Title : Koha-devel Digest, Vol 199, Issue 16<br>Category : <br>Description : <div>Send Koha-devel mailing list submissions to<br> koha-devel@lists.koha-community.org<br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>or, via email, send a message with subject or body 'help' to<br> koha-devel-request@lists.koha-community.org<br><br>You can reach the person managing the list at<br> koha-devel-owner@lists.koha-community.org<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of Koha-devel digest..."<br><br><br>Today's Topics:<br><br> 1. Re: Effective circulation rule preview/tester (Philippe Blouin)<br> 2. Re: Effective circulation rule preview/tester (Cab Vinton)<br> 3. Re: Effective circulation rule preview/tester<br> (Victor Grousset/tuxayo)<br> 4. Distributing Koha Plugins efficiently (dcook@prosentient.com.au)<br> 5. Pretty Plugin URLs (dcook@prosentient.com.au)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Wed, 22 Jun 2022 09:27:31 -0400<br>From: Philippe Blouin <philippe.blouin@inlibro.com><br>To: koha-devel@lists.koha-community.org<br>Subject: Re: [Koha-devel] Effective circulation rule preview/tester<br>Message-ID: <9f77d6ab-5ec2-a553-0331-cb992e6d4faa@inlibro.com><br>Content-Type: text/plain; charset="utf-8"; Format="flowed"<br><br>That is an excellent idea. I'll file it in my "fillers", if we ever get <br>interns with spare time again.<br><br>Seriously, that type of query is a continuous drain on our support team.<br><br>Philippe Blouin,<br>Directeur de la technologie<br><br>Tél. : (833) 465-4276, poste 230<br>philippe.blouin@inLibro.com<br><br>inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com><br>On 2022-06-21 22:16, dcook@prosentient.com.au wrote:<br>><br>> Hi all,<br>><br>> How good would it be if there were a preview/tester for effective <br>> circulation rules in the Admin module?<br>><br>> I’m sure I’m not the only one who struggles to figure out what <br>> circulation rule is being applied in any given scenario at times. I <br>> imagine a lot of librarians could make use of it especially.<br>><br>> Probably not something I would develop, but thought it was an <br>> interesting idea.<br>><br>> David Cook<br>><br>> Senior Software Engineer<br>><br>> Prosentient Systems<br>><br>> Suite 7.03<br>><br>> 6a Glen St<br>><br>> Milsons Point NSW 2061<br>><br>> Australia<br>><br>> Office: 02 9212 0899<br>><br>> Online: 02 8005 0595<br>><br>><br>> _______________________________________________<br>> Koha-devel mailing list<br>> Koha-devel@lists.koha-community.org<br>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>> website :https://www.koha-community.org/<br>> git :https://git.koha-community.org/<br>> bugs :https://bugs.koha-community.org/<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220622/af40ba51/attachment-0001.htm><br><br>------------------------------<br><br>Message: 2<br>Date: Wed, 22 Jun 2022 10:55:51 -0400<br>From: Cab Vinton <bibliwho@gmail.com><br>To: Koha-devel <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] Effective circulation rule preview/tester<br>Message-ID:<br> <CABW43UQ2MFW3gbiSU7NjsrduvxH9wAaThOL1cUvouJtP5g_4HA@mail.gmail.com><br>Content-Type: text/plain; charset="UTF-8"<br><br>+1 ! :-)<br><br>Along the same lines, a cron job to periodically rationalize circ<br>rules in multi-branch environments would be useful as well. It's easy<br>for redundancies to creep in, w/ all branches setting up identical<br>rules, which can of course be easily replaced w/ a single rule for all<br>branches.<br><br>All best,<br><br>Cab Vinton, Director<br>Plaistow Public Library<br>Plaistow, NH<br><br><br>------------------------------<br><br>Message: 3<br>Date: Wed, 22 Jun 2022 18:48:08 +0200<br>From: Victor Grousset/tuxayo <victor@tuxayo.net><br>To: koha-devel@lists.koha-community.org, David Cook<br> <dcook@prosentient.com.au>, Philippe Blouin<br> <philippe.blouin@inlibro.com><br>Subject: Re: [Koha-devel] Effective circulation rule preview/tester<br>Message-ID: <28874e6d-a416-1ee5-106f-32bbc31cdb64@tuxayo.net><br>Content-Type: text/plain; charset=UTF-8; format=flowed<br><br>Hi :)<br><br>IIUC part of solution is in:<br>Bug 23732 - Hold rules checker: show matched rules and syspref values to <br>help understand why a hold is possible or not<br><br>If you are interested in testing and reviewing the code, that can <br>motivate me to get it ready this cycle. I tried in the previous cycles <br>and it's mostly done but I still have a number of details, corrections <br>and some automated testing to add.<br><br>-- <br>Victor Grousset/tuxayo<br><br><br>------------------------------<br><br>Message: 4<br>Date: Thu, 23 Jun 2022 13:51:45 +1000<br>From: <dcook@prosentient.com.au><br>To: "'koha-devel'" <koha-devel@lists.koha-community.org><br>Cc: "'Martin Renvoize'" <martin.renvoize@ptfs-europe.com>, "'Kyle<br> Hall'" <kyle@bywatersolutions.com>, "'Tomas Cohen Arazi'"<br> <tomascohen@theke.io><br>Subject: [Koha-devel] Distributing Koha Plugins efficiently<br>Message-ID: <031c01d886b4$9d869db0$d893d910$@prosentient.com.au><br>Content-Type: text/plain; charset="utf-8"<br><br>Hi all,<br><br> <br><br>If I were to unpack 5 different Koha plugins to /opt/koha-plugins and then<br>added "<pluginsdir>/opt/koha-plugins</pluginsdir>" to the koha-conf.xml for<br>all my Koha instances, I should be able to just run "koha-foreach perl<br>/usr/share/koha/bin/devel/install_plugins.pl" to install/upgrade all those<br>plugins within Koha, right?<br><br> <br><br>Once "bug 21366 - add plack reload" is done, we could then do "koha-plack<br>--reload $(koha-list --enabled --plack)" to gracefully reload all those Koha<br>instances to have the freshest version of the plugin. <br><br> <br><br>--<br><br> <br><br>If that's true, a person could bundle Koha plugins however they like, right?<br>They could put them into koha-common, they could do their own koha-plugins<br>package (included or separate to their Koha codebase), they could just use a<br>Git repo, or whatever makes sense for distributing. The advantage of Debian<br>packages would be adding that "koha-foreach" and "koha-plack" into package<br>install hooks. <br><br> <br><br>I suppose a "install plugins" hook in "koha-create" would be wise too so<br>that a new instance could auto install any centralized plugins.<br><br> <br><br>Does that all make sense? Am I missing anything?<br><br> <br><br>I'd really like to use plugins in lieu of Koha customizations but I find<br>distributing the code across a large number of Koha instances to be<br>prohibitive. <br><br> <br><br>David Cook<br><br>Senior Software Engineer<br><br>Prosentient Systems<br><br>Suite 7.03<br><br>6a Glen St<br><br>Milsons Point NSW 2061<br><br>Australia<br><br> <br><br>Office: 02 9212 0899<br><br>Online: 02 8005 0595<br><br> <br><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220623/d9b7f0ad/attachment-0001.htm><br><br>------------------------------<br><br>Message: 5<br>Date: Thu, 23 Jun 2022 14:22:01 +1000<br>From: <dcook@prosentient.com.au><br>To: "'koha-devel'" <koha-devel@lists.koha-community.org><br>Subject: [Koha-devel] Pretty Plugin URLs<br>Message-ID: <032301d886b8$ca953470$5fbf9d50$@prosentient.com.au><br>Content-Type: text/plain; charset="utf-8"<br><br>Hi all,<br><br> <br><br>At the moment, in the Staff Interface, we have plugin URLs like this:<br><br> <br><br>http://localhost:8081/cgi-bin/koha/plugins/run.pl?class=Koha%3A%3APlugin%3A%<br>3ACom%3A%3AByWaterSolutions%3A%3ACoverFlow<br><http://localhost:8081/cgi-bin/koha/plugins/run.pl?class=Koha%3A%3APlugin%3A<br>%3ACom%3A%3AByWaterSolutions%3A%3ACoverFlow&method=configure><br>&method=configure<br><br> <br><br>What if we had something prettier like the following?<br><br> <br><br>http://localhost:8081/cgi-bin/koha/plugin/coverflow/configure or<br><br>http://localhost:8081/cgi-bin/koha/plugin/coverflow?method=configure<br><br><br><br>I was thinking it would leverage a plugin_key of "__NAME__" in the<br>"plugin_data" table. <br><br> <br><br>I suppose it increases the risk of name collisions, but to be honest those<br>collisions can happen in Wordpress (as I recently learned) and it's fine<br>overall. <br><br><br><br> <br><br>David Cook<br><br>Senior Software Engineer<br><br>Prosentient Systems<br><br>Suite 7.03<br><br>6a Glen St<br><br>Milsons Point NSW 2061<br><br>Australia<br><br> <br><br>Office: 02 9212 0899<br><br>Online: 02 8005 0595<br><br> <br><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220623/728e4f20/attachment.htm><br><br>------------------------------<br><br>Subject: Digest Footer<br><br>_______________________________________________<br>Koha-devel mailing list<br>Koha-devel@lists.koha-community.org<br>https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>website : https://www.koha-community.org/<br>git : https://git.koha-community.org/<br>bugs : https://bugs.koha-community.org/<br><br><br>------------------------------<br><br>End of Koha-devel Digest, Vol 199, Issue 16<br>*******************************************<br></div><br><br>NOTE: You are receiving this mail because, the Requester/Technician wanted you to get notified on this request creation.<br></body></html>