Comment 8 for bug 1686463

This has just come up again in our consortium, in regards to newly created items.

I'm wondering what would be involved in kicking off a process for created or updated items that's similar to the "Retarget ..." checkin modifiers processing available at checkin. And if this could be a reasonable approach.

While it would not solve the age-hold protection expiration, or the change in attributes of status or copy location, it would address the situations related directly to adding and updating items.

It is quite common in our consortium for a newly added or updated item to be expected to capture a hold. Less common for changes that affect the items indirectly.