Problems with default MARC-Instance mapping when some call number fields are repeated or have repeated subfields

Description

See the Instance (top) portion of this wiki page: https://folio-org.atlassian.net/wiki/display/FOLIJET/Classification+and+Call+number+handling+in+Data+Import

Overview: When an incoming MARC Bib record has multiples of the same field in some call number fields, the data in the Instance classification fields is not parsed correctly

Current workaround: Only one of each subfield must be in the call number fields of the incoming MARC Bib record

Steps to Reproduce:

  1. Log into FOLIO-snapshot as diku_admin

  2. Import the attached MARC file using the default Create Instance and MARC Bib job profile

  3. Once imported, click on the completed file, and then click on the "Created" hotlink in the Instance column

  4. Check the classification section of the first instance record (where multiple $a are in a single field)

Expected Results:

  • When call numbers are in multiple separate fields (see the second record in the attached file), everything works fine

  • See the column called Required handling when subfield in one field is repeated If $a is repeated, then the second $a (and any following $b) should be separated to a new classification field in the Instance

  • This already works properly for call number types UDC (080) and Gov Doc (086)

Actual Results

  • When call numbers are in multiple separate fields (see the second record in the attached file), everything is fine

  • When multiple subfield a's are in the same field, default mapping does not work properly for call number types LC (050 and 090), NLM (060) and Dewey (082)
    There are all the values from the multiple 050 in the one field

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

Ensure there is only 1 of each subfield in call number fields when creating/updating instances

Attachments

4
  • 10 Apr 2023, 10:08 AM
  • 20 Mar 2023, 08:21 AM
  • 20 Mar 2023, 08:21 AM
  • 20 Mar 2023, 08:21 AM

Confluence content

Checklist

hide

TestRail: Results

Activity

Show:

Ann-Marie Breaux April 17, 2023 at 4:39 PM
Edited

Hi This looks really good - thank you for fixing! Checked in Snapshot, closing this issue. Also added to the Poppy release notes https://folio-org.atlassian.net/wiki/display/REL/%5BDRAFT%5D+Poppy+%28R2+2023%29+Release+Notes and updated the default mapping wiki page. https://folio-org.atlassian.net/wiki/display/FOLIOtips/Default+MARC+Bibliographic-to-Inventory+Instance+Mappings.

Maksym Ishchenko April 10, 2023 at 10:08 AM

Hello  

Task verified on snapshot env. Subfields for the same field is now splitting into the different rows.

Moving ticket into "In review" column

Screencast:

cc:  

Ann-Marie Breaux March 21, 2023 at 3:32 PM

Discussed with today. https://folio-org.atlassian.net/browse/MODDICORE-322#icft=MODDICORE-322 is higher priority than this, and less risky, since this is a change to the default MARC-Instance map. Moving this to Poppy, but aiming to get https://folio-org.atlassian.net/browse/MODDICORE-322#icft=MODDICORE-322 done in Orchid BF. Will work on this ASAP during Poppy

Ann-Marie Breaux March 20, 2023 at 9:54 AM

Hi wiki page and Jira all cleaned up. Please let me know if questions.

Ann-Marie Breaux November 9, 2022 at 6:05 AM

Thanks, I talked it over with and we think it's best to move to Orchid. I've started a wiki page, and will finish it and get both bugs ready for Folijet to work on.

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Folijet

Fix versions

Release

Poppy (R2 2023)

RCA Group

Incomplete/missing requirements

Affected releases

Nolana (R3 2022)
Morning Glory (R2 2022)
Lotus (R1 2022)

Affected Institution

!!!ALL!!!

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created November 8, 2022 at 5:45 AM
Updated November 10, 2024 at 11:48 AM
Resolved April 17, 2023 at 4:43 PM
TestRail: Cases
TestRail: Runs

Flag notifications