...
All request capabilities must be compatible with one another and yet must stand independently without reliance on any 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 goal(s) of the capability. 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
Releases
Requirements, implementation and deployment are staggered by release and grouped by customer.
Release 3 will meet the delivery of MOBIUS contractual development:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Release 6 will meet the delivery of GALILEO contractual development:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Functionality
fdjkakjl
Item resolution factors
Following are the item resolution factors corresponding to each capability. The list includes existing and new capabilities by release:
Circulation status (existing)
Geographic proximity (existing)
Loans (release 3)
Holds (release 3)
Preferred suppliers (release 6)
Auto request balancing (release 6)
Rules
Loans and holds
The following rules ranked by order of evaluation are intended to support the goals for each capability:
On-shelf ranks above loans, ranks above holds
When all items are loaned, the item due soonest is selected
Overdue items are not resolvable.
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
If no other resolution determinants are enabled, choose an item at random.
Preferred suppliers and auto request balancing
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
Acceptance Criteria
When an item is not selectable…
When an item…