Feature: action.hold_request should datestamp the hold when targeter assigned a copy
Bug #1430545 reported by
Blake GH
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
New
|
Undecided
|
Unassigned |
Bug Description
We would like to know when a copy was targeted. This will enable us to decide to retarget a hold after X amount of time. It would be great if there was a library setting that will automatically retarget a hold after a configurable amount of time. We are finding that copies are getting targeted but never pulled. We don't know how long something has been targeted because the hold targeter continues to update the prev_check_time column. Perhaps a new timestamp column should be added to the schema?
The table action. unfulfilled_ hold_list keeps a record of holds that should have been filled by a current targeted copy but which were not filled. It is populated each time the hold targeter processes a hold for retargeting.
The hold targeter also consults the "Maximum library target attempts" library setting. If items at a given library have failed to pulled the number of times specified by that setting, the targeter will try exclude that library's copies from future consideration.
Does that give you enough to work with?