Item in transit for hold doesn't check if still needed for hold if checked in at location other than pickup library
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
3.11.1
We've discovered behavior that when checking in material that's in transit, Evergreen just sees its in transit and redirects rather than checking to see if it is still needed.
1. an item is needed for hold, captured and put in transit at library A
2. patron cancels hold
3. arrives at library (B) other than destination library, is checked in
4. rather than check if its needed for hold and where it should be going, its simply sees its in transit and redirects to destination library (C)
5. destination library (C) receives item, checks it in and realizes the hold was canceled before it even arrived at (B)
Also, when this scenario occurs, there's no record of it in the action.transit_copy table. Its "checkin" at library B is not recorded
tags: | added: circ-holds transits |
Changed in evergreen: | |
status: | New → Confirmed |
In this scenario, is library B acting as a sort of transit hub that is responsible for forwarding on items bound for library C? Or a main library sorting through a set of received books to pass them on to the branches?