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

[UXPROD-2777] INN-Reach: Submit Local Server Locations to INN-Reach Central Server Created: 23/Oct/20  Updated: 27/Oct/21  Resolved: 15/Oct/21

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

Type: New Feature Priority: TBD
Reporter: Brooks Travis Assignee: Brooks Travis
Resolution: Done Votes: 0
Labels: consortia
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by MODINREACH-11 Create a Data Model or Models to Stor... Closed
is defined by MODINREACH-17 Reference Data: INN-Reach Compatible ... Closed
is defined by MODINREACH-36 Reference Data: INN-Reach Compatible ... Closed
is defined by MODINREACH-46 System Configuration: Submit Mapped L... Closed
is defined by UIINREACH-16 INN-Reach General Settings: INN-Reach... Closed
Requires
requires UXPROD-2673 Implement Oauth2 Consumer for Request... Closed
Epic Link: Add Support for D2IR API Integration with INN-Reach Resource Sharing Systems
Development Team: Volaris
PO Rank: 95
Rank: Chicago (MVP Sum 2020): R5
Rank: Cornell (Full Sum 2021): R5
Rank: Duke (Full Sum 2021): R5
Rank: 5Colleges (Full Jul 2021): R5
Rank: GBV (MVP Sum 2020): R5
Rank: Grand Valley (Full Sum 2021): R2
Rank: MO State (MVP June 2020): R2
Rank: TAMU (MVP Jan 2021): R5
Rank: U of AL (MVP Oct 2020): R5

 Description   

Current situation or problem:
In an INN-Reach consortium, each participating local server must provide a list of location (branches + shelving locations) to the central INN-Reach server. When changes are made to the list of locations on the local server, this information must be transmitted to the central server. INN-Reach location codes are limited to five (5) characters and must be unique per local server.

In scope

  • A system to manage mapping between FOLIO and INN-Reach location codes
  • A mechanism for detecting changes to locations and either updating them or alerting a system admin that an action is required (eg. a location description/discovery name is updated vs. a new location is added/removed).

Out of scope

  • Mechanism for determining the correct location code to be included on contributed item records.

Use case(s)

Proposed solution/stories
System administrators should be able to use a FOLIO settings interface to manage the mapping configuration between FOLIO locations (including campuses and libraries) and INN-Reach locations. One INN-Reach location/description should be able to represent multiple FOLIO locations/libraries/campuses. The list of INN-Reach locations is editable at the central server, and an API is provided to download the current list for comparison. A mismatch should trigger an alert to a FOLIO administrator.

Whenever a location is added or updated, the INN-Reach integration system should be notified to evaluate the change and take action based on configured rules and preferences.

Links to additional info

Questions

  • What mechanism can be used to notify the INN-Reach FOLIO module(s) to evaluate a new or updated location?
  • How can system administrators be notified when a new location requires action on their part?
  • How can system administrators be notified when the central location list does not match the configuration on the local server?
  • What kind of interface should be used to manage this functionality for multiple INN-Reach central servers?

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