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 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
Related Jiras
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
MARC Classification fields and Instances
Red = Change neededthat was made in Poppy
| Description | MARC 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 | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| LC | 050 $a (R) $b (NR) | Separate classification fields | Separate classification fields | One classification field | Separate classification fields, with 1st $a and its $b if present in first Instance field, and 2nd $a in second Instance field | ||||||||
| NLM | 060 $a (R) $b (NR) | Separate classification fields | Separate classification fields | One classification field | Separate 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 | ||||||||
| UDC | 080 $a (NR) $b (NR) | Separate classification fields | Separate classification fields | n/a | n/a | Since $a is not repeatable within a field, no change is needed | |||||||
| Dewey | 082 $a (R) $b (NR) | Separate classification fields. If there is a slash in $a, remove it and close up the space | Separate classification fields. If there is a slash in $a, remove it and close up the space | One classification field | Separate 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 Doc | 086 $a (NR) $z (R) | Separate classification fields. If $a and $z both present in the same 086 field, split them into separate Instance fields | Separate classification fields. If $a and $z are both present in the same 086 field, split them into separate Instance fields | Separate classification 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 | No change is needed | |||||||
| Local LC | 090 $a (R) $b (R) | Separate classification fields | Separate classification fields | One classification field | Separate 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 | Local Dewey | 092 $a (R) $b (R) | n/a | n/a | n/an/a | Not included in the default MARC-to-Instance map |
Instance Examples
Based on the required handling above
...
MARC Classification and Holdings/Items
Red = Change that was made in Orchid
| Description | MARC Field and relevant subfields | Field mapping | Current Pre-Orchid handling when field is repeated | Required Orchid handling | Current Pre-Orchid handling | Required Orchid handling | Notes | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| LC | 050 $a (R) $b (NR) | 050$a " " 050$b | TBDSome of the data from the second field is included | Use data from the first 050 only; ignore any subsequent | TBD050 field | All data from the field is included | Use data from the first $a and $b only; ignore any subsequent | |||||||||
| NLM | 060 $a (R) $b (NR) | 060$a " " 060$b | TBDData from both fields included | Use data from the first 060 only; ignore any subsequent | TBD060 field | All data from the field is included | Use data from the first $a and $b only; ignore any subsequent | |||||||||
| UDC | 080 $a (NR) $b (NR) | 080$a " " 080$b | TBDData from both fields included | Use data from the first 080 only; ignore any subsequent 080 field | 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 | TBDData from both fields included and mixed together | Use data from the first 082 only; ignore any subsequent | TBD082 field | All data from the field is included | Use data from the first $a and $b only; ignore any subsequent | |||||||||
| Gov Doc | 086 $a (NR) $z (R) | 086$a | TBDData from both fields included | Use data from the first 086 only; ignore any subsequent | if multiple $z? | TBD086 field | As long as only $a is mapped, all is fine | No change needed | ||||||||
| Local LC | 090 $a (R) $b (R) | 090$a " " 090$b | TBDSome of the data from the second field is included | Use data from the first 090 050 only; ignore any subsequent | TBD050 field | All data from the field is included | 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 | Sample MARC | Field mapping | Holdings/Item Call Number |
|---|---|---|---|---|
| LC | 2 050s | 050 14 $aB3199.A33 $bP7613 2000a | 050$a " " 050$b | B3199.A33 P7613 2000a |
| LC | 1 050 with 2 $a | 050 04 $aZ5853.M38 $bG37 1993 $aTA418.9.C6 | 050$a " " 050$b | Z5853.M38 G37 1993 |
| NLM | 2 060s | 060 10 $aW1 $bME9616J v.69 1997 | 060$a " " 060$b | W1 ME9616J v.69 1997 |
| NLM | 1 060 with 2 $a | 060 \0 $aW1 NE372F v.12 $aQU 95 S839 | 060$a " " 060$b | W1 NE372F v.12 |
| UDC | 2 080s | 080 \\$a001.81 $bB67 | 080$a " " 080$b | 001.81 B67 |
| Dewey | 2 082s | 082 04 $a300.723 $bHEA 082 04 $a338.7/6292/092 $bHEA $221 | 082$a " " 082$b | 300.723 HEA |
| Dewey | 1 082 with 2 $a | 082 04 $a300.723 $bHEA $a338.7/6292/092 | 082$a " " 082$b | 300.723 HEA |
| Gov Doc | 2 086s | 086 0\ $aD 210.6:M 56 086 0\ $aY 3.AT 7:6 M 56/ | 086$a | D 210.6:M 56 |
| Gov Doc | 1 086 with 2 $z | 086 0\ $aA 1.1: $zA 1.1/3:984 $zA 1.1/4:985 | 086$a | A 1.1 |
| Local LC | 2 090s | 090 14 $aB3199.A33 $bP7613 2000a | 090$a " " 090$b | B3199.A33 P7613 2000a |
| Local LC | 1 090 with 2 $a | 090 14 $aZ5853.M38 $bG37 1993 $aTA418.9.C6 | 090$a " " 090$b |
| Z5853.M38 G37 1993 |