[Koha-bugs] [Bug 25643] Remove maxreserves syspref

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Tue Jun 2 13:47:58 CEST 2020


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

Andrew Fuerste-Henry <andrew at bywatersolutions.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |andrew at bywatersolutions.com

--- Comment #7 from Andrew Fuerste-Henry <andrew at bywatersolutions.com> ---
(In reply to Katrin Fischer from comment #6)
> I believe it's not the same thing and we should really discuss how to
> interpet default vs. all libraries - I believe we cannot have both and
> should not mix them. There needs to be a clear definition to move forward
> and we should avoid changing behaviour unintentionally for libraries.
> 
> Say you have 3 libraries.
> As they all have the same circulation conditions you only enter rules under
> "Default (all libraries)". Max holds is set to 5.
> 
> maxreserves is set to 10.
> 
> What I believe happens is that you can have only up to 10 holds (capped by
> maxreserves), but a max of 5 for each of the libraries.
> 
> If we remove maxreserves, we either remove the ability to inherit or remove
> the global capping.

+1 to all of this. Katrin's example scenario correctly describes the current
behavior (based on what they've got ReservesControl set to). There's nothing in
the circ rules that can accomplish exactly what MaxReserves does and I hate to
remove that functionality, even though it is confusing.

For what it's worth, I get libraries asking for more functionality along the
lines of what MaxReserves does -- they want to be able to set global limits
irrespective of library and define things like "Patrons in Category A can have
a total of 50 holds across all branches." As Koha stands now, that sort of rule
may or may not be possible based on ReservesControl and other rules.

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


More information about the Koha-bugs mailing list