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...

1. 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.

2. Hold ID: The hold_removed table should record the hold_id associated with the hold being removed. This would enable comprehensive tracking of a hold from its creation to its removal in the system.

3. Link to Filled Hold Transaction: Ideally, the hold_removed table should have a way to link the removed hold to a filled hold transaction AND a hold placed transaction in the circ_trans table. This linkage would provide a complete history of the hold, including both the creation and removal events.

Thank you for your consideration!