/
Requirements | Linking bib field to authority record | Create/Edit/Delete authority record interactions (old)

Requirements | Linking bib field to authority record | Create/Edit/Delete authority record interactions (old)

Owned by Khalilah Gambrell
Last updated: Dec 28, 2022

NOTE: All linked bib fields will have a $0 populated and will be read-only on the UI. The $0 will populate a URI that includes the linked Authority record 010 $a or 001 as a unique identifier. A MARC bib field's $0 will serve as a match point. 

ARCH-23 - Getting issue details... STATUS

Overall requirements for Nolana/Orchid (manual) 

  • Change Authority 1XX value will change all linked bib fields. 
  • Change 010 $a value will change all linked bib fields $0 values 
  • Updating linked bib fields WILL NOT be a part of the update Authority records DI job
  • Will conduct performance/scalability tests to
    • ensure no degradation of DI 
    • determine expected turnaround timeframe based on # of bib fields updated 
  • Will generate a report/log to inform users
    • Status for processing linked bib field updates
    • Any errors/failures
  • Will allow for authority record deletion via UI. Formerly linked bib fields will retain all values... just uncontrolled. 
  • Will honor data field protection settings 


Scenarios

#Scenario

Manual Outcome Options (Nolana/Orchid development) ARCH-23 - Getting issue details... STATUS

Auto-link Outcome Options (Orchid/Poppy development)Comments
1Create new MARC authority record via data import 

No change. Nothing happens as far as linking.


JAC- Would like to be able to auto-link records based on the 010 matching a $0, but would prefer this to happen outside of the import process due to other potential processes happening at the same time. Would prefer that linking isn't tied to data import, including separate logs.
JC- logs should be available at the completion of this process. If there are other circumstances that create unlinked records but have a $0 consider making this some kind of regular scheduled system process rather than related to DI.

JE: I feel that the linking is slightly different than the import. The 2 are related in that the import will launch the linking. I'd like to see a place to govern when, where, and what has been linked with errors and the ability to schedule linking jobs.


2

Edit MARC authority (1XX field) records via data import 

  1. User imports a MARC authority record (personal name - 100 $a Twain, Mark, $d 1835-1910) 
  2. This record is linked to 1000 bib records
  3. Import includes an update to the record's 100 $a value from Twain, Mark to Twain, Marc E. 
  1. Update MARC authority 100 $a - No change to current data import process
  2. Begin process to update 1000 bib records linked to authority record


Phase 2 requirement options

A. Job logs list similar to data import (UX) - https://bugfest-mg.int.aws.folio.org/data-import (username: folio / password: folio) 

 

 



I think this will depend on institutions and the number of authority records and how authority records are managed (loaded by vendor, other). I'd like to see options to set this and change it when necessary. I'd like to see something else perhaps even a separate utility for managing authorities that lists jobs, has scheduling, perhaps even reports on errors or even the ability to link to external authority services.
3

Edit MARC authority (1XX field) records via quickMARC

  1. User accesses MARC authority record (personal name - 100 $a Twain, Mark, $d 1835-1910) 
  2. This record is linked to 1000 bib records
  3. User edits the record's 1XX value from from Twain, Mark to Twain, Marc E. 
  4. User hits Save 
  5. Display a message that informs user of the total number of linked bib records that will be updated
  6. If user proceeds with update then bib records will be updated in a separate process. 
  7. The Outcome options columns has several questions.  
  1. Update MARC authority 100 $a 
  2. Begin process to update 1000 bib records linked to authority record


Phase 2 requirement options

A. Job logs list similar to data import (UX) - https://bugfest-mg.int.aws.folio.org/data-import (username: folio / password: folio) 



Question 1

JC- Hard to determine without knowing the update mechanism. If this is a shadow DI job, performance and other concerns much higher, would want to do large sets overnight even more.

JC - DI log style

JE: The more I think about this, I'd like to see a utility or something where you can manage linking, perhaps integrations with external services, scheduling.

4

Edit MARC authority (NOT 010 $a or 1XX field) field via quickMARC 

  1. User accesses MARC authority record (personal name - 100 $a Twain, Mark, $d 1835-1910) 
  2. This record is linked to 1000 bib records
  3. User edits the record's 4XX value  
  4. User hits Save 

No impact to any bib records linked to the authority record 

 

 Same as manual


5

Edit MARC authority (NOT 010 $a or 1XX field) records via data import 

  1. User imports a MARC authority record (personal name - 100 $a Twain, Mark, $d 1835-1910) 
  2. This record is linked to 1000 bib records
  3. Import includes an update to record's 4XX value  

No impact to any bib records linked to the authority record 

 

 Same as manual


6

Edit MARC authority (010 $a field) record via data import (rare use case) 

  1. User imports a MARC authority record (personal name - 100 $a Twain, Mark, $d 1835-1910) 
  2. This record is linked to 1000 bib records
  3. Import includes an update to the record's 010 $a value