[Koha-bugs] [Bug 21932] reservetype and reserveexpiration needed for holds (reserves and old_reserves tables)

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Sat Dec 1 21:16:21 CET 2018


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

--- Comment #1 from Christopher Brannon <cbrannon at cdalibrary.org> ---
To test flaws:

1) Place a first available hold for the next available item, and set the hold
expires date to a short time, like tomorrow.
2) Make sure your ReservesMaxPickUpDelay setting is set for longer that a day. 
Say 7 days, for example.
3) View the hold.  Note the expiration date is set.
4) Check in the item and trigger the hold.  See that the item is waiting.  Note
the expiration is set to the patron's preferred expiration date.
5) Set the priority back to 1, and update the hold.  Note that the hold is now
an item specific hold instead of a next available hold.
6) Note the expiration stayed.  This is okay in this instance.
7) Cancel the hold and start over.
8) Place a first available hold for the next available item, but do not set the
hold expires date.
9) View the hold.  Note the expiration date is not set.
10) Check in the item and trigger the hold.  See that the item is waiting.  Not
the expiration date is set.
11) Set the priority back to 1, and update the hold.  Note that the hold is now
an item specific hold instead of a next available hold.
12) Note the expiration stayed.  This is not okay in this instance.  The
patron's hold will disappear after the date!

-- 
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