More reliable data around Holds: Don't delete Holds in the `holds_removed` Sierra DNA table!
Data in the hold_removed
table is being deleted before the 60-day retention period is up in situations where staff clear the hold shelf, and an entry in the hold_removed
table is indicated to be "picked up". This is unexpected and not helpful in the task of gathering more data related to holds.
I propose the following changes...
Retention Period: Entries are being removed from the hold_removed table before the default 60-day retention period is up. I propose that data should remain in this table, as it represents the lifecycle of a hold and the recorded event that removed an active hold from the Sierra system.
Hold ID: The
hold_removed
table should record thehold_id
associated with the hold being removed. This would enable comprehensive tracking of a hold from its creation to its removal in the system.Link to Filled Hold Transaction: Ideally, the
hold_removed
table should have a way to link the removed hold to afilled hold
transaction AND ahold placed
transaction in thecirc_trans
table. This linkage would provide a complete history of the hold, including both the creation and removal events.
Thank you for your consideration!

In accordance with the Idea Graduation Workflow guidelines agreed upon by Innovative and IUG, this idea has been closed because it was submitted more than two years ago and has not been selected for inclusion in the product.
This idea is still available for commenting but is no longer eligible for voting.
Ideas that were submitted three or more years ago are archived for future reference.
-
Andrew Hollingsworth commented
Currently the view is not very useful for gathering any meaningful data since all the data is not there