Bib field - subfield 9 is reserved for populating authority UUID when user links MARC bib to authority record. Following outlines current requirements implemented to determine if additional requirements are needed to support
- Current cataloging workflows
- Authority control implementation for Orchid release and future enhancements
| Page/Action | Field type | Actual outcome | Expected outcome | Record used | Poppy requirement | Automated |
|---|---|---|---|---|---|---|
| Edit/Derive MARC bib | Non-linkable field | Cannot add or edit. Get an error message UIQM-341 - Getting issue details... STATUS | Requirements change - allow user to add/edit UIQM-426 - Getting issue details... STATUS | NAL_bib_with_subfield9_onanonlinkablefield.mrc | UIQM-426 - Getting issue details... STATUS | |
| Edit/Derive MARC bib | Linkable field (linked and unlinked) | Cannot add or edit. Get an error message UIQM-341 - Getting issue details... STATUS | NAL_bib_with_subfield9_onanonlinkablefield.mrc | UIQM-426 - Getting issue details... STATUS (for linked) | ||
| Data import > Create bib | Non-linkable field | Successfully creates record with subfield 9 | As expected | NAL_bib_with_subfield9_onanonlinkablefield.mrc | Same as Orchid | |
| Data import > Create bib | Linkable field | Invalid UUID Creates a record in SRS but not in mod-inventory The SRS record does not include the field with $9 Valid UUID MODSOURCE-592 - Getting issue details... STATUS | As expected = Return an error Not as expected | Address in Poppy
|
MODSOURCE-592 - Getting issue details... STATUS | ||
| Data import > Update bib (no data field protection) | Non-linkable field | Is not imported. | MODDATAIMP-795 - Getting issue details... STATUS Maintain the $9 | MODDATAIMP-795 - Getting issue details... STATUS | ||
| Edge case: Data import > Update bib (no data field protection) | Linkable field | Need to check | MODDICORE-330 - Getting issue details... STATUS MODDICORE-324 - Getting issue details... STATUS Import record but do not import/save $9 Field remains unlinked | |||
| Data import > Update bib (no data field protection) | Linked field - no change to subfield 9 | Remains linked No change to original $9 | As expected - No change to original $9 with the same $0 | No change from Orchid | ||
| Data import > Update bib (no data field protection) | Linked field - change to subfield 9 | No change to original $9 | As expected - No change to original $9 with the same $0 | No change from Orchid | ||
| Data import > Update bib (no data field protection) | Linked field Change to subfield $0 or subfield $0 does not exist $9 exist (does not matter if it is the linked UUID) | Need to check | Unlink MARC bib field when $0 has changed and remove the subfield 9 tied to the non-existent $0 MODDICORE-324 - Getting issue details... STATUS MODDICORE-331 - Getting issue details... STATUS | Update MARC bib field when $0 has changed (automated)
| ||
| Edge case: Multiples > Create | Non-linkable field | Successfully creates record with multiple subfield 9s | Create with multiple $9 | No change from Orchid expected outcome | ||
| Edge case: Multiples > Create | Linkable field | Need to check |
| |||
| Edge case: Multiples > Update | Non-linkable field | Is not imported. | Keep multiple subfields MODDATAIMP-795 - Getting issue details... STATUS | MODDATAIMP-795 - Getting issue details... STATUS | ||
| Edge case: Multiples > Update | Linked field | As expected - No change to original $9 with the same $0 | As expected - No change to original $9 with the same $0 | No change from Orchid expectation | ||
| Edge case: Multiples > Update | Linked field - change to $0 or it is not included | Need to check | Unlink MARC bib field when $0 has changed and remove the subfield 9 tied to the non-existent $0 Do we allow $9 (if not authority UUID to be saved? | |||
| Edge case: Multiples > Update | Linkable field | Need to check | A. Ignore and do not update with $9 B. Reject entire record update C. Successfully import | |||
| More Edge case: Data import > Update bib (w/ data field protection) | Non-linkable field | Address in Poppy | Behave like any other subfield | |||
| More Edge case: Data import > Update bib (w/ data field protection) | Linkable field | Address in Poppy | A. Behave like any other subfield B. Ignore the data field protection setting | |||
| More Edge case: Data import > Update bib (w/ data field protection) | Linked field same $0 | Address in Poppy | No change. Everything remains linked | |||
| More Edge case: Data import > Update bib (w/ data field protection) | Linked field no subfield $0 or changed subfield $0 | Address in Poppy | Unlink bib field AND remove the $9 (IOW ignore data field protection setting) | |||
| More Edge case: Data import > Update bib (w/ Field mapping profile > MARC bib updates) | Non-linkable field | Address in Poppy | Behaves like any other subfield | |||
| More Edge case: Data import > Update bib (w/ Field mapping profile > MARC bib updates) | Linkable field | Address in Poppy | A. Behave like any other subfield B. Ignore the data field protection setting | |||
| More Edge case: Data import > Update bib (w/ Field mapping profile > MARC bib updates) | Linked field same $0 | Address in Poppy | Keep bib field linked AND retain the $9 (IOW ignore data field protection setting) | |||
| More Edge case: Data import > Update bib (w/ Field mapping profile > MARC bib updates) | Linked field no subfield $0 or changed subfield $0 | Address in Poppy | Unlink bib field AND remove the $9 that was tied to the non-existent $0 (IOW ignore data field protection setting) OR consider logic that checks if $9 is not an authority UUID AND update $9 | |||
| More Edge case: Data import > Update bib (w/ Field mapping profile > MARC bib | Override data field protection) | Non-linkable field | Address in Poppy | Behaves like any other subfield | |||
| More Edge case: Data import > Update bib (w/ Field mapping profile > MARC bib | Override data field protection) | Linkable field | Address in Poppy | A. Behave like any other subfield B. Ignore the data field protection setting | |||
| More Edge case: Data import > Update bib (w/ Field mapping profile > MARC bib | Override data field protection) | Linked field same $0 | Address in Poppy | No change. Everything remains linked | |||
| More Edge case: Data import > Update bib (w/ Field mapping profile > MARC bib | Override data field protection) | Linked field no subfield $0 or changed subfield $0 | Address in Poppy | Unlink bib field AND remove the $9 (IOW ignore data field protection setting) | |||
| Most Edge case: Data import > Update bib (w/ Field mapping profile > MARC bib modifications | Add) | Non-linkable field | Address in Poppy | Behaves like any other subfield | |||
| Most Edge case: Data import > Update bib (w/ Field mapping profile > MARC bib modifications | Add) | Linkable field | Address in Poppy | A. Behave like any other subfield B. Ignore and do not add | |||
| Most Edge case: Data import > Update bib (w/ Field mapping profile > MARC bib modifications | Add) | Linked field same $0 | Address in Poppy | No change. Everything remains linked. Ignore the Add. | |||
| Most Edge case: Data import > Update bib (w/ Field mapping profile > MARC bib modifications | Add) | Linked field no subfield $0 or changed subfield $0 | Address in Poppy | Unlink MARC bib field when $0 has changed and remove the subfield 9 tied to the non-existent $0 Do we allow $9 (if not authority UUID to be saved? | |||
| Most Edge case: Data import > Update bib (w/ Field mapping profile > MARC bib modifications | Delete) | Non-linkable field | Address in Poppy | Behaves like any other subfield | |||
| Most Edge case: Data import > Update bib (w/ Field mapping profile > MARC bib modifications | Delete) | Linkable field | Address in Poppy | Behave like any other subfield Or just do not allow a library to ever populate $9 | |||
| Most Edge case: Data import > Update bib (w/ Field mapping profile > MARC bib modifications | Delete) | Linked field same $0 | Address in Poppy | No change. Everything remains linked. Ignore the Delete. | |||
| Most Edge case: Data import > Update bib (w/ Field mapping profile > MARC bib modifications | Delete) | Linked field no subfield $0 or changed subfield $0 | Address in Poppy | Unlink MARC bib field when $0 has changed and remove the subfield 9 tied to the non-existent $0 | |||
| Most Edge case: Data import > Update bib (w/ Field mapping profile > MARC bib modifications | Edit) | Non-linkable field | Address in Poppy | Behaves like any other subfield | |||
| Most Edge case: Data import > Update bib (w/ Field mapping profile > MARC bib modifications | Edit) | Linkable field | Address in Poppy | A. Behave like any other subfield B. Ignore and do not edit | |||
| Most Edge case: Data import > Update bib (w/ Field mapping profile > MARC bib modifications | Edit) | Linked field same $0 | Address in Poppy | No change. Everything remains linked. Ignore the Edit | |||
| Most Edge case: Data import > Update bib (w/ Field mapping profile > MARC bib modifications | Edit) | Linked field no subfield $0 or changed subfield $0 | Address in Poppy | Unlink MARC bib field when $0 has changed and remove the subfield 9 tied to the non-existent $0 Do we allow $9 (if not authority UUID to be saved? | |||
| Most Edge case: Data import > Update bib (w/ Field mapping profile > MARC bib modifications | Move) | Non-linkable field | Address in Poppy | Behaves like any other subfield | |||
| Most Edge case: Data import > Update bib (w/ Field mapping profile > MARC bib modifications | Move) | Linkable field | Address in Poppy | A. Behave like any other subfield B. Ignore and do not Move | |||
| Most Edge case: Data import > Update bib (w/ Field mapping profile > MARC bib modifications | Move) | Linked field same $0 | Address in Poppy | No change. Everything remains linked. Ignore the Move | |||
| Most Edge case: Data import > Update bib (w/ Field mapping profile > MARC bib modifications | Move) | Linked field no subfield $0 or changed subfield $0 | Address in Poppy | Unlink MARC bib field when $0 has changed and remove the subfield 9 tied to the non-existent $0 Do we allow $9 (if not authority UUID to be saved? |