Description

Save MARC_Authority + create Inventory Authority

NB: Save MARC_AUTHORITY action is implicit

Flow

1. JobDefinition (UUID, profile - defines job type: insert/update) for import created in mod-srm
2. MARC file + JobDefinition ID are uploaded from WEB client to mod-data-import
3. MARC records are packed into batches and put to Kafka queue DI_RAW_RECORDS_CHUNK_READ
   
4. mod-srm reads batches from the queue, validates, generates a UUID for Inventory record, and sets it to '999ff i' field and passes to mod-srs via Kafka queue DI_RAW_RECORDS_CHUNK_PARSED. Job starts on the first chunk received.
5. mod-srs stores records into PostgreSQL database and returns the result back via Kafka queue (broken records are also stored as 'error record') - DI_PARSED_RECORDS_CHUNK_SAVED
6. mod-srm reads the profile and creates JSON payload (containing parsed MARC, profile, mapping parameters) for processing. exports it to an appropriate Kafka queue (one message per MARC entry) - DI_SRS_MARC_AUTHORITY_RECORD_CREATED,
7. mod-inventory reads the message, map Authority from MARC with mapping rules. Stores (via OKAPI HTTP) in mod-inventory-storage. Exports message DI_COMPLETED

Diagram

Source