Add Support for D2IR API Integration with INN-Reach Resource Sharing Systems (UXPROD-2598)

[UXPROD-3470] INN-Reach: Support INN-Reach Only Manual Patron Blocks Created: 04/Jan/22  Updated: 23/Feb/23  Resolved: 23/Feb/23

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: TBD
Parent: Add Support for D2IR API Integration with INN-Reach Resource Sharing Systems

Type: New Feature Priority: P3
Reporter: Brooks Travis Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: inn-reach, resourceaccess, usermanagement
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by MODINREACH-208 INN-Reach Settings: Store Configurati... Draft
is defined by MODINREACH-209 INN-Reach Settings: API to CRUD Confi... Draft
is defined by UIINREACH-130 INN-Reach Settings: Add Setting to Co... Draft
Epic Link: Add Support for D2IR API Integration with INN-Reach Resource Sharing Systems
Front End Estimate: XL < 15 days
Back End Estimate: XL < 15 days
Development Team: Volaris
PO Rank: 0
Rank: Cornell (Full Sum 2021): R5

 Description   

Current situation or problem:

The current implementation of patron blocks in INN-Reach relies on the patron blocks supported by the existing FOLIO circulation modules (mod-patron-blocks). It does not offer the ability to restrict patrons ONLY from placing INN-Reach requests/holds.

In scope

Implement a mechanism to indicate that a patron is blocked from placing INN-Reach requests when performing patron authorization via edge-inn-reach/mod-inn-reach.

Out of scope

  • INN-Reach specific modifications to existing patron block functionality.
  • Automated INN-Reach blocks (existing automated blocks will block INN-Reach as well)

Use case(s)

Some consortia or libraries have different criteria for when a patron should be blocked from placing INN-Reach holds vs. accessing circulation services at their home library. In these cases, the library needs a method to indicate the INN-Reach block without affecting local circulation/requests.

Proposed solution/stories

  • Utilize a custom field, similar to the method used to indicate patron agency in a multi-agency local server, to indicate that a patron should be blocked from INN-Reach transactions

Links to additional info

Questions

  • Is there interest in a general "ILL" block enhancement to the existing manual blocks
  • Will a manually controlled custom field work in an environment that uses mod-user-import to manage its patrons?


 Comments   
Comment by Tim Auger [ 02/Jan/23 ]

Until we know the extent of our contractual obligation, putting this on ice.

Generated at Fri Feb 09 00:32:15 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.