Load MARC Bib Record to create/update various records, but do not store the MARC

Purpose: To import data for Inventory or Acquisitions via a MARC record, but then do not save the MARC record in SRS

Sample use cases:

• MARC Bib or Holdings creates related inventory record, but library does not want SRS (so Inventory Source = FOLIO, not MARC)
• Brief MARC Bib supplies order or invoice data, but should not overlay a richer MARC SRS record

As a staff person working with imported files
I want to be able to specify whether an incoming MARC record should be saved in SRS or not
So that I can discard MARC records that are used for transport purposes only

Scenarios

1. Scenario 1
   • Given the Settings/Data import/Job profile
   • When Creating or Updating a Job profile and the Accepted data type = MARC
   • Then under the Accepted data type field, display a checkbox with label "Do not save MARC after import"
   • And default it to unchecked
   • See 2-Checkbox when Data type=MARC.PNG attached
2. Scenario 2
   • Given the Settings/Data import/Job profile
   • When Viewing a Job profile and the Accepted data type = MARC
   • Then under the Accepted data type field, display a checkbox with label "Do not save MARC after import", as checked or unchecked
   • And do not allow it to be edited
   • See 3-View-Checkbox unchecked.PNG and 4-View-Checkbox checked.PNG attached
3. Scenario 3
   • Given the Settings/Data import/Job profile
   • When a Job profile has Accepted data type = MARC and the checkbox for "Do not save MARC after import" = unchecked
   • Then when the file is imported
   • Save the new or updated MARC records to SRS
4. Scenario 4
   • Given the Settings/Data import/Job profile
   • When a Job profile has Accepted data type = MARC and the checkbox for "Do not save MARC after import" = checked
   • And there is an action profile linked to the job profile to
     • Create instance
     • Create holdings
     • Create item
     • Update holdings
     • Update item
   • Then when the file is imported
     • If the records create new Inventory Instances
     • Then make the Instance Source = FOLIO rather than MARC
     • And DO NOT save the new MARC records in SRS
     • If the records create or update Inventory Holdings or Items
     • Then leave the Instance source as-is
     • And DO NOT save the new MARC records
5. Scenario 5
   • Given the Settings/Data import/Job profile
   • When a Job profile has Accepted data type = MARC and the checkbox for "Do not save MARC after import" = checked
   • And there is an action profile linked to the job profile to
     • Update instance
   • Then when the job profile is saved
     • Uncheck the "do not save MARC" checkbox in the job profile (display as greyed out, unchecked, and uneditable in the Create/Edit screen)
   • And when the file is imported
     • SAVE the MARC record after import
   • NOTE: If the Update instance action is removed from the job profile, re-enable the "Do not save MARC after import" checkbox
6. Scenario 6
   • Given the Settings/Data import/Job profile
   • When a Job profile has Accepted data type = MARC and the checkbox for Do not save MARC after import = checked
   • And there is an action profile linked to the job profile to
     • Modify MARC
     • Update MARC
   • #* Then when the job profile is saved
     • Uncheck the "do not save MARC" checkbox in the job profile (display as greyed out, unchecked, and uneditable in the Create/Edit screen)
   • Then when the file is imported
     • And SAVE the MARC record after import
   • NOTE: If the Modify/Update MARC action is removed from the job profile, re-enable the "Do not save MARC after import" checkbox
7. Scenario 7
   • Ensure this story passes Accessibility testing
8. Scenario 8
   • Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot

OleksiiKuzminov Please create appropriate backend story and link to this one