SPLIT FROM UXPROD-2764 UXPROD-3615

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 ()

• Phase 4 will cover back-end enhancements to improve job management and monitoring

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

• Add the ability to pause a full contribution job

• Add the ability to update contribution statistics in "real-time"

• Make contribution activity "less chatty", if possible (coalesce updates when possible, perhaps?) 

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?