...
- If a user links a bib field to an authority record then the linked bib field has a $9 stored populated with Authority UUID
- Storing $9 serves as a unique linking identifier between the linked bib field and authority record and ensures that the right bib field is updated
- If the bib field is no longer linked to the authority record then $9 is removed from the now unlinked bib field
- Might be used for searching all bib records linked to an authority record
- Might be used for creating authority control reports
- OPEN QUESTION - Should $9 display on View Source and quickMARC UI?
- OPEN QUESTION - How does $9 support DI updates? Will discuss on this confluence page.
- If we decide to show and it is needed for DI support then we need to make updates to Data export too.
$9 handling table
| # | Scenario | How to handle MARC bib subfield $9 | Comments |
|---|---|---|---|
| 1 | Manual link a bib field to an authority record (Nolana release) | Add $9 to that bib field populated with Authority UUID once Save is clicked TBD if $9 will display on View source and Edit quickMARC bib | |
| 2 | Manual unlink a bib field from an authority record (Nolana release) | Field is unlinked. All fields/subfields are editable. $9 is removed from previously linked bib field once Save is clicked TBD if $9 will display on View source and Edit quickMARC bib | |
| 3 | Automated link a bib field to an authority record (Orchid release) | Add $9 to that bib field populated with Authority UUID when automated matching service is run. | |
| 4 | Automated unlink a bib field from an authority record (Orchid/Poppy release) | Remove $9 from that bib field when automated matching service is run. |
...