Add validation of Folio Record Type upon linking of Action and Mapping profile

Overview: The imported file is displayed in the 'Running' section after running the import and is not completed.

Preconditions:

1. The user is logged into application as admin.

Steps to Reproduce:

1. Go to Settings/Data import/MARC field protections. If these fields are not already in the field protection settings, add these two:

• • Field 020, Ind 1 *, Ind 2 *, Subfield a, Data *
  • Field 514, Ind 1 *, Ind 2 *, Subfield *, Data *

       2. Create and save field mapping profile 1:

• • Name: Update MARC Bib with protections
  • FOLIO record type: MARC Bibliographic
  • Field mappings for MARC: Update
  • In the details, ignore the Updates details
  • In the Override protected fields section, do not check any rows
    Save the profile.

        3. Create and save field mapping profile 2:

• • Name: Update instance 1
  • FOLIO record type: Instance
  • Add an administrative note, e.g. "This note was added when the MARC Bib was updated to check field protections"

       4. Create and save field mapping profile 3:

• • Name: Update MARC Bib with protection OVERRIDES
  • FOLIO record type: MARC Bibliographic
  • Field mappings for MARC: Update
  • In the details, ignore the Updates details
  • In the Override protected fields section, put a checkmark in the "Override" box for the 020 and 514 fields

       5. Create and save field mapping profile 4:

• • Name: Update instance 2
  • FOLIO record type: Instance
  • Add an administrative note, e.g. "This note was added when the MARC Bib was updated to check field protection OVERRIDES"

       6. Create and save 4 Action profiles, and link to the above field mapping profiles:

• • Action profile 1: Update MARC Bib with protections, Action: Update, FOLIO record type: MARC Bibliographic
  • Action profile 2: Update instance 1, Action: Update, FOLIO record type: Instance
  • Action profile 3: Update MARC Bib with protection OVERRIDES, Action: Update, FOLIO record type: MARC Bibliographic
  • Action profile 4: Update instance 2, Action: Update, FOLIO record type: Instance

       7. Go to Settings/Data import/Match profiles, and either confirm, that this match profile exists, or if not, then create and save it

• • Name: 001 to 001 MARC Bib
  • MARC Bib linked to MARC Bib
  • Incoming MARC Bib record: Field: 001, all others [blank]
  • Exactly matches
  • Existing MARC Bib record: Field: 001, all others [blank]

       8. Go to Settings/Data import/Job profiles, and create and save Job profile 1

• • Name: Update 1: MARC Bib with protections
  • Accepted data type: MARC
  • Match profile: 001 to 001 MARC Bib
  • For matches:
  • First assign Action profile: Update MARC Bib with protections
  • Then assign Action profile: Update instance 1
    The Update MARC Bib action must be before the Update instance action

       9. Go to Settings/Data import/Job profiles, and create and save Job profile 2

• • Name: Update 2: MARC Bib with protections
  • Accepted data type: MARC
  • Match profile: 001 to 001 MARC Bib
  • For matches:
  • First assign Action profile: Update MARC Bib with protection OVERRIDES
  • Then assign Action profile: Update instance 2
    The Update MARC Bib action must be before the Update instance action

       10. Import the first attached MARC file, named oneMarcBib-BeforeOverride.mrc, using the default job profile named Default - Create instance and SRS MARC Bib

       11. Copy the instance HRID.

       12. Open the other two attached MARC files in MARCedit:

• • oneMarcBib-Rev1-Protect.mrc
  • oneMarcBib-Rev2-Override.mrc
    Paste the Instance HRID into the 001 field, then recompile the records into .mrc files

       13. Import the first update file, named oneMarcBib-Rev1-Protect.mrc, using the job profile named MARC Bib with protections

       14. Import the second update file, named oneMarcBib-Rev1-Override.mrc, using the job profile named MARC Bib with protection OVERRIDES

       15. Pay attention to the file in the 'Running' section.

Expected Results: Import was completed with no errors.

Actual Results: The imported file is displayed in the 'Running' section after running the import and is not completed.