[Koha-bugs] [Bug 31500] Add ability to specify MaxReservesPickupDelay at the patron category level

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31500

--- Comment #8 from Katrin Fischer <katrin.fischer at bsz-bw.de> ---
Ok, I will hold off providing the follow-up for now, because I think we should
discuss the concept first:

To me, this feels not right on patron category level, I feel like it should be
in in the circulation rules instead.

So I did some research:

1) There are patches to move ExpireReservesMaxPickUpDelayCharge to circulation
rules, which would fit well together with the pickup delay:
* bug 25711 - ExpireReservesMaxPickUpDelayCharge (NSO)

2) There have been several bugs filed in present and past about moving the
pickup delay to the circulation rules:

* bug 19309 - ReservesMaxPickUpDelay (marked duplicate)

Which argues:

Some libraries would love to have the option to specify the
ReservesMaxPickUpDelay by itemtype, rather than specify the
ReservesMaxPickUpDelay for all items via the system preference. There are times
when specific item types like popular or new items, DVD's or even Museum passes
may not want to sit on a shelf for 7 days waiting for the patron to pick it up.
Versus a non popular item that can wait for 7 days for the patron to pick the
item up. 

A use case I'd add is academic libraries with closed stacks where you might
want to give a longer pickup-period before you return the items to the shelf.

And actually we have a competing bug with patches!

* bug 8367 - How long is a hold waiting for pickup at a more granular level
(FQA)

I'd love if we could push the solution on bug 8367 instead of the patron
category based solution.

We could say: we can do that later... BUT: there is no migration path. If we
start with category level, we won't be able to populate values in the
circulation rules later because of the * (all) rules. So I think this would be
an argument for going circulation rules right away.

-- 
You are receiving this mail because:
You are watching all bug changes.