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

[UXPROD-3615] Record Contribution Enhancements ("Bibs" and "Items") for INN-Reach Central Server (Phase 3) Created: 17/Mar/22  Updated: 12/Jul/22  Resolved: 12/Jul/22

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Morning Glory (R2 2022)
Parent: Add Support for D2IR API Integration with INN-Reach Resource Sharing Systems

Type: New Feature Priority: P3
Reporter: Brooks Travis Assignee: Brooks Travis
Resolution: Done Votes: 0
Labels: consortia, d2ir-record-contribution
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
clones UXPROD-2764 Record Contribution Enhancements/Ongo... Closed
is cloned by UXPROD-3679 Record Contribution Enhancements ("Bi... In Refinement
Defines
is defined by MODINREACH-258 SPIKE: Determine Why Instances are Be... Closed
is defined by UIINREACH-55 Record Contribution: Provide manageme... Closed
is defined by UIINREACH-96 Manage contribution (cancellation): B... Closed
Relates
relates to MODINREACH-22 SPIKE: Verify Inventory Domain Events... Closed
Requires
requires UXPROD-2673 Implement Oauth2 Consumer for Request... Closed
requires UXPROD-3051 Create Settings For Managing Contribu... 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   

SPLIT FROM UXPROD-2764

Problem/Overview

This work was split into two phases:

  • Phase 1 is covered by UXPROD-3218
  • Phase 2 will cover ongoing record contribution and enhancements to the initial record contribution process UXPROD-2764
  • Phase 3 will cover UI enhancements and integration with back-end work from Phase 2

Original context
In an INN-Reach consortium, each participating library must contribute bibliographic records ("bibs") to the INN-Reach central server that correspond to items the contributing library wishes to include in the INN-Reach central catalog for discovery and/or lending. Records contributed should be able to be limited by some local criteria, and may need to be transformed before contribution (eg. to support record matching, contributed MARC record 001 field may need to be changed from FOLIO HRID to OCLC number). Records must be contributed in MARC21 encoded according to API specifications.

Whenever an inventory record is created, updated, or deleted, it should be evaluated for contribution or update. This would include any Title-level requests (when available) or new items added to associated holdings. Inventory records without associated item records should not be included until an associated item record is created.

In scope

  • Mechanism for filtering records to be contributed to the central server.
    • Ability to indicate whether a record should display in the central discovery catalog, and whether it should show as contributed by the contributing institution or the consortium.
  • Mechanism to generate and/or transform MARC21 records for indicated inventory record using a rule-based system.
  • System for maintaining record contribution status

Out of scope

  • Batch contribution of bibs.

Use case(s)

Proposed solution/stories
Given an inventory instance record is updated, the INN-Reach business logic module should receive a message that indicates what record has been modified and evaluate said record based on its configured contribution criteria, transform/generate an associated MARC21 record and pass it on to the associated Edge API for transmission to the INN-Reach Central server as appropriate.

Links to additional info

Questions

  • What mechanism can be used to notify the INN-Reach FOLIO module to evaluate an inventory instance for contribution/update?
  • What criteria are available for filtering records?
  • How will filters and record transformation be configured?
  • What kind of interface should be used to manage this functionality for multiple INN-Reach central servers?


 Comments   
Comment by Khalilah Gambrell [ 11/Jul/22 ]

Hey Mikita Siadykh and Brooks Travis, can this feature be moved to In Review or Closed?

Comment by Mikita Siadykh [ 12/Jul/22 ]

hi Brooks Travis 

looks like this one is ready for final review

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