DCB loan policy flexibility based on library/agency code

Description

Objective:

Some libraries want different loan rules for items going to/from a specific library. Currently, all virtual items contain an effective location of “DCB”. Using a different data element than a location based data element (e.g. material types or loan type or patron type or any other) is not a viable means of solution.

Use cases:

Borrower loans for virtual items supplied by a specific library must use a circulation rule that is different than other members. The associated loan period should be set in the borrower library and the supplying library.

Circulation rules must be configured in the borrower library and corresponding circulation rules in the supplying library such that the supplying library loan period supports the special relationship between the two organizations.

Although MOBIUS has only two such library, the solution should be extensible to the use case for pickup anywhere AND for additional special relationships (whether one-to-one or one-to-many relationships).

In Scope:

FOLIO (Polaris and Sierra are already able to accommodate such relationships via existing configuration).

Out of scope:

tbd

Solution:

to store the unique libraryCode / agency code into the virtual item institution location (instead of the current value of "DCB").

Priority

Fix versions

Development Team

Volaris

Assignee

Solution Architect

Parent Field Value

None

Parent Status

None

is defined by

Checklist

hide

Activity

Show:

Details

Reporter

PO Rank

0

Front End Estimate

Out of scope

Release

Trillium (R2 2025)

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created January 7, 2025 at 3:44 PM
Updated 16 hours ago
TestRail: Cases
TestRail: Runs

Flag notifications