Uploaded image for project: 'mod-source-record-manager'
  1. mod-source-record-manager
  2. MODSOURMAN-675

Data Import handles repeated 020 $a:s in an unexpected manner when creating Instance Identifiers

    XMLWordPrintable

Details

    • 5
    • Folijet Support
    • Lotus R1 2022
    • !!!ALL!!!
    • Data related (ex. Can be detected with large dataset only)

    Description

      Overview:
      Steps to Reproduce:

      1. Log into Bugfest-Kiwi
      2. Import the attached MARC record using the profile "Create instance and holdings AMB"
        The record has the following 020:

      Expected Results:
      After bugfix

      • If the number is in $a, it is assigned Identifier type ISBN, along with any qualifier information that directly follows it in the same subfield or in $q
      • If the number is in $z, it is assigned Identifier type Invalid ISBN, along with any qualifier information that directly follows it in the same subfield or in $q
      • With this data in the MARC record:
        • 020 $a9780471622673$q(acid-free paper)$a0471725331$q(electronic bk.)
        • 020 $z9780471725336$q(electronic bk.)$z0471725323$q(electronic bk.)
        • 020 $a9780471725329 (electronic bk.)$z0471622672$q(acid-free paper)
      • The following should be created in the Instance
        • ISBN 9780471622673 (acid-free paper)
        • ISBN 0471725331 (electronic bk.)
        • Invalid ISBN 9780471725336 (electronic bk.)
        • Invalid ISBN 0471725323 (electronic bk.)
        • ISBN 9780471725329 (electronic bk.)
        • Invalid ISBN 0471622672 (acid-free paper)

      Based on the Default mapping rules, one of the following should have happened:

      • The record fails since 020$a cannot be repeated according to MARC21
      • The repeated (second) 020$a is discarded
      • Data migration follows the default mapping rules in the tenant, and concatenates the identifiers like so: "0870990004 (v. 1) 0870990020 (v. 2)"
        (but note, that neither is a desired behaviour)

      Actual Results:

      Additional Information:
      There is likely A VERY SIMPLE solution to this. Just like with the other identifiers in the default mapping rules, add the entityPerRepeatedSubfield flag to the entity mappings for 020s. Both 020 $a and $020 $z.

      The EBSCO ICs just discovered this behavior in their tools. The current set of Default rules, forces us to edit all rules to avoid the above-described behavior.

      URL:
      These are links to the results of the import in Bugfest-Kiwi. Similar behaviour is in Bugfest-Juniper as well.
      https://bugfest-kiwi.folio.ebsco.com/data-import/log/8c150a5a-e5be-4f24-bbb2-d2b00a548f81/f215d190-69f2-4e42-a50d-5c17bad29fb2
      https://bugfest-kiwi.folio.ebsco.com/inventory/view/f215d190-69f2-4e42-a50d-5c17bad29fb2?qindex=id&query=f215d190-69f2-4e42-a50d-5c17bad29fb2&sort=title

      The Kiwi Mapping rules for 022 has the flag set:

      while it lacks it for 020 $a:

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                Miami20 Khamidulla Abdulkhakimov
                ttolstoy Theodor Tolstoy
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases