Comment 3 for bug 1895052

I have pushed a branch that adds two new YAOUSen that control this new pickup library oriented stalling. The new settings can work in conjunction with the existing soft stalling setting. Branch coordinates: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/miker/lp-1895052-pickup-library-controlled-stalling-rebased

From the commit messages:

First:

This commit provides a new YAOUS that, when set, takes precedence over the current "soft stalling interval" YAOUS. Instead of limiting capture to items owned by the pickup library (or the directly targeted item) based on the context of scanned item's circulating library, it instead
restricts op capture to holds that have a pickup library of the scanning location when the hold is younger that the interval, base on the context of the pickup location of each hold.

tl;dr: It allows the pickup library to control op capture stalling rather than the circulating library of an arbitrary scanned item.

Second:

This commit adds a new YAOUS that allows a pickup library to specify that it does not want its holds to have foreign (prox > 0) copies directly targeted if there is a local copy in an available status (on the shelf). The setting is an interval, and after the age of the hold
has passed that interval, foreign direct targetting is allowed.

This does not change the calculation of the potential list, so op-capture will be available (all else being equal) without retargetting.

This setting (circ.pickup_hold_stalling.hard) is meant to be used in concert with the other new setting in the parent commit (circ.pickup_hold_stalling.soft), and should generally have a value the same or smaller than the soft setting. Doing this allows tiered targetting, where no remote items are targeted via the hard setting for, say, 3 days, where all capture is restricted to only the pickup, and then, with a soft setting of 5 days, the next 2 days allow only direct target capture of foreign copies. After 5 days, normal, global targetting and op-capture resumes.

An alternative use for this setting is to ignore the parent-commit soft setting and allow op-capture everywhere, but only direct targetting at the pickup library. The effect of this, if used globally throughout an entire Evergreen instance, would be that the pull list would only
represent pickup-local holds, but serendipitous scans of items that could fill remote holds could capture for transit.

Thank you to CW MARS for funding this effort!