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