This document will illustrate changes to data import to facilitate a reliable and performant system for ingesting MARC records etc into FOLIO.

Goals

• Journey Simplification: The current flow involves back and forth communication between actors in the system with recurring expensive operations. Also means that the multiple actors makes troubleshooting harder, tracing the journey through multiple modules.
  This will create avenue to allow complex functionality to be developed within a simple paradigm.

• Cross-Domain Flexibility: There are scenarios where actions in one domain e.g. orders is dependent on another domain e.g. inventory for perform a complete unit of work. Making that happen today is complicated via “post processing” and generally leaves room for only one dependent action to be performed i.e can only create a instance for the order, but inventory cannot interact with another domain cleanly within the purview of the original create order request.

• Incoming Record Journey Logging: Show the journey of an incoming record in the journal.

• Job Execution Status: Job execution can be broken at any actor but the status might not be communicated appropriately system wide. Provide structures that will allow good notification of job executions.

• Error Codes: Introduce error codes so that user-friendly messages are shown to the user instead of coding exceptions.

• Job Profile Validation: Increase validations performed on job profiles before persistence.

• Multiple Results from Match Profile: Allow multiple results to be returned by a Match Profile in a Job Profile.

...