On-site checkouts and circulation types proposal
Hi fellow Koha devs, I'm working on Bug 24101 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24101 in which our client wants the ability to separately define circulation rules for normal and on-site checkouts. They need the ability to renew on-site checkouts, define due date calculation parameters and additionally specify separate fine rules (not mentioned in bz ticket yet). I wanted to ask for your thoughts on this. Initially I was thinking of duplicating the rules of normal circulation the way maxissueqty and maxonsiteissueqty is currently done, but in the end this would lead to duplicating almost all of the circulation rules. That would not be very convenient and it seems like a short-sighted way of solving this problem because it leaves no room for . Who wants to see the circulation rule table doubling in width? Not me. Another, more elegant approach would be to define a new circulation rule scope "circulationtype" that defines whether a rule applies to normal or on-site checkout (or any other type of checkout someone may come up with in the future). Now that we are able to explicitly define a scope that a specific circulation rule follows, this would make sense. No need for ugly duplication and we can get rid of maxonsiteissueqty too. Anyways, before I start implementing such a change I wanted to ask for support from the community, or better yet even cooler ideas. Perhaps there is something about Koha that I have missed that could already solve their problem. Thanks for your time. -- Lari Taskula CEO, Hypernova Oy +358449857337 Kauppakatu 25 C 409 80100 Joensuu, Finland
Hey Lari, I had never even heard of on-site checkouts before reading your email. My vote is whatever makes things simplest for librarians. The current circulation and fines rules system is so complex that I have yet to meet a librarian who understands it intuitively. That said, I feel like Owen Leonard might be re-engineering that system currently? So he might be the best person to talk to. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595 -----Original Message----- From: Koha-devel <koha-devel-bounces@lists.koha-community.org> On Behalf Of Lari Taskula Sent: Wednesday, 1 April 2020 5:25 PM To: Koha Devel <koha-devel@lists.koha-community.org> Subject: [Koha-devel] On-site checkouts and circulation types proposal Hi fellow Koha devs, I'm working on Bug 24101 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24101 in which our client wants the ability to separately define circulation rules for normal and on-site checkouts. They need the ability to renew on-site checkouts, define due date calculation parameters and additionally specify separate fine rules (not mentioned in bz ticket yet). I wanted to ask for your thoughts on this. Initially I was thinking of duplicating the rules of normal circulation the way maxissueqty and maxonsiteissueqty is currently done, but in the end this would lead to duplicating almost all of the circulation rules. That would not be very convenient and it seems like a short-sighted way of solving this problem because it leaves no room for . Who wants to see the circulation rule table doubling in width? Not me. Another, more elegant approach would be to define a new circulation rule scope "circulationtype" that defines whether a rule applies to normal or on-site checkout (or any other type of checkout someone may come up with in the future). Now that we are able to explicitly define a scope that a specific circulation rule follows, this would make sense. No need for ugly duplication and we can get rid of maxonsiteissueqty too. Anyways, before I start implementing such a change I wanted to ask for support from the community, or better yet even cooler ideas. Perhaps there is something about Koha that I have missed that could already solve their problem. Thanks for your time. -- Lari Taskula CEO, Hypernova Oy +358449857337 Kauppakatu 25 C 409 80100 Joensuu, Finland _______________________________________________ Koha-devel mailing list Koha-devel@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/
That said, I feel like Owen Leonard might be re-engineering that system currently?
Not me! I think Bug 15522, "New interface for revamped circulation rules" is what you're thinking of. -- Owen -- Web Developer Athens County Public Libraries (740) 737-6006 https://www.myacpl.org
Wow I got that completely wrong. My apologies. In that case, nothing further to add, except to reiterate that we really should get as much user input as possible, so I'm glad Jonathan suggested the general list. (Not to say that users always know what is best, but I know they often have a very different take on things from developers.) David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595 -----Original Message----- From: Koha-devel <koha-devel-bounces@lists.koha-community.org> On Behalf Of Owen Leonard Sent: Thursday, 2 April 2020 7:34 AM To: Koha Devel <koha-devel@lists.koha-community.org> Subject: Re: [Koha-devel] On-site checkouts and circulation types proposal
That said, I feel like Owen Leonard might be re-engineering that system currently?
Not me! I think Bug 15522, "New interface for revamped circulation rules" is what you're thinking of. -- Owen -- Web Developer Athens County Public Libraries (740) 737-6006 https://www.myacpl.org _______________________________________________ Koha-devel mailing list Koha-devel@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/
Apologizes, sent my email before I could finish my edit;
leaves no room for . ... possible new types of checkouts in the future.
Lari Taskula CEO, Hypernova Oy +358449857337 Kauppakatu 25 C 409 80100 Joensuu, Finland On 1.4.2020 9.24, Lari Taskula wrote:
Hi fellow Koha devs,
I'm working on Bug 24101 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24101 in which our client wants the ability to separately define circulation rules for normal and on-site checkouts. They need the ability to renew on-site checkouts, define due date calculation parameters and additionally specify separate fine rules (not mentioned in bz ticket yet).
I wanted to ask for your thoughts on this.
Initially I was thinking of duplicating the rules of normal circulation the way maxissueqty and maxonsiteissueqty is currently done, but in the end this would lead to duplicating almost all of the circulation rules. That would not be very convenient and it seems like a short-sighted way of solving this problem because it leaves no room for . Who wants to see the circulation rule table doubling in width? Not me.
Another, more elegant approach would be to define a new circulation rule scope "circulationtype" that defines whether a rule applies to normal or on-site checkout (or any other type of checkout someone may come up with in the future). Now that we are able to explicitly define a scope that a specific circulation rule follows, this would make sense. No need for ugly duplication and we can get rid of maxonsiteissueqty too.
Anyways, before I start implementing such a change I wanted to ask for support from the community, or better yet even cooler ideas. Perhaps there is something about Koha that I have missed that could already solve their problem.
Thanks for your time.
Hi Lari, I think it would be interesting to get opinions from the general mailing list. What are the different use cases? Which rules are suitable for such separation? Theoretically, all. But in practice? Your idea is good I think, and certainly a great way to answer the need. Few things: You will not double the size of the table horizontally, but maybe vertically. Instead of 1 row you will end up with 2. To prevent it to be doubled, the "type" will need to be "normal", "onsite", or "both" if current maxissueqty == maxonsiteissueqty Keep in mind the syspref ConsiderOnSiteCheckoutsAsNormalCheckouts. Cheers, Jonathan Le mer. 1 avr. 2020 à 08:24, Lari Taskula <lari.taskula@hypernova.fi> a écrit :
Hi fellow Koha devs,
I'm working on Bug 24101 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24101 in which our client wants the ability to separately define circulation rules for normal and on-site checkouts. They need the ability to renew on-site checkouts, define due date calculation parameters and additionally specify separate fine rules (not mentioned in bz ticket yet).
I wanted to ask for your thoughts on this.
Initially I was thinking of duplicating the rules of normal circulation the way maxissueqty and maxonsiteissueqty is currently done, but in the end this would lead to duplicating almost all of the circulation rules. That would not be very convenient and it seems like a short-sighted way of solving this problem because it leaves no room for . Who wants to see the circulation rule table doubling in width? Not me.
Another, more elegant approach would be to define a new circulation rule scope "circulationtype" that defines whether a rule applies to normal or on-site checkout (or any other type of checkout someone may come up with in the future). Now that we are able to explicitly define a scope that a specific circulation rule follows, this would make sense. No need for ugly duplication and we can get rid of maxonsiteissueqty too.
Anyways, before I start implementing such a change I wanted to ask for support from the community, or better yet even cooler ideas. Perhaps there is something about Koha that I have missed that could already solve their problem.
Thanks for your time.
-- Lari Taskula CEO, Hypernova Oy +358449857337 Kauppakatu 25 C 409 80100 Joensuu, Finland
_______________________________________________ Koha-devel mailing list Koha-devel@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/
I have sent this to the general mailing list. tldr for general list readers; * we need to be able to define separate circulation rules between normal and on-site checkouts. * my proposal in this mail is to add a new circulation rule scope "circulationtype". A rule scope in Koha is currently a combination of a library, patron category and item type. * circulationtype would be either "All" (default), "Normal" or "On-site" The case is explained by our client library here https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24101#c0
Which rules are suitable for such separation?
I think this would make sense to all circulation rules except hold-related rules. It would allow very flexible parametrization between normal and on-site checkouts. In order to make adaptation straight-forward, this could be blocked by Bug 15522 (the circulation rules user interface change). Once 15522 is pushed and libraries update their Koha instances, they could find this together with the new GUI. Also at this point it doesn't make much sense to develop anything new on top of the old interface. Lari Taskula CEO, Hypernova Oy +358449857337 Kauppakatu 25 C 409 80100 Joensuu, Finland On 1.4.2020 10.46, Jonathan Druart wrote:
Hi Lari,
I think it would be interesting to get opinions from the general mailing list. What are the different use cases? Which rules are suitable for such separation? Theoretically, all. But in practice?
Your idea is good I think, and certainly a great way to answer the need.
Few things: You will not double the size of the table horizontally, but maybe vertically. Instead of 1 row you will end up with 2. To prevent it to be doubled, the "type" will need to be "normal", "onsite", or "both" if current maxissueqty == maxonsiteissueqty
Keep in mind the syspref ConsiderOnSiteCheckoutsAsNormalCheckouts.
Cheers, Jonathan
Le mer. 1 avr. 2020 à 08:24, Lari Taskula <lari.taskula@hypernova.fi> a écrit :
Hi fellow Koha devs,
I'm working on Bug 24101 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24101 in which our client wants the ability to separately define circulation rules for normal and on-site checkouts. They need the ability to renew on-site checkouts, define due date calculation parameters and additionally specify separate fine rules (not mentioned in bz ticket yet).
I wanted to ask for your thoughts on this.
Initially I was thinking of duplicating the rules of normal circulation the way maxissueqty and maxonsiteissueqty is currently done, but in the end this would lead to duplicating almost all of the circulation rules. That would not be very convenient and it seems like a short-sighted way of solving this problem because it leaves no room for possible new types of checkouts in the future. Who wants to see the circulation rule table doubling in width? Not me.
Another, more elegant approach would be to define a new circulation rule scope "circulationtype" that defines whether a rule applies to normal or on-site checkout (or any other type of checkout someone may come up with in the future). Now that we are able to explicitly define a scope that a specific circulation rule follows, this would make sense. No need for ugly duplication and we can get rid of maxonsiteissueqty too.
Anyways, before I start implementing such a change I wanted to ask for support from the community, or better yet even cooler ideas. Perhaps there is something about Koha that I have missed that could already solve their problem.
Thanks for your time.
-- Lari Taskula CEO, Hypernova Oy +358449857337 Kauppakatu 25 C 409 80100 Joensuu, Finland
_______________________________________________ Koha-devel mailing list Koha-devel@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/
participants (4)
-
dcook＠prosentient.com.au -
Jonathan Druart -
Lari Taskula -
Owen Leonard