When using the real time holds queue new requests rebuild the entire holds queue - this can mean libraries go to find a book on a shelf, only to find the queue has changed and another item has filled the request in the meantime. Similarly, when not using the real time holds queue, some libraries will limit the cron to running once a day to avoid ever changing holds lists. It would be nice to have an option for both methods that would limit the queue to filling new holds without deleting the current queue
I don't think that the RT holds queue rebuilds the whole table, but that it does rebuilt all entries for one biblionumber, which can also cause issues with the timestamps (a library might use it to print request slips to closed stacks) Nick, are you sure it's completely rebuilt or is this just an issue with the cron?
(In reply to Katrin Fischer from comment #1) > I don't think that the RT holds queue rebuilds the whole table, but that it > does rebuilt all entries for one biblionumber, which can also cause issues > with the timestamps (a library might use it to print request slips to closed > stacks) > > Nick, are you sure it's completely rebuilt or is this just an issue with the > cron? You are correct, it is only per biblio that RTHQ rebuilds the queue, but some libraries would like items to remain on the queue for longer
Yes, I am adding Michaela as I think if we made the update more clever, that would also resolve the issue they found with the timestamps getting updated (and thus making it not reliable to be used as an indicator for what has been printed already).
*** This bug has been marked as a duplicate of bug 32565 ***