Comment 3 for bug 1686463

I can conceive of a checkin with hold capture expected happening quite soon after the update that makes the item holdable. There's also the frequent situation where a checkin IS the edit that puts the item into a holdable status. Ideally, the hold would just capture in that case.

But even retargeting in the background that could take a minute or so would be a great improvement.

Mike's idea is intriguing, too, and if there could be a way to get new copies into the peer table in the background as they're added, that might cover all the bases.

Here are a few use cases:

A library is processing their pull list. They are unable to locate an item on the list so they change its status to Missing. Shortly thereafter, they locate the item and check it in. The hold should capture.

A library has some items in a "Summer Reading" copy location which are offsite during much of the year. While offsite, the copy location is set as not holdable. When the boxed items arrive at the library, the copy location attribute is changed to holdable, and the items are unpacked and checked in. Any existing holds on the titles to which these items are attached should capture.

A library receives a gift of a very popular item with multiple holds. Cataloging staff quickly enters it into the system and checks it in. The appropriate next existing hold on the title should capture the item.