Uploaded image for project: 'mod-di-converter-storage'
  1. mod-di-converter-storage
  2. MODDICONV-324

Cannot update "MARC auth" record using edited "Match profile" if "Ind1" and "Ind2" are blank in "Match criterion"

    XMLWordPrintable

Details

    • Folijet Sprint 176
    • 0
    • Folijet
    • Poppy (R2 2023) Bug Fix
    • Hide
      1) Delete edited by user Match profile with connected Action Profile and Mapping Profile >> Delete Job profile
      2) Create a totally new Job profile with the necessary configuration.
      Show
      1) Delete edited by user Match profile with connected Action Profile and Mapping Profile >> Delete Job profile 2) Create a totally new Job profile with the necessary configuration.
    • !!!ALL!!!
    • Not a bug
    • Poppy (R2 2023), Orchid (R1 2023)

    Description

      Overview: Cannot update "MARC auth" record using edited "Match profile" if "Ind1" and "Ind2" are blank in "Match criterion"
      Steps to Reproduce:

      1. Log into Snapshot FOLIO environment as User with following permissions:
        Data import: Can upload files, import, and view logs
        Settings (Data import): Can view, create, edit, and remove
        MARC Authority: View MARC authority record
      2. Go to "Settings" > "Data import" > "Field mapping profiles"
      3. On the "Field mapping profiles" list, go to "Actions" menu and select "New field mapping profile" option:
        Enter a Name - "Update MARC auth"
        For Incoming record type, select "MARC Authority"
        For FOLIO record type, select "MARC Authority"
        For Field mappings for MARC, select "Updates"
        Click on the "Save as profile & Close".
      4. Go to "Settings" > "Data import" > "Action profiles"
      5. On the "Action profiles" list, go to "Actions" menu and select "New action profile" option:
        Enter a Name - "Update MARC auth"
        For Action, select "Update (all record types except Orders, Invoices, or MARC Holdings)"
        For FOLIO record type, select "MARC Authority"
        For Associated field mapping profile, link the field mapping profile you created at previous step - "Update MARC auth".
        Click on the "Save as profile & Close".
      6. Go to "Settings" > "Data import" > "Match profiles"
      7. On the "Match profiles" list, go to "Actions" menu and select "New match profile" option:
        Enter a Name - "Update MARC auth 010 $a match"
        For Incoming records, select "MARC Authority"
        For Existing records, select "MARC Authority"
        Match criteria: MARC Authority field in incoming record > 
        Fill in Field - "010"
        In.1 - leave blank
        In.2 - leave blank
        Subfield - "a"
        Match criterion: MARC Authority field in existing record > enter the same values as for incoming record.
        Click on the "Save as profile & Close".
      8. Go to "Settings" > "Data import" > "Job profiles"
      9. On the "Job profiles" list, go to "Actions" menu and select "New job profile" option:
        Enter a Name - "Update MARC auth 010 $a match"
        For Accepted data type, select "MARC"
        For Overview, Select Add Match and choose the Match profile you created
        For Matches, Select Action and choose the Action profile you created
        For Non-Matches, Select Action and choose the Action profile:  Default - Create SRS MARC Authority
        Click on the "Save as profile & Close".
      10. Go to "Data import" app and import original "MARC authority" record (MARC_Auth_Original.mrc) using "Default - Create SRS MARC Authority" job profile
      11. Update imported original "MARC authority" record by "MARC authority" record with updates (MARC_Auth_update_1.mrc) using created by you "Update MARC auth 010 $a match" job profile
      12. Go to "Settings" > "Data import" > "Match profiles"
      13. On the "Match profiles" list, open created by your match profile "Update MARC auth 010 $a match" >> Click on the "Actions" menu and select "Edit" option:
        Update Match criteria: MARC Authority field in incoming record > 
        Fill in Field - "010"
        In.1 - 1
        In.2 - 2
        Subfield - "a"
        Match criterion: MARC Authority field in existing record > enter the same values as for incoming record.
        Click on the "Save as profile & Close".
      14. On the "Match profiles" list, open edited by you match profile "Update MARC auth 010 $a match" >> Click on the "Actions" menu and select "Edit" option:
        Update Match criteria: MARC Authority field in incoming record > 
        Fill in Field - "010"
        In.1 - leave blank
        In.2 - leave blank
        Subfield - "a"
        Match criterion: MARC Authority field in existing record > enter the same values as for incoming record.
        Click on the "Save as profile & Close".
      15. Go to "Data import" app and update imported and updated once "MARC authority" record by "MARC authority" record with updates (MARC_Auth_update_2.mrc) using created and updated by you "Update MARC auth 010 $a match" job profile

      Expected Results: "MARC authority" record successfully updated, regardless of the fact that user edited "Match profile".
      Actual Results: Update Job finished with "Completed with errors" status. There is no error log on UI.
      In response, the following message is displayed: "JobSummary for jobExecutionId: '<<job UUID>>' was not found"
      Additional Information: See attached screencast: MODDICONV-324_steps_1-9.webmMODDICONV-324_steps_10-15.mp4
      Interested parties: abreaux , MaksymI , kgambrell 

      TestRail: Results

        Attachments

          1. MARC_Auth_Original.mrc
            1 kB
          2. MARC_Auth_update_1.mrc
            1 kB
          3. MARC_Auth_update_2.mrc
            1 kB
          4. MODDICONV-324_steps_10-15.mp4
            17.32 MB
          5. MODDICONV-324_steps_1-9.webm
            19.43 MB
          6. MODDICONV-324_verified.png
            MODDICONV-324_verified.png
            129 kB

          Issue Links

            Activity

              People

                rtaylor@ebsco.com Ryan Taylor
                valpil Valery Pilko
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases