New Hold Type - Send To/Rotation - cancel when arrives
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
New
|
Wishlist
|
Unassigned |
Bug Description
Hello, I've been looking at how some types of item rotation could be made easier, and one idea I've been toying with is having a separate hold type that acts like a forced hold, but the goal is just to get an item to the pickup location so it will go on the shelf there.
We currently use floating, so all we need to do is get an item to the correct location, and when it gets checked in, the circ lib changes to the current location. But the lists of what to send have to be sent to each location, and there is no tracking of the items when they are in delivery.
I think it would be ideal if the holds pull list could be used to notify staff about what they need to grab, and then the items could be pulled and tracked in transit like any other hold.
Once the item arrives at the pickup location and gets checked in, the hold would be canceled and the item would float to that location.
I can emulate this now by placing force holds and then canceling the hold as soon as the item goes in transit, saying no to canceling the transit. It would just be nice not to have to do the hold cancellation step.
This would make it possible to handle rotation and collection balancing entirely in Evergreen, without needing to send out separate lists via email, and having special procedures for handling those items.
This could be made to work for systems that don't use floating by forcing the circ_lib=pickup_lib at checkin also. For those that do rotate items, but don't use floating.
Josh
Josh,
This is interesting, but I wonder if it deserves a separate UI from holds that helps with tracking. For instance, we could (in a dedicated UI) simply fill a bucket (new type of "rotation"), force the circ_lib up front via the batch-copy- edit-in- bucket logic, and have the UI provide a "rotation pull list" that could be generated at any time, given a selected rotation bucket. Then, when pulled and scanned at checkin, the items would transit to their new home automatically, via the normal mechanism. This would also have the benefit of allowing circ between the "rotation selection" stage and the "check in for transit" stage, if a patron has the item in hand.
Thoughts?