Linking Bib field to Authority 1XX | Handling $0 and $9

Owned by Khalilah Gambrell
Last updated: Feb 19, 2023
4 min read

Handling $0 and $9 - Why we need to implement requirements for supporting both

  • $9 serves as the linking identifier between bib field row and an authority record after the user links the bib field to the authority record. 
  • $0 serves as a way to match/verify match between a bib field to an authority record before the user links the bib field to the authority record. It also supports automated matching development planned for Poppy. And it will support future requirements related to Linked Data and Entity Management. 

$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 (Poppy release).
    • Used in manual requirements 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 

#ScenarioHow to handle MARC bib subfield $0Comments
1

Link existing bib field with $0 that is exact match to authority record 001 or 010 $a

  1. User hits Edit quickMARC bib 
  2. User clicks Link to authority heading option 
    1. This existing bib field has a $0
  3. User finds an applicable MARC authority record to link which is an exact match to the MARC bib field $0 
  4. User hits Link 
  5. Returns to Bib record 
  6. MARC bib field is updated with the applicable subfields on the MARC authority record

Make $0 read only


2

Link existing bib field with $0 that is NOT exact match to authority record 001 or 010 $a

  1. User hits Edit quickMARC bib 
  2. User click Link to authority heading option 
    1. This existing bib field has a $0
  3. User finds an applicable MARC authority record to link which is not an exact match to the MARC bib field $0 
  4. Show a warning message when user attempts to link. Allow user to proceed with linking. 
  5. User hits Link 
  6. Returns to Bib record 
  7. MARC bib field is updated with the applicable subfields on the MARC authority record
  •  Override $0 with Authority record 001 or 010 $a. Generate a URI that is formatted as <<base URL>>/linkedauthorityrecord 001/010 $a otherwise populate with linkedauthorityrecord 001/010 $a
  • Make $0 read only on UI

3

Link existing bib field without $0 and string text matches linked authority record 

  1. User hits Edit quickMARC bib 
  2. User click Link to authority heading option 
    1. This existing bib field has no $0
  3. User finds an applicable MARC authority record to link that is an exact match to the MARC bib string text
  4. User hits Link 
  5. Returns to Bib record 
  6. MARC bib field is updated with the applicable subfields on the MARC authority record
  • If available, generate a URI that is formatted as <<base URL>>/linkedauthorityrecord 001/010 $a otherwise populate with linkedauthorityrecord 001/010 $a
  • Make $0 read only on UI

4

Link existing bib field without $0 and string text does not match linked authority record 

  1. User hits Edit quickMARC bib 
  2. User click Link to authority heading option
    1. This existing bib field has no $0
  3. User finds an applicable MARC authority record to link that is not an exact match to the MARC bib string text
  4. User hits Link 
  5. Returns to Bib record 
  6. MARC bib field is updated with the applicable subfields on the MARC authority record
  • If available, generate a URI that is formatted as <<base URL>>/linkedauthorityrecord 001/010 $a otherwise populate with linkedauthorityrecord 001/010 $a
  • Make $0 read only on UI

5

Attempt to link existing bib field to a not acceptable Authority file source/type

  1. User hits Edit quickMARC bib for 100. 100 can only accept authority type = Name 
  2. User click Link to authority heading option
  3. User attempts to link to an authority type = Subject
  4.  Show an error message. Prevent user from linking. 


$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 
  • Used for searching all bib records linked to an authority record 
  • Might be used for creating authority control reports

$9 handling table 

#ScenarioHow to handle MARC bib subfield $9Comments
1Manual link a bib field to an authority record

Add $9 to that bib field populated with Authority UUID once Save is clicked 

$9 does not display on 

  • Edit MARC bib
  • Derive new MARC bib

$9 displays

  • View Source
  • Export MARC bib

2Manual unlink a bib field from an authority record 

Field is unlinked. All fields/subfields are editable. $9 is removed from previously linked bib field once Save is clicked


3Cannot manually enter $9 (Orchid release)Show an error message