Use copy owning library as the context for finding best hold sort order setting
Bug #1271293 reported by
Mike Rylander
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
2.5 |
Fix Released
|
Medium
|
Unassigned |
Bug Description
In the olden days before best hold sort order and proximity adjustment, there was no need to consider any context org other than "here", because the choices were, essentially, FIFO or Traditional applied within the hard-boundary range. However, now we need to decided whose rule to follow, and the most correct arbiter of that is the owning library of the call number of the copy. We avoid copy circ lib because that can change with floating copies.
This applies cleanly to 2.4+.
Changed in evergreen: | |
milestone: | 2.6.0-alpha1 → 2.6.0-beta1 |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
no longer affects: | evergreen/2.4 |
To post a comment you must log in.
Been testing this on one of our systems, so far so good.
Picked to master, rel_2_5, and rel_2_4. Thanks Mike!