Purpose/Overview:
Provide a way to confirm the changes after they are committed to the database.
Requirements/Scope:

1. The functionality is available only for instances with their source set to MARC.

2. From the existing Confirmation form user can download .mrc file with the MARC records and the record reflect changes made to the existing SRS record:

   1. new fields and subfields are added

   2. existing fields are updated or removed as specified on the bulk edit form.

3. The is in MARC format and contain the changes committed to the database.

4. MARC fields provided on the MARC field bulk edit form are matched to the inventory instance note fields according to the existing matching profiles.

   1. Not all subfields will have their inventory instance representation

   2. Some MARC fields cannot be mapped to inventory instance record and the note will be displayed as the general note.

5. Multiple notes of the same type are separated with the “|” character.

6. If the note is staff only, the note is followed with “(staff only)” information.

7. The columns with all updated notes are visible.

Out of scope:

Preview of the records is covered in

Approach:

1. Prepared .mrc file should be imported with using data-import capabilities.

2. Unchanged records should be excluded from final mrc file that will be sanded to data-import.

3. Importing profile should be created and saved in data-import - separate component . Note: Profiles should be narked as hidden in scope of this story.

4. InstanceUpdateProcessor should be renamed to FolioInstanceUpdateProcessor, existing logic for source FOLIO should be saved.

5. MarcInstanceUpdateProcessor should be implemented to use data-import capabilities for updating instances with source MARC.

6. UpdateProcessorFactory should be reworked to support new processor type.

7. DataImport client should be implemented to cover full cycle of updating instances with source MARC based on already prepared .mrc file .

8. MarcUpdateService should be implemented to save marc files. This service should be integrated in the commit method of BulkOperationService.

9. MarcUpdateService should be resolved based on information on BulkOperation and used for saving changes.

10. Importing errors should be handled and saved according to existing errors handling flow .

Additional information

• UI representation:

• MARC 21 Note fields:

• Mapping profiles documentation:

Acceptance criteria:

• All requirements are met

• Unit and API tests are written/updated.