Contribute Inventory Item Records ("Items") to INN-Reach Central Server

Current situation or problem:
In an INN-Reach consortium, each participating library must contribute item records ("items") 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 include holdings data (eg. online access URLs). Contributed records must include

Whenever an inventory item record is created, updated, or deleted, it should be evaluated for contribution or update. This includes local requests or updated circulation status (including due date), effective call number, effective location, item notes, copy number, volume designation, and item type.

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.
• System for maintaining record contribution status.
• Batch contribution by instance ("bib").

Out of scope

• Contribution of "Bib" records.
• Local location to INN-Reach location mapping
• Local to INN-Reach status mapping

Use case(s)

Proposed solution/stories
Given an inventory item record (or holdings record with associated item) 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, generate the required JSON payload 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 items (and holdings) for contribution/update?
• What criteria are available for filtering records?
• How will filters be configured?
• How will we map FOLIO locations to INN-Reach location codes (5-character limit)?
• How will we map FOLIO statuses to INN-Reach circulation statuses?
• What kind of interface should be used to manage this functionality for multiple INN-Reach central servers?