[ List Archives Home ] [ Thread index for 2008 ] [ Date index for 2008 ] [ Author index for 2008 ]


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
I am trying to understand how the holdshelf functions work when setup for Multiple Location. From what I understand there is an internal list on the system that contains an item record number, a hold shelf location(pickup location) and an active flag, for each item. An item gets placed on this list when it is checked in at the pickup location or any time a staff member clicks on the "place on holdshelf" button.

When an item is checked out the status gets changed but the item remains on the holdshelf list.

When an item is checked in the status gets changed but the item remains on the holdshelf list.

When clear holdshelf is run a process goes through that list and marks items as active or not depending on the current item status/ time on holdshelf etc.

When the holdshelf is cleared holds are automatically moved on to the next patron with no control over the process.

When an item's time on the holdshelf is up and if it is just checked in it moves on to the next hold but it remains on the holdshelf list.

Every night a process runs through the holdshelf list and removes inactive entries.

Problems we are having with process:
There is no room for flexibility if the clear holdshelf is run every day. Staff cannot hold onto an item for an extra day if the patron cannot pickup in the time allowed. If it is a popular item with many holds it gets moved to another patron right away.

The system doesn't stay in sync with reality very well, any location can place items on anyone else's holdshelf, and often do. The item doesn't have to be checked in at the correct location. I think this can be helped by changing our Check-in: Check-in at wrong location option though.

Design:
It seems like this was designed this way because it isn't feasible to do an item database search to deal with the holdshelf, or at least it isn't scalable to very large collections. It would take too much time to search for all items with a status of on holdshelf with a certain pickup location in the associated hold. I wonder if there was an index on the status field if it would be feasable to deal with the holdshelf without this seperate system list. Or maybe have a database trigger go off when the status is changed from on hold shelf to something else that would update the holdshelf list..

Does this sound about right, or am I way off on some of my assumptions. Anyone have anything more to add from their experiences.
Thanks
Josh



--
--
Josh Stompro | Office 218.233.3757 EXT-139
LARL Network Coordinator | Mobile 701.371.3857