Orchid > Subfield 0 handling
- Khalilah Gambrell
- Current cataloging workflows
- Authority control implementation for Orchid release and future enhancements
| Page/Action | Field type | Actual outcome | Expected outcome | Record used | Poppy release | Automated |
|---|---|---|---|---|---|---|
| Edit/Derive MARC bib | Non-linkable field | Allow to add/edit Can add/edit multiple in a single field | Same as actual outcome | N/A | ||
| Edit/Derive MARC bib | Linkable field (linked/unlinked) | unlinked: Allow to add/edit linked: Allow to add For both: Can add multiple in a single field For unlinked: Can edit multiple in a single field | Unlinked: Expected Linked: Should display an error message when user adds another $0 OR it is setup as uncontrolled fields | |||
| Data import > Create bib | Non-linkable field | Creates with $0s including multiple $0 on one bib field | Same as actual | |||
| Data import > Create bib | Linkable field | Creates with $0s including multiple $0 on one bib field | Same as actual | quick-export-5_20.mrc | ||
| Data import > Update bib (no data field protection) | Non-linkable field | Allow to update and support multiples | Same as actual | |||
| Data import > Update bib (no data field protection) | Linked field (no change to $0) | Keeps the link OR appears to do so on the UI AND allows for the addition of multiple $0s BUT UI looks odd | Keep the link AND Need to not add the additional $0 at all OR have it as editable | quick-export-5_22.mrc | ||
| Data import > Update bib (no data field protection) | Linked field (change to $0) | Unlink bib field and accept bib field updates | Same as actual | |||
| Data import > Update bib (no data field protection) | Linkable field | Allow update and for multiples | Same as actual | quick-export-5_22.mrc | ||
| Data import > Update bib (w/ data field protection) | Non-linkable field | No change to current behavior Known issue with repeatable fields | ||||
| Data import > Update bib (w/ data field protection) | Linkable field | No change to current behavior Known issue with repeatable fields | ||||
| Data import > Update bib (w/ data field protection - selected fields set to protect linkable field + $9) | Linked field | Using subfield 9/0 preserves links but UI does not look great Repeatable field = duplicates OR a change in one subfield value results in duplicates | Correct the UI but the duplication might be okay when thinking about single record import MODDICORE-327 - Getting issue details... STATUS | |||
| Data import > Update bib (w/ Field mapping profile > MARC bib updates) | Non-linkable field | |||||
| Data import > Update bib (w/ Field mapping profile > MARC bib updates) | Linkable field | |||||
| Data import > Update bib (w/ Field mapping profile > MARC bib updates) | Linked field | |||||
| Data import > Update bib (w/ Field mapping profile > MARC bib | Override data field protection) | Non-linkable field | |||||
| Data import > Update bib (w/ Field mapping profile > MARC bib | Override data field protection) | Linkable field | |||||
| Most Edge case: Data import > Update bib (w/ Field mapping profile > MARC bib modifications | Add) | Non-linkable field | |||||
| Most Edge case: Data import > Update bib (w/ Field mapping profile > MARC bib modifications | Add) | Linkable field | |||||
| Most Edge case: Data import > Update bib (w/ Field mapping profile > MARC bib modifications | Delete) | Non-linkable field | |||||
| Most Edge case: Data import > Update bib (w/ Field mapping profile > MARC bib modifications | Delete) | Linkable field | |||||
| Most Edge case: Data import > Update bib (w/ Field mapping profile > MARC bib modifications | Delete) | Linked field | |||||
| Most Edge case: Data import > Update bib (w/ Field mapping profile > MARC bib modifications | Edit) | Non-linkable field | |||||
| Most Edge case: Data import > Update bib (w/ Field mapping profile > MARC bib modifications | Edit) | Linkable field | |||||
| Most Edge case: Data import > Update bib (w/ Field mapping profile > MARC bib modifications | Move) | Non-linkable field | |||||
| Most Edge case: Data import > Update bib (w/ Field mapping profile > MARC bib modifications | Move) | Linkable field |