Uploaded image for project: 'mod-source-record-storage'
  1. mod-source-record-storage
  2. MODSOURCE-534

Matching on created 035 does not work in Lotus or MG (MG bugfix)

    XMLWordPrintable

Details

    • 1
    • Folijet Support
    • Morning Glory (R2 2022) Bug Fix
    • !!!ALL!!!
    • Legitimate regression

    Description

      Overview:

      Prior to Lotus, the 035 that was created from the incoming record's 001 and 003 manipulation could be used as a match point. Since Lotus that created 035 no longer seems to be part of the matching logic.

      Steps to Reproduce:

      1. Log into Morning Glory, Lotus, and/or Kiwi - to test and compare in all 3 environments
      2. Go to the Data Import app, and upload the attached MARC file MODSOURCE-521.mrc
        • NOTE: It's important to check that the System control number that is created does not already exist in the environment. Otherwise you will not be able to get a unique match for the second half of the test
      3. Select the "Default - Create instance and SRS MARC Bib" job profile, and confirm the import
      4. Once the import finishes, click on the file name to view the log
      5. Click on "Created" for the Instance, and view the Instance in Inventory. There should be an identifier with
        • Type: System control number
        • Identifier: (NhFolYBP)2304396
      6. Click on Actions/View source
        • In the MARC record, there should be an 035 field that looks like this: 035 $a (NhFolYBP)2304396
        • There should not be any other 035s in the MARC record
      7. Go to Settings/Data import/Match profiles and create the following:
        • Name: Match on newly-created 035
        • Incoming record: MARC Bib
        • Existing record: Instance
        • MARC Bibliographic field:
        • Field: 035 In1: * In2: * Subfield: a
        • Exactly matches
        • Existing Instance record field: Identifier: System control number
      8. Save the newly-created profile
      9. Go to Settings/Data import/Field mapping profiles and create the following:
        • Name: Update instance via 035
        • Incoming record type: MARC Bibliographic
        • FOLIO record type: Instance
        • Administrative notes:
          • Add these to existing
          • Note: "This instance was updated, plus a new subject heading was added"
          • For Kiwi or Lotus, add a Statistical code instead of an Admin note
      10. Save the new profile
      11. Go to Settings/Data import/Action profiles and create the following:
        • Name: Update instance via 035
        • Action: Update
        • FOLIO record type: Instance
        • Click "Link profile" and connect the field mapping profile created in step 9
      12. Save the new profile
      13. Go to Settings/Data import/Job profiles and create the following:
        • Name: Update instance via 035
        • Click + and select the Match profile created in step 7
        • For matches, click + and select the Action profile created in step 11
      14. Save the newly-created job profile
      15. Go to the Data import app and upload the attached MODSOURCE-521_rev.mrc MARC file (which is exactly the same as the first file, except it has 1 additional subject heading
      16. Select the newly-created job profile and import the file
      17. Click on the file name to view the log results
      18. Click on the "Updated" hotlink and view the Instance
      19. Do the same steps with the other MARC files: MODSOURCE-521_with_035.mrc (create) and MODSOURCE-521_with_035_rev.mrc (update)

      Expected Results: (whether there is an existing 035 in the MARC record or not)

      • The new Admin note (MG) or Stat code (Lotus/Kiwi) displays in the Instance
      • There is an additional subject heading
      • In the MARC record (view source) there is only 1 035 field
      • However, per jenncolt's note: The record does not match (in Lotus). It was found that if the incoming record had no existing 035 that the matching will work, but many incoming vendors would have an 035 OCLC number for instance as well as a vendor 035. Adding a qualifier did not help if there were existing 035s.
      • From A-M: I added another set of MARC files to use that already contained an 035, and made a video covering all 3 envs showing the results

      Actual Results 1: (no existing 035)

      • Kiwi and Lotus: I saw the expected results
      • Morning Glory: The expected updates happened to the instance, BUT a hybrid 035 was created, based on the 001 HRID of the existing SRS MARC Bib and the 003 of the incoming updated MARC Bib. This hybrid 035 should NOT be created

      Actual Results 2: (an existing 035 in the record, but not the 035 being used for matching to the instance)

      • Kiwi:
        • Existing 035 (OCLC number) was retained - CORRECT
        • New 035 (made of 001+003 of the incoming record) was added - CORRECT
        • Match happened properly and the instance was updated - CORRECT
      • Lotus:
        • Existing 035 (OCLC number) was retained - CORRECT
        • New 035 (made of 001+003 of the incoming record) was added - CORRECT
        • Match did not happen, and the Instance was not updated - BUG
      • Morning Glory:
        • Existing 035 (OCLC number) was retained - CORRECT
        • New 035 (made of 001+003 of the incoming record) was added - CORRECT
        • Match did not happen, and the Instance was not updated - BUG

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                Kateryna Senchenko Kateryna Senchenko
                jenncolt Jenn Colt
                Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases