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

[UXPROD-2788] Handle "Move Request" Action on INN-Reach Requests (Owning Site) Created: 26/Oct/20  Updated: 02/Mar/22  Resolved: 02/Mar/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-122 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: Large < 10 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 request is assigned to an owning site by the Central Server, the owning site has the option to "transfer" that request to another appropriate item in their collection. In FOLIO parlance, this is known as "moving" the request. If a request created by an INN-Reach request is moved to another item by the owning site, the Central Server should be notified of the move/transfer.

In scope

  • A method for notifying the INN-Reach module(s) when a request is moved to another item.
  • Logic for evaluating notifications that a request has been moved and notifying the Central Server as required.

Out of scope

Use case(s)

Proposed solution/stories
A message should be published to a message queue (eg. PubSub/Kafka) whenever a request is moved to another item, so that the INN-Reach modules can subscribe to these messages and evaluate the associated request for further processing/action.

Links to additional info

Questions



 Comments   
Comment by Brooks Travis [ 02/Mar/22 ]

Verified in Rancher

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