[Koha-bugs] [Bug 29877] MaxReserves should be enforced consistently between staff interface and API

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

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

--- Comment #10 from Katrin Fischer <katrin.fischer at bsz-bw.de> ---
(In reply to Andrew Fuerste-Henry from comment #9)
> Bug 29875, just pushed to master, updates the system preference text to
> reflect the current behavior in which 0 disables the feature.
> 
> We found this bug because we have libraries with MaxReserves=0 with the
> expectation that this will disable the system preference, as it has done for
> years. So while I appreciate that one *might* expect a value of 0 to mean no
> holds are allowed, I would counter than many users definitively *do* expect
> a value of 0 to mean this feature is disabled and to change that would be
> highly disruptive.

I understand your argument. I often vote for consistence over small
interruptions, because I think long term it makes Koha easier to use. In this
case it would have mimicked what empty means for max holds, max checkouts etc
in circulation rules. As long as we can do so without causing a disruptive
behavior change.

I guess a workaround for disabling holds for users would be OPACHoldRequests
and in the circulation rules, so we might not need a global one. (And can close
this.)

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