Overview
...
Overview
Item resolution is the last in a series of steps to determine which item OpenRS will select for placing a request. Currently, items that are checked out or have item holds cannot be requested via OpenRS. The purpose of DCB-1530 and DCB-1549 is to augment the existing item resolution capabilities such that checked outs and items with holds can be considered for selection. The business goal of these capabilities is to increase the volume of OpenRS borrowing and to increase the speed of item delivery to patrons. Other item resolution capabilities will better balance . These two issues are contractual obligations to MOBIUS but are likely to be used by GALILEO and other new OpenRS consortium.
Future item resolution development for GALILEO (DCB-1540 and DCB-1541) have the business goal of better balancing the distribution of item requests for suppliers. In the first release of new item resolution capabilities, OpenRS will allow These capabilities are outside the scope of this development.
Functionality
Allow requests on items with holds
...
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 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)
...
With the exception of Polaris libraries, item hold counts are currently returned from the member library systems via RTAC to DCB. When DCB is returned an item with a hold count of 1 or greater, that item is removed from the list of potentially selectable items while DCB continues to evaluate the selectability of each item. See From Contribution to Selectable for additional informations.
DCB-1530 allows for OpenRS requests to be placed on items with holds. A set of rules determines how item holds are evaluated when a group of copies are on-shelf (available), some that are checked out and some with holds. Please see the Rules section below for rule criteria and ranking.
If a library system is unable to supply an hold item count for any reason, the items from that potential supplier are ranked lower than other libraries that are able to provide a hold count.
A consortium is able to enable or disable this feature across all members of the consortium.
Allow requests on loaned items
Currently, items on loan (i.e. checked out) are not allowed to be requested via OpenRS. With DCB-1549, the ability to place a hold on loaned items will be available in OpenRS.
Each platform needs a definition of what constitutes a loaned item:
FOLIO items are on loan when
circStatus
=Checked out
Polaris items are on loan when
circStatus
=Out
Sierra items are on loan when
itemStatus.duedate
!= null (i.e., is checked out)
[will need to reconcile with existing “Available rules” From Contribution to Selectable ”]
A consortium is able to enable or disable this feature across all members of the consortium.
Compatible and independent
All request capabilities must be compatible with one another and, yet, must stand independent without reliance on any other resolution capability. So, as a consortium administrator, I can choose to allow patrons to requests items with holds and loaned items or one and not the other or, neither. This means that both features must be enabled independently of one another.
Rules
Loans and holds
The following rules ranked by order of evaluation are intended to support the goals for each capability:. OpenRS will select the item with the highest ranked criteria.
On-shelf ranks above loans, ranks
Loans rank above holds
When all items are loaned, the item due soonest is selected 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 selection criterion 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 selection criterion 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…
Acceptance criteria
See Rules
Scope
Platforms/LMS: Polaris, FOLIO, Sierra
Can support platforms that do not return hold data
Uses existing methods to get holds from an LMS except where noted
Manual selection of items
Out of scope
bib/instances/volume holds