Best-Hold Selection Sort Order

When an item is captured for a hold upon check-in, Evergreen evaluates the holds in the system that the item could fill. Evergreen then uses a set of rules, or a Best-Hold Selection Sort Order, to determine the best hold to fill with the item. Best-Hold Selection Sort Order (BHSSO) allows libraries to configure customized rules, whether by creating new sets of rules or modifying existing ones, for Evergreen to use to select the best hold to fill at opportunistic capture. These rules is that they answer the question, “What is important to your library when ordering holds to be filled?” BHSSOs are created in AdministrationServer AdministrationBest-Hold Selection Sort Order. A BHSSO is then set per organizational unit under Local AdministrationLibrary Settings EditorBest-hold selection sort order.

Preconfigured Best-Hold Orders

Evergreen comes with seven preconfigured Best-Hold Selection Sort Orders to choose from:

  • Traditional

  • Traditional with Holds-go-home

  • Traditional with Holds-always-go-home

  • Traditional with Holds-chase-home-lib-patrons

  • FIFO

  • FIFO with Holds-go-home

  • FIFO with Holds-always-go-home

Traditional

  • Uses Org Unit Proximity to identify the nearest hold to fill, prioritizing holds where the check-in/capture library is the same as the pickup library.

  • Can help fill holds more efficiently and reduce transit of items.

  • Holds are not filled in order they were placed.

FIFO (First In, First Out)

  • Follows a strict order of first-in, first-out rules.

  • Prioritizes the hold request time and fills holds in order of request time.

  • Can increase transits of items.

Holds Go Home

Holds Go Home and Holds Always Go Home allow libraries to determine how long they want to allow items to transit outside of the item’s home library, before it must return to its home library to fulfill any holds that are to be picked up there. Libraries can set this time limit in the library setting Holds: Max foreign-circulation time. Both Holds Go Home and Holds Always Go Home prioritize holds of patrons at the item-owning library. They can be used with Traditional and FIFO, though with FIFO, this means some holds will not be filled in strict FIFO order.

  • If a hold has been placed by a patron at the item’s owning library, and the item has not filled a hold for an owning library patron within the interval configured in “Max foreign-circulation time,” the item will go “home” to fill that patron’s hold.

Holds Always Go Home

  • If a hold has been placed by a patron at the item’s owning library, the next time the item is captured it will go “home” to fill that patron’s hold.

Traditional with Holds-chase-home-patrons

  • First introduced in 3.5.

  • Gives primary ranking to the Owning Lib to Patron Home Lib Proximity weight, which looks at the proximity between item-owning library and patron home library.

  • Prioritizes holds for patrons whose home library is the same as the item-owning library, regardless of pickup library.

  • This BHSSO may be useful for library systems that resource share and allow patrons to pick up holds at any branch or library within the resource sharing system, but want to ensure that their items are filling holds for their patrons first.

Table 1. Preconfigured Weights for Best-Hold Selection Sort Orders
ID Name Capture Lib to Pickup Lib Proximity Circ Lib to Request Lib Proximity Owning Lib to Patron Home Lib Proximity Adjusted Circ Lib to Pickup Lib Proximity Adjusted Capture Location to Pickup Lib Proximity Hold Priority Hold Cut-in-line State Hold Selection Depth Copy Has Circulated From Home Lately Hold Request Time Copy Has Been Home At All Lately

1

Traditional

2

3

1

4

5

6

7

2

Traditional with Holds-always-go-home

3

1

4

2

5

6

7

8

3

Traditional with Holds-go-home

3

4

2

5

6

7

1

8

4

FIFO

5

6

7

1

2

4

8

3

5

FIFO with Holds-always-go-home

6

1

7

2

3

5

4

8

6

FIFO with Holds-go-home

6

8

7

2

3

5

1

4

7

Traditional with Holds-chase-home-lib-patrons

4

2

1

5

3

6

7

8

9

Best-Hold Selection Sort Order Criteria

  • Adjusted Capture Location to Pickup Lib Proximity - The adjusted org unit proximity between the capture library and pickup library.

  • Adjusted Circ Lib to Pickup Lib Proximity - The adjusted org unit proximity between the circulation library and pickup library.

  • Capture Lib to Pickup Lib Proximity - The default org unit proximity between the capture library and pickup library.

  • Circ Lib to Request Lib Proximity - The default org unit proximity between the circulating library and request library.

  • Copy Has Been Home At All Lately - Tests whether the item has been at its owning library during the time frame set in the Library Settings Editor called “Max foreign-circulation time.” It looks for * completed transits to the owning library within the time frame specified.

  • Copy Has Circulated From Home Lately - Tests whether the item has circulated at its owning library during the time frame set in the Library Settings Editor called “Max foreign-circulation time.”

  • Hold Cut-in-line State - Looks for holds that have been manually set to the top of the holds queue.

  • Hold Priority - Looks at the Hold Priority field in the permission group configuration of the user receiving the hold.

  • Hold Request Time - Looks at the timestamp for when the hold request was created.

  • Hold Selection Depth - For boundary-restricted holds, this prioritizes more restricted holds over less restricted.

  • Owning Lib to Patron Home Lib Proximity - The default org unit proximity between the item-owning library and patron home library.

The adjusted org unit proximities are determined through Server AdministrationOrg Unit Proximity Adjustments.

Create a New Best-Hold Selection Sort Order

To create a new Best-Hold Selection Sort Order, go to Administration → Server Administration → Best-Hold Selection Sort Order.

  1. Click New Best-Hold Sort Order.

    New Best-Hold Selection Sort Order
  2. Assign your Best-Hold Selection Sort Order a Name.

  3. Next, use the numeric selectors next to each field to set the order that you would like Evergreen to check when looking for the best hold to fill with an item at opportunistic capture.

  4. Click Save to create your custom Best-Hold Selection Sort Order.

New Best-Hold Selection Sort Order

Edit an Existing Best-Hold Selection Sort Order

To edit an existing Best-Hold Selection Sort Order, go to Administration → Server Administration → Best-Hold Selection Sort Order.

  1. Find the Sort Order that you want to edit in the grid

  2. Select the row you need to edit and access the Actions Menu. The Actions Menu can be accessed in the upper right of the grid or by right-clicking the row.

  3. Choose Edit Selected. You can also access the Edit feature by double-clicking on a grid row.

    Edit Best-Hold Selection Sort Order
  4. Next, use the numeric selectors next to each field to set the new order that you would like Evergreen to check when looking for the best hold to fill with an item at opportunistic capture.

  5. Click Save to save your edits.

Edit Best-Hold Selection Sort Order

Tips for Customizing the New Best-Hold Selection Sort Order

  • The lower the number, the more important the criteria.

  • Not all criteria need to be used within a BHSSO configuration.

  • Hold Request Time can be viewed as the “tie-breaking” criteria.

Choosing the Best-Hold Selection Sort Order

The Best-Hold Selection Sort Order can be set for an Org Unit in the Library Settings Editor.

To select the Best-Hold Selection Sort Order that your Org Unit will use:

  1. Go to Administration → Local Administration → Library Settings Editor.

  2. Locate the setting Holds: Best-hold selection sort order, and click Edit.

  3. Choose the Context org unit for this setting.

  4. Select the Best-hold selection sort order, or Value, from the drop down menu.

  5. Click Update Setting.

Best-hold selection in the Library Settings Editor

Permissions to Use This Feature

To administer the custom Best-Hold Selection Sort Order interface, you need the following permission:

  • ADMIN_HOLD_CAPTURE_SORT