Uploaded image for project: 'ui-data-import'
  1. ui-data-import
  2. UIDATIMP-885

856$3 not mapping into holdings record (no numeric subfield mappings are working)

    XMLWordPrintable

Details

    • Folijet Sprint 111, Folijet Sprint 112
    • 1
    • Folijet
    • R1 2021 Bug Fix
    • Lehigh, Simmons
    • Legitimate regression

    Description

      Overview: Cannot map data from a numeric subfield. (I tried using the $3 of an 856 field, but I think it's any numeric subfields). Regression - was previously fixed in MODDICORE-81

      Current workaround: No great one, would have to edit the MARC file pre-import to change any numeric subfields to alphas

      Steps to Reproduce:

      1. Log into FOLIO-snapshot as diku_admin
      2. Go to Settings/Data import
      3. Create field mapping profile 1
        • Name: Create instance
        • Incoming record type: MARC Bib
        • FOLIO record type: Instance
        • Cataloged date: ###TODAY###
      4. Create field mapping profile 2
        • Name: Create e-holdings with $3
        • Incoming record type: MARC Bib
        • FOLIO record type: Holdings
        • Permanent location: "Online (E)"
        • Digitization policy: 856$3
        • Electronic access:
          • Add these to existing
          • Relationship: "Resource"
          • URI: 856$u
          • Link text: 856$z
          • Materials specified: 856$3
      5. Create field mapping profile 3 (only difference from profile 2 is that 856$3 is replaced with 856$a)
        • Name: Create e-holdings with $a
        • Incoming record type: MARC Bib
        • FOLIO record type: Holdings
        • Permanent location: "Online (E)"
        • Digitization policy: 856$a
        • Electronic access:
          • Add these to existing
          • Relationship: "Resource"
          • URI: 856$u
          • Link text: 856$z
          • Materials specified: 856$a
      6. Create action profile 1
        • Name: Create instance
        • Action: Create
        • FOLIO record type: Instance
        • Link to Field mapping profile 1 (create instance)
      7. Create action profile 2
        • Name: Create e-holdings with $3
        • Action: Create
        • FOLIO record type: Holdings
        • Link to Field mapping profile 2 (Create e-holdings with $3)
      8. Create action profile 3
        • Name: Create e-holdings with $a
        • Action: Create
        • FOLIO record type: Holdings
        • Link to Field mapping profile 3 (Create e-holdings with $a)
      9. Create job profile 1
        • Name: Create instance and e-holdings with $3
        • Accepted data type: MARC
        • No match
        • Action: Create instance
        • Action: Create e-holdings with $3
      10. Create job profile 2
        • Name: Create instance and e-holdings with $a
        • Accepted data type: MARC
        • No match
        • Action: Create instance
        • Action: Create e-holdings with $a
      11. Go to Data Import and upload the attached file: 856 with 3.mrc
      12. Select the job Create instance and e-holdings with $3 and import the file
      13. Go to Inventory and search for together alone
      14. View the associated holdings, and check the Digitization policy and Electronic access/Materials specified fields to see if JSTOR-ADD-AGAIN populated into those fields
      15. Go to Data Import and upload the attached file: 856 with a.mrc
      16. Select the job Create instance and e-holdings with $a and import the file
      17. Go to Inventory and search for together together
      18. View the associated holdings, and check the Digitization policy and Electronic access/Materials specified fields to see if JSTOR-ADD-AGAIN populated into those fields

      Expected Results:

      • Data from 856 $3 should be populated into the Digitization policy and Electronic access/Materials specified fields when loading the 856 with 3.mrc file
      • Data from 856 $a should be populated into the Digitization policy and Electronic access/Materials specified fields when loading the 856 with a.mrc file

      Actual Results: The 856$a mapping works, but the 856$3 mapping does not. I think the problem may be with any numeric subfield in any field mapping profile. Needs checking with other subfield numbers in various free-text fields in instance, holdings, and field mapping profiles

      Additional Information: See attached video and MARC files

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                Ivan Kryzhanovskyi Ivan Kryzhanovskyi
                Ivan Kryzhanovskyi Ivan Kryzhanovskyi
                Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases