Uploaded image for project: 'data-import-processing-core'
  1. data-import-processing-core
  2. MODDICORE-187

Blank fields generated from MARC mapping create invalid Instance records in Inventory KIWI BF

    XMLWordPrintable

    Details

    • Template:
    • Story Points:
      3
    • Development Team:
      Folijet Support
    • Release:
      R3 2021 Bug Fix
    • Potential Workaround:
      Edit data in quickMARC to change to subfields that are mapped or fields that are not mapped at all.
    • Affected Institution:
      Cornell, TAMU

      Description

      Overview: MARC subfields not mapped to Inventory Instance elements can generate blank Instance fields. These blank fields make the Instance invalid.

      Steps to Reproduce - edit via quickMARC:

      1. Log into Juniper Bugfest as User with permission to edit instances and to use quickMARC
      2. Open a record with source=MARC (ex: hrid ins00007284163)
      3. Select Actions–>Edit in quickMARC
      4. Add a 590 field with text in a $3 and no $a (ex; 590
        $3 materials specified)
      5. Save & close
      6. Select Actions–>Edit (the instance, NOT the SRS MARC Bib)
      7. Add or change the instance Status (or Statistical code, Cataloged date, Nature of content, or any of the 3 checkboxes at the top of the Instance)
      8.  Save & close

      Alternate Steps to Reproduce - import a new instance:

      1. Log into Juniper Bugfest as User with permission to edit instances and to use data import
      2. Import the attached file Accordion.mrc using the Default - Create instance and SRS MARC Bib job profile
      3. Find the newly-created Instance in Inventory
      4. Select Actions–>Edit (the instance, NOT the SRS MARC Bib)
      5. Add or change the instance Status (or Statistical code, Cataloged date, Nature of content, or any of the 3 checkboxes at the top of the Instance)
      6.  Save & close

      Expected Results: 

      • The $3 (which is a valid subfield in MARC 590) does not map to anything in the instance data. Since none of the 590 subfields in this record are mapped to the Instance, this 590 field should not generate a corresponding instance note field.
      • When a user edits the Instance status field, the record can be saved

      Actual Results: 

      • A blank instance note element is generated.
      • When a user edits the Instance status field (Status (or Statistical code, Cataloged date, Nature of content, or any of the 3 checkboxes at the top of the Instance), the instance cannot be saved. Scroll down to the Notes accordion of the Instance. The instance fails to save because it requires information in the local note field, but the user cannot add any information in the local note field since it is controlled by the SRS MARC Bib.

      Additional Information: See attached video

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                Aivar Iusupov Aivar Iusupov
                Reporter:
                lauraw Laura Daniels
                Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases