Comment 1 for bug 1686463

How soon after a copy status, etc. update would we expect staff to check the item in for capture?

Since this could result in re-targeting hundreds of holds for a single copy update, the re-targeting process will have to run in the background after the copy update has completed. It could take (say) a minute before the copy could be op-capturable by all affected holds via checkin.

We'll probably want to use the new soft_retarget_interval option (e.g. "0s") so the copy maps for the affected holds are updated to pick up the newly available copy, without modifying the already-targeted (viable) copies. That should make is slightly faster as well.