Calculated Proximity Adjustments / Custom Best-Hold Selection Sort Order
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
For Evergreen master/2.4+
Calculated Proximity Adjustments, a new feature
Allows customization to the way that Evergreen measures the distance
between org units for the purposes of 1) determining what copy at what
org unit is best suited for targeting a title-level hold, and 2)
determining what hold is best suited for fulfillment by a copy-in-hand
at capture (checkin) time. The customization is based on a table
'actor.
that the system compares to properties of the holds and copies in
question.
This feature is actually side-ported from the FulfILLment project, where
it was originally developed by Mike Rylander. Lebbeous Fogle-Weekley
was responsible for integration into current Evergreen code, some
testing and bug-fixing, and minor refinement of documentation.
Note to testers: 1) see tech specs included in the branch, 2) the first place to see results of these adjustments is in action.
Thanks to Bibliomation, MassLNC, HSLC and Sage for sponsoring this work!
Changed in evergreen: | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
At this point I question something:
How can we pre-calc this proximity on the copy when we don't know *where* the copy will be captured? Not to mention we could have issues with not taking into account where we currently are holding the copy.
It isn't like we know the copy will be captured at the owning library, after all. (Though I could see FulfILLment being able to make that assumption)