...
- 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 a table tables of the affected classification fields and subfields and requirements 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
Related Jiras
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
MARC Classification and Holdings/Items
| Description | MARC Field and relevant subfields | Field 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 |
|---|---|---|---|---|---|---|---|
| LC | 050 $a (R) $b (NR) | 050$a " " 050$b | TBD | Use data from the first 050 only; ignore any subsequent | TBD | Use data from the first $a and $b only; ignore any subsequent | |
| NLM | 060 $a (R) $b (NR) | 060$a " " 060$b | TBD | Use data from the first 060 only; ignore any subsequent | TBD | Use data from the first $a and $b only; ignore any subsequent | |
| UDC | 080 $a (NR) $b (NR) | 080$a " " 080$b | TBD | Use data from the first 080 only; ignore any subsequent | n/a | n/a | Since neither subfield is repeatable within a field, no change is needed |
| Dewey | 082 $a (R) $b (NR) | 082$a " " 082$b | TBD | Use data from the first 082 only; ignore any subsequent | TBD | Use data from the first $a and $b only; ignore any subsequent | |
| Gov Doc | 086 $a (NR) $z (R) | 086$a | TBD | Use data from the first 086 only; ignore any subsequent | if multiple $z? | TBD | |
| Local LC | 090 $a (R) $b (R) | 090$a " " 090$b | TBD | Use data from the first 090 only; ignore any subsequent | TBD | Use data from the first $a and $b only; ignore any subsequent | |
| Local Dewey | 092 $a (R) $b (R) | 092$a " " 092$b | TBD | Use data from the first 092 only; ignore any subsequent | TBD | TBD | per Data Import Subgroup |
Holdings and Item Examples
Based on the required handling above
| Description | MARC data | Field mapping | Holdings/Item Call Number |
|---|---|---|---|
| LC | 2 050s | 050$a " " 050$b | |
| LC | 1 050 with 2 $a | 050$a " " 050$b | |
| NLM | 2 060s | 060$a " " 060$b | |
| NLM | 1 060 with 2 $a | 060$a " " 060$b | |
| UDC | 2 080s | 080$a " " 080$b | |
| Dewey | 2 082s | 082$a " " 082$b | |
| Dewey | 1 082 with 2 $a | 082$a " " 082$b | |
| Gov Doc | 2 086s | 086$a | |
| Gov Doc | 1 086 with 2 $z | 086$a | |
| Local LC | 2 090s | 090$a " " 090$b | |
| Local LC | 1 090 with 2 $a | 090$a " " 090$b | |
| Local Dewey | 2 092 | 092$a " " 092$b | |
| Local Dewey | 1 092 with 2 $a | 092$a " " 092$b |