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

[UXPROD-3536] INN-Reach: Clean up "Virtual" Items and Associated Loan, Request, and Inventory Records Created: 01/Feb/22  Updated: 30/Nov/23  Resolved: 22/Feb/23

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

Type: New Feature Priority: P2
Reporter: Brooks Travis Assignee: Tim Auger
Resolution: Done Votes: 0
Labels: inn-reach, inventory, loans, requests, resourceaccess
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
is blocked by MODINREACH-335 Scheduler test case for FINAL_CHECKIN... Closed
Defines
is defined by MODINREACH-254 Delete Item, Holdings, and Instance R... Closed
is defined by MODINREACH-255 Make Clean-up of INN-Reach Patron Hol... Closed
Relates
relates to MODINREACH-316 UXPROD-3536 - CANCEL_REQUEST - Clean ... Closed
relates to MODINREACH-317 UXPROD-3536 - BORROWING_SITE_CANCEL -... Closed
relates to MODINREACH-318 UXPROD-3536 - FINAL_CHECKIN - Clean u... Closed
relates to MODINREACH-311 SPIKE: For UXPROD-3536 Closed
Release: Orchid (R1 2023)
Epic Link: Add Support for D2IR API Integration with INN-Reach Resource Sharing Systems
Front End Estimate: Out of scope
Back End Estimate: XXL < 30 days
Back-End Confidence factor: 90%
Development Team: Volaris
PO Rank: 100
Rank: Cornell (Full Sum 2021): R5
Solution Architect: Raman Auramau

 Description   

Current situation or problem:

When creating a Patron Hold transaction in mod-inn-reach, the module creates a corresponding Inventory record set (Instance/Holdings/Item) to represent the requested item. This can quickly lead to a number of "stub" records littering Inventory. When terminating a patron hold transaction, we need to clean up these records. In order to not break the UI in the circulation apps, we need to clean up the associated request and loan records, as well. There should be a mechanism to perform this clean-up on-demand, as well.

In scope

An approach to delete Inventory records created by mod-inn-reach related to a patron hold transaction without causing issues with the related circulation records (loans, requests, fees/fines)

Out of scope

Modifications to the existing loan (and requests?) anonymization functionality.

Use case(s)

Proposed solution/stories

Links to additional info

Questions

  • How will this impact the ability to generate aggregate circulation statistics?
  • Should we delete or just anonymize loans?
  • What level of anonymization can be done to a request record given present functionality?


 Comments   
Comment by Tim Auger [ 18/Sep/22 ]

I'm not a proponent of giving users the ability to "clean up" whenever they want or even to clean up the database resulting from bad application behavior. I'd rather spend time now figuring out where the holes are and plug them and then have EBSCO clean up to a pristine state and then monitor. Doing otherwise will likely result in covering up problem cases that should be addressed with code fixes.

Comment by Khalilah Gambrell [ 29/Sep/22 ]

Per Brooks. We do not clean up INN-Reach instance/holdings/item record used for handling requests. WE need to clean these up once INN-Reach transaction is terminated/complete.

Comment by Tim Auger [ 29/Sep/22 ]

My comments above are based on an assumption that turned out to be untrue. What is being asked for is to automatically cleanup the temporary stub records used for the transaction. Once the transaction is complete, the corresponding temporary stub records should be removed from inventory.

Comment by Tim Auger [ 11/Oct/22 ]

Now that I better understand the ask, we will need to cleanup the existing data as a one-time cleanup.

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