I'm confused. Once the hold targeter has populated the current_copy column, I wasn't aware that it would automatically pick another copy after awhile. It sounds like you are saying that it does. Right now, /openils/bin/hold_targeter.pl will pass
$storage->request('open-ils.storage.action.hold_request.targetable_holds.id_list', '24h');
Meaning: Every 24 hours, attempt to expand the pool of potential copies in the action.hold_copy_map. In addition to that, only pay attention to holds that haven't received attention in 24 hours (based on prev_check_time). This is the reason that newly cataloged items do not fill holds right away. This doesn't mean "Search for a different copy if capture_time is still null after x amount of time" does it?
I'm confused. Once the hold targeter has populated the current_copy column, I wasn't aware that it would automatically pick another copy after awhile. It sounds like you are saying that it does. Right now, /openils/ bin/hold_ targeter. pl will pass >request( 'open-ils. storage. action. hold_request. targetable_ holds.id_ list', '24h');
$storage-
Meaning: Every 24 hours, attempt to expand the pool of potential copies in the action. hold_copy_ map. In addition to that, only pay attention to holds that haven't received attention in 24 hours (based on prev_check_time). This is the reason that newly cataloged items do not fill holds right away. This doesn't mean "Search for a different copy if capture_time is still null after x amount of time" does it?