https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41879
Bug ID: 41879
Summary: Holds that move to a new bib can be unfillable
Initiative type: ---
Sponsorship ---
status:
Product: Koha
Version: 25.11
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P5 - low
Component: Hold requests
Assignee: [email protected]
Reporter: [email protected]
QA Contact: [email protected]
CC: [email protected], [email protected],
[email protected]
If a library's 'Holds and bookings policies by item type' allows holds by
patrons from any library, but pickup at the item’s home library only, holds can
be moved from bib A to bib B in a way that makes them unfillable with no
indication that they won't fill. Currently, when the hold is moved from bib A
to bib B, the hold pickup location will not automatically update to reflect the
rule, and there is no notice that the rule has been broken.
Scenario:
-ReservesControlBranch is set to 'item's home library'
-Main library's 'Holds and bookings policies by item type' for the itype BOOK
is set to allow holds from patrons from any library, but pickup at Main only
-Bib A is owned by North library, and bib B is owned by Main. Both are the item
type BOOK, and each has one item on the bib.
Steps:
-Place a hold for a North patron on bib A for pickup at North
-Move the hold to bib B
-Note that the hold moves successfully, and is still set for pickup at North
When the hold moves, there is no indication that the item will never trigger to
send to North due to Main's 'Holds and bookings policies by item type'. The
only way staff would realize that the hold will never fill is if they drop down
the pickup locations for the moved hold and see the flag indicating that the
current location isn't allowed.
The move should either fail (as it does if the target record only allows holds
from patrons matching the item’s home library per 'Holds and bookings policies
by item type'), or staff should be forced to select a valid pickup location in
order to complete the move.
--
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.
_______________________________________________
Koha-bugs mailing list
[email protected]
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
