$0 Requirements
- If a bib record contains a $0 then the unique identifier value can be used to conduct an authority identifier search when manually linking a bib field to an authority 1XX field
- Populating $0 and making $0 when the field is linked to an authority record for the following reasons:
- Store the URI to official authority record. Maybe desired by discovery systems. May serve a larger purpose in Linked Data and Entity Management requirements.
- Will be used in automated matching requirements (Orchid release).
- May be used in manual requirements (Nolana release) as it can be used to conduct an identifier search query on the Select an Authority modal.
- May be used to validate that the user is linking to the right authority record
- Still serves as a match point between the bib field and authority record.
- Generating the $0 URI – can be handled as an extension of MODINVSTOR-892. Please see confluence page for additional requirements.
- Will need to consider that sometimes authority record 010 $a populates unique identifiers with a space (example - n 00041513). We should support searching with and without space since we will not include a space in the $0 URI.
- If a base URI is not available then only populate $0 with the unique identifier.
- Unlinking the bib field from authority record makes the $0 editable. Does not remove $0 value from the bib field.
$0 handling table
# | Scenario | How to handle MARC bib subfield $0 | Comments |
---|---|---|---|
1 | Link existing bib field with $0 that is exact match to authority record 001 or 010 $a
| Make $0 read only | |
2 | Link existing bib field with $0 that is NOT exact match to authority record 001 or 010 $a
|
| |
3 | Link existing bib field without $0 and string text matches linked authority record
|
| |
4 | Link existing bib field without $0 and string text does not match linked authority record
|
| |
5 | Attempt to link existing bib field to a not acceptable Authority file source/type
|
$9 Requirements
- 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.
$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. |