Handling Unfilled Pages
This is a resubmission of a recently expired idea & my continued longing to see some long lost development efforts brought to fruition.
Following Disney's lead of recycling years old ideas for theme park attractions, I'd like to see an idea I'd had while working with a former employer brought to fruition in Sierra. We had been using Millennium at the time & the Circulation Product Manager had gotten to a point in development that there was a near-working model on III's test environment (I've got screenshots & even a Captivate video somewhere), but I left that employer & the III product manager left III & the idea was abandoned, which is a shame, as it could still be of benefit to Sierra hold management workflows.
How it was designed to work was as follows:
1) Staff would complete their title, item, or Rapido paging list, trapping everything that they pulled from the shelf for a local or external hold.
2) If there were any items they could not locate, they would then access this newly created Unfilled Pages function.
3) From this new function, they'd select the instance of the paging list from a drop-down menu that showed the time(s) the list was last run. The drop-down would include the title, item, & INN-Reach lists, & for libraries that ran it multiple times a day, each instance of that list.
4) Their selection would take them to a list of items on that instance of the list that were not pulled & trapped for holds.
5) From here, they would be able to convert the status of all unfound items to Missing in batch. The intended customer retained their place in the hold queue & the torch was then passed to the next library location where the item was understood to be available.