Pickup Library Hard Stalling Should Integrate Better with Holds Retarget Interval

[John Amundson]

Evergreen 3.5.3 with some custom patches.

In our system, we have the following set network-wide:
- Pickup Library Hard Stalling Interval: 2 days
- Pickup Library Soft Stalling Interval: 2 days
- (Global Flag) Holds Retarget Interval: 24 hours

The goal:
For the first two days of a hold's life, if a local available copy exists, the hold will not move on. After 2 days, the hold will retarget every 24 hours.

What we are finding:
After having had this set for several months, we are getting reports that even though the hard stalling interval is set to 2 days, holds are moving on to other items after the first 24 hours even when there is a local, available copy.

Ideally, the retarget interval should take into account better the hard stalling interval and skip the retarget if the currently assigned copy is a local copy.

For now, we are most likely going to increase the retarget interval to 48 hours to better accommodate. However, there are many real-word applications where that may not work.

For example, say a small library in a network is open 2 days a week. Stalling intervals are set for the library to 5 days to give the library a fighting chance at filling their own holds. Realistically, the retarget interval for the network can't be set to 5 days to accommodate the one small library.

[Jessica Woolford (jwoolford)]

Our libraries have been asking for this for a long time. They would love it if there was a setting that the hold *never* retarget if a local copy is on the shelf and available.