Skip to end of banner
Go to start of banner

Classification and Call number handling in Data Import

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

DRAFT       DRAFT       DRAFT       DRAFT

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 fields.
  • See below for a table of the affected classification fields and subfields and requirements 

Related Jiras

MODSOURMAN-882 - Getting issue details... STATUS

MODSOURMAN-900 - Getting issue details... STATUS

MARC Classification fields and Instances

DescriptionMARC Field and relevant subfields

Current handling

when field is repeated

Required handling 

when field is repeated

Current 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 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 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 fields??Separate classification fields. If $a and multiple $z's are both present in the same 086 field, split them all into separate Instance fields
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 in second Instance field
Local Dewey092 $a (R) $b (R)n/an/an/an/aNot included in the default MARC-to-Instance map

Instance Examples

Based on the required handling above

DescriptionMARC dataInstance Classification field(s) 
LC2 050s
LC1 050 with 2 $a
NLM

2 060s


NLM1 060 with 2 $a
UDC2 080s
Dewey2 082s
Dewey1 082 with 2 $a
Gov Doc2 086s
Gov Doc1 086 with 2 $z
Local LC2 090s
Local LC1 090 with 2 $a
Local Dewey2 092
Local Dewey1 092 with 2 $a

MARC Classification and Holdings/Items

DescriptionMARC Field and relevant subfieldsField mapping

Current handling when field is repeated

Required handling 

when field is repeated

Current handling

when subfield in one field is repeated

Required handling

when subfield in one field is repeated

Notes
LC050 $a (R)  $b (NR)050$a " " 050$bTBDUse data from the first 050 only; ignore any subsequentTBDUse data from the first $a and $b only; ignore any subsequent
NLM060 $a (R)  $b (NR)060$a " " 060$bTBDUse data from the first 060 only; ignore any subsequentTBDUse data from the first $a and $b only; ignore any subsequent
UDC080 $a (NR) $b (NR)080$a " " 080$bTBDUse data from the first 080 only; ignore any subsequentn/an/aSince neither subfield is repeatable within a field, no change is needed
Dewey082 $a (R)  $b (NR)082$a " " 082$bTBDUse data from the first 082 only; ignore any subsequentTBDUse data from the first $a and $b only; ignore any subsequent
Gov Doc086 $a (NR) $z (R)086$aTBDUse data from the first 086 only; ignore any subsequentif multiple $z?TBD
Local LC090 $a (R) $b (R)090$a " " 090$bTBDUse data from the first 090 only; ignore any subsequentTBDUse data from the first $a and $b only; ignore any subsequent
Local Dewey092 $a (R) $b (R)092$a " " 092$bTBDUse data from the first 092 only; ignore any subsequentTBDTBDper Data Import Subgroup

Holdings and Item Examples

Based on the required handling above

DescriptionMARC dataField mappingHoldings/Item Call Number
LC2 050s050$a " " 050$b
LC1 050 with 2 $a050$a " " 050$b
NLM

2 060s

060$a " " 060$b
NLM1 060 with 2 $a060$a " " 060$b
UDC2 080s080$a " " 080$b
Dewey2 082s082$a " " 082$b
Dewey1 082 with 2 $a082$a " " 082$b
Gov Doc2 086s086$a
Gov Doc1 086 with 2 $z086$a
Local LC2 090s090$a " " 090$b
Local LC1 090 with 2 $a090$a " " 090$b
Local Dewey2 092092$a " " 092$b
Local Dewey1 092 with 2 $a092$a " " 092$b


  • No labels