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

[UXPROD-2787] Handle INN-Reach Borrower Renewal Requests (Borrowing Library) Created: 26/Oct/20  Updated: 18/Feb/22  Resolved: 18/Feb/22

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Lotus (R1 2022)
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, d2ir-circulation-flow
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by MODINREACH-163 INN-Reach Circulation Flow: React to ... Closed
Relates
relates to MODINREACH-10 SPIKE: Investigate Possible Methods t... Closed
Requires
requires UXPROD-2673 Implement Oauth2 Consumer for Request... Closed
requires UXPROD-3380 Add Kafka Message Queues to Select Ci... Closed
Epic Link: Add Support for D2IR API Integration with INN-Reach Resource Sharing Systems
Front End Estimate: Out of scope
Back End Estimate: XL < 15 days
Development Team: Volaris
PO Rank: 90
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:
When a renewal is requested by the borrower on an INN-Reach, FOLIO must send a request to the central server, which will then be passed on to the owning site for verification. Ideally, the renewal in FOLIO would not process until verification was received.

In scope

  • A method for notifying the INN-Reach module(s) of loan renewal requests.
  • Logic for determining whether a renewal request is associated with an INN-Reach request and notifying the INN-Reach central server, as required.
  • A method for denying/allowing renewal based on the response from the Central Server

Out of scope

Use case(s)

Proposed solution/stories
Ideal: The ability to "plug-in" to the renewal request flow and "wait" on the response from the Central server before proceeding with the renewal.
"Thin thread": Process the renewal request according to local circulation rules/policies and then modify the loan as needed after the central server responds.

Links to additional info

Questions

  • How should/could we handle the UI/UX in the thin-thread story for the renewing patron so as to minimize confusion?


 Comments   
Comment by Brooks Travis [ 18/Feb/22 ]

Verified in Rancher

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