Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
stylenone

...

Overview

Introduce additional new item resolution capabilities that improves increases the volume of OpenRS borrowing and the speed of item 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 . Other item resolution capabilities will better balance the distribution of item requests for suppliers.

In the first release of new item resolution capabilities, OpenRS will allow requests on items with holds and, items that are checked out.

...

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 factorgoal(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.

...

Requirements, implementation and deployment are staggered by release and grouped by customer.

For MOBIUS, the scope of new development is limited toRelease 3 will meet the delivery of MOBIUS contractual development:

Jira Legacy
serverSystem Jira
serverIda6f93653-ee50-3e81-88ad-29eb84ada35c
keyDCB-1530

Jira Legacy
serverSystem Jira
serverIda6f93653-ee50-3e81-88ad-29eb84ada35c
keyDCB-1549

For GALILEO, the scope of new development is limited toRelease 6 will meet the delivery of GALILEO contractual development:

Jira Legacy
serverSystem Jira
serverIda6f93653-ee50-3e81-88ad-29eb84ada35c
keyDCB-1541

...

Following are the item resolution factors corresponding to each capability, . The list includes existing and new developmentcapabilities by release:

  • Circulation status (existing)

  • Geographic proximity (existing)

  • Loans (phase 1 devrelease 3)

  • Holds (phase 1 devrelease 3)

  • Preferred suppliers (phase 2 devrelease 6)

  • Auto request balancing (phase 2 devrelease 6)

Rules

Applying the The following list of rules in the following order is intended to increase the probability of 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 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.

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

...