| Table of Contents | ||
|---|---|---|
|
...
Overview
The primary driver in determining item resolution is speed of delivery.
Factors used to determine item resolution are:
Circulation status
Loans
Holds
Geographic proximity
Preferred suppliers
Auto request balancing
Rules
...
On-shelf ranks above loans, ranks above holds
...
When all items are loaned, the item due soonest is selected
...
When all items have holds, the item with the least number of holds is selected
...
When all item resolution determinants are equal (e.g. all items on-shelf) and geographic proximity is enabled and preferred suppliers are not enabled, use geographic proximity to determine which item is selected to place the request
...
When preferred suppliers are also enabled, use a preferred supplier from the same group.
...
If more than one supplier in the same group, use geographic proximity OR load balancing to make the selection
...
Introduce additional item resolution capabilities that improves the speed of delivery to patrons OpenRS requests and, for suppliers, the need to distribute requests according to consortial business needs. To aid in speed of delivery, OpenRS needs to allow requests on items with holds and, items that are checked out.
In a subsequent release, two additional capabilities will be introduced. One is to prioritize item resolution by preferred suppliers. The other is to use automated request balancing to provide more even distribution of item requests to suppliers.
All request capabilities must be compatible with one another and yet must stand independently without reliance on any of the other resolution factor. A set of rules and the ordering of those rules is intended to funnel down to the item which best achieves the goals of each factor. For the first release, the order of rules will remain static. For the subsequent release, it is yet to be determined whether static or dynamic ordering will be required.
Scope
Requirements, implementation and deployment are staggered by release and grouped by customer.
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Item resolution factors
Following are the item resolution factors corresponding to each capability, existing and new development:
Circulation status (existing)
Geographic proximity (existing)
Loans (phase 1 dev)
Holds (phase 1 dev)
Preferred suppliers (phase 2 dev)
Auto request balancing (phase 2 dev)
Rules
Applying the following list of rules in the following order is intended to increase the probability of
On-shelf ranks above loans, ranks above holds
When all items are loaned, the item due soonest is selected
When all items have holds, the item with the least number of holds is selected
If a library system is unable to supply an item count of holds because the platform does not support it (e.g. Polaris), rank items from that library lower than other libraries that are able to provide hold count.
When all item resolution determinants are equal (e.g. all items on-shelf) and geographic proximity is enabled, use geographic proximity to determine which item is selected to place the request
Additional rules (defined at a later date)
When preferred suppliers are also enabled, use a preferred supplier from the same group.
If more than one supplier in the same group, use geographic proximity OR load balancing to make the selection
If a preferred supplier is not found, and more than one supplier is outside the preferred group, use geographic proximity or load balancing to make the selection,
Filter and Sort / Pool and Rank
...