Un-cancelling an in-transit hold can cuase the item to not transit back to the owning library upon checkin at the destination.

Bug #2062379 reported by Dale Rigney
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Evergreen
New
Undecided
Unassigned

Bug Description

Tested on Evergreen 3.11.5

When a hold is canceled after an item is placed in transit and then un-canceled it can cause the item to be placed in reshelving status when checked in at receiving library. If the hold was to remain canceled Evergreen will send that item back to the owning library.

Here is how to duplicate the issue.

1) Place a hold with a pickup library of B.
2) Check in an item at Library A that will capture for the hold, Evergreen will place that item in transit to Library B to fill the hold.
3) Cancel the hold.
4) Un-cancel the hold. This will clear the capture time from the hold but keep the current_copy field with the item that was captured.
5) The hold will retarget automatically after 24 hours but you can re-target the hold to speed up that process. The hold should target a different copy.
6) Check in the in-transit item at Library B.
7) Evergreen will update the shelf_expire_time on the hold the item was intended for but will not prompt the staff to place the item on the hold shelf. Evergreen then changes the item status to Reshelving and does not place the item back in transit to the owning library.

Note: Evergreen will also create events for any of the Hold Ready for Pickup notices that are active. When those events run they end up with a state of "Invalid".

IMO. The item should either be captured for another hold and placed in-transit or on the hold shelf for the new hold. If no hold is found the item should be placed back in-transit to the owning library.

Tags: circ-holds
Michele Morgan (mmorgan)
tags: added: circ-holds
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.