Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Remove Red when Jiras are completed

Statement of problem

  • In 2022, the Inventory and Data Import users discovered that MARC call number fields (such as 050, 060, etc.) with repeated fields or subfields are not handled properly when Instances, Holdings, and Items are created or updated. 
  • The default MARC Bib-to-Inventory Instance mapping rules handle repeated classification fields fine, since classification is a repeatable field in the Inventory Instance. However, the current rules do not handle repeated subfields within a particular classification field properly. This is often the case with classification for bibliographies or juvenile materials.
  • The existing field mappings for call numbers in holdings and item records do not work properly if the mapped call number field is repeated in the MARC Bibliographic record. Since the call number field is not repeatable in the Inventory holdings or item record, the result is a call number that is a combination of the multiple MARC fields.
  • See below for tables of the affected classification fields and subfields and requirements. 
    • Correcting the handling in Instances requires changes to the default MARC Bib-to-Inventory Instance map
    • Correcting the handling in Holdings and Items requires changes to the handling of mapped data in the call number fields of the Holdings and Item field mapping profiles

...

MARC Classification fields and Instances

Red = Change neededthat was made in Poppy

DescriptionMARC Field and relevant subfields

Current Pre-Poppy handling

when field is repeated

Required handling 

when field is repeated

Current Pre-Poppy handling

when subfield in one field is repeated

Required handling

when subfield in one field is repeated

Notes
LC050 $a (R)  $b (NR)Separate classification fieldsSeparate classification fieldsOne classification fieldSeparate classification fields, with 1st $a and its $b if present in first Instance field, and 2nd $a in second Instance field
NLM060 $a (R)  $b (NR)Separate classification fieldsSeparate classification fieldsOne classification fieldSeparate classification fields, with 1st $a and its $b if present in first Instance field, and 2nd $a (and its $b, if it has one) in second Instance field
UDC080 $a (NR) $b (NR)Separate classification fieldsSeparate classification fieldsn/an/aSince $a is not repeatable within a field, no change is needed
Dewey082 $a (R)  $b (NR)Separate classification fields. If there is a slash in $a, remove it and close up the spaceSeparate classification fields. If there is a slash in $a, remove it and close up the spaceOne classification fieldSeparate classification fields, with 1st $a and its $b if present in first Instance field, and 2nd $a (and its $b, if it has one) in second Instance field
Gov Doc086 $a (NR) $z (R)Separate classification fields. If $a and $z both present in the same 086 field, split them into separate Instance fieldsSeparate classification fields. If $a and $z are both present in the same 086 field, split them into separate Instance fieldsSeparate classification fieldsSeparate classification fields. If $a and multiple $z's are both present in the same 086 field, split them all into separate Instance fieldsNo change is needed
Local LC090 $a (R) $b (R)Separate classification fieldsSeparate classification fieldsOne classification fieldSeparate classification fields, with 1st $a and its $b if present in first Instance field, and 2nd $a (and its $b, if it has one) in second Instance field

...

DescriptionMARC Field and relevant subfieldsField mapping

Current Pre-Poppy handling when field is repeated

Required Poppy handling 
when field is repeated

Current Pre=Poppy handling
when subfield in one field is repeated

Required Poppy handling
when subfield in one field is repeated

Notes
LC050 $a (R)  $b (NR)050$a " " 050$bSome of the data from the second field is includedUse data from the first 050 only; ignore any subsequent 050 fieldAll data from the field is includedUse data from the first $a and $b only; ignore any subsequent
NLM060 $a (R)  $b (NR)060$a " " 060$bData from both fields  includedUse data from the first 060 only; ignore any subsequent 060 fieldAll data from the field is includedUse data from the first $a and $b only; ignore any subsequent
UDC080 $a (NR) $b (NR)080$a " " 080$bData from both fields  includedUse data from the first 080 only; ignore any subsequent 080 fieldn/an/aSince neither subfield is repeatable within a field, no change is needed
Dewey082 $a (R)  $b (NR)082$a " " 082$bData from both fields included and mixed togetherUse data from the first 082 only; ignore any subsequent 082 fieldAll data from the field is includedUse data from the first $a and $b only; ignore any subsequent
Gov Doc086 $a (NR) $z (R)086$aData from both fields  includedUse data from the first 086 only; ignore any subsequent 086 fieldAs long as only $a is mapped, all is fineNo change needed
Local LC090 $a (R) $b (R)090$a " " 090$bSome of the data from the second field is includedUse data from the first 050 only; ignore any subsequent 050 fieldAll data from the field is includedUse data from the first $a and $b only; ignore any subsequent

...