[Koha-bugs] [Bug 25643] Move maxreserves functionality into circulation rules

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

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

Ray Delahunty <r.delahunty at arts.ac.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |r.delahunty at arts.ac.uk

--- Comment #13 from Ray Delahunty <r.delahunty at arts.ac.uk> ---
I have been testing out changes to reservations / holds settings in our test
server and the maxreserves setting is not working for us in the way Katrin
reports. 

We are on 20.11.04 and all our 6 libraries have the same circulation policies
so I have set Total reservations allowed (under Default issue, reserve & return
policy by category) to 5 for all user categories permitted to place
reservations. Our maxreserves is set to 10.  We do not (currently) allow OPAC
item level reservations so I am not yet thinking about how the Reservations
allowed (under Defining circulation & fine rules for all libraries) will work
for us. (Like, how would Koha know the counts of reservations by item type in
our title-level reservation environment, so it could limit reservations using
this very granular functionality?).  I have set Reservations allowed to 10
which I think effectively takes ‘reservations by item type/user category’ out
of the equation).

But I have not been able to place more than 5 reservation using either the OPAC
or the Koha intranet.  I tried this with ReservesControlBranch set to either of
Item’s home library or user’s home library, but I have not been able to achieve
what I thought was how the functionality works- say 5 reservations for items at
library A, 3 reservations at library B and 2 at Library C.

We are trying to unravel how the counts are set so we can set the counts to be
how we want them to be. Being able to advise users that ‘Patrons in Category A
can have a total of 50 holds across all branches’ (or whatever) would be great.

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