Issue #11
Hello all,
This is a follow-up to the last blog that discussed the lag in filling holds and provided tips on expediting that process.
WorkFlows Function Alert - Filling Holds in a Timely Manner When Three Campuses Are Involved
We have received more reports of items being sent back to their owning campus instead of being sent to the campus that the patron requested the item be sent to when they placed the item on hold.
This scenario is most likely to occur when there are 3 campuses involved:
- an owning campus
- an item drop-off campus
- and a hold pick-up campus
Here is an example scenario where an item has been returned to its owning campus instead of being sent to the requested hold pick-up campus:
A patron places a hold on an item that is currently checked out and chooses a pick-up campus that is not the item-owning campus; that item is returned to a campus other than its owning campus; circulation staff at the item drop-off campus do not see the "Item in Transit" hold alert instructing them to place the item in transit to the requested pickup campus; the item is placed in transit back to its owning campus and not to the location that the patron requested it be sent for pick-up.
This situation causes a significant lag in the time that the hold will be filled for the patron!
To avoid this situation, please look carefully at any WorkFlows pop-ups that appear when you are checking in items that have arrived in the daily mail and wait several seconds before moving on to process another item!
Items that have a hold on them will prompt an "Item Not Charged" pop-up when they are checked-in, but the "Item in Transit" message that appears shortly after the initial "Item Not Charged" pop-up can be easily overlooked if you move on to another transaction too quickly.
If this happens, then an item that should be placed in transit to the hold pick-up campus will be returned to its owning campus and additional time will be added on to when the hold will be filled.