Requirement | Linking bib field to authority record | Create/Derive/Edit bib record interactions (updated)

Requirement | Linking bib field to authority record | Create/Derive/Edit bib record interactions (updated)

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

Overall requirements for Nolana/Orchid for Manual linking 

Incoming $0 / $9

Updated record via Data import >  Expected outcome until auto-link/match is in place

Same as existing $0 or $9 value

  • Keep link

  • Update uncontrolled values 

  • Controlled values always same as linked authority field value

No $0 and $9

  • Update values 

  • Unlink field IF a Link exist 

Different $0 or $9 

  • Update values 

  • Unlink field IF a Link exist to another authority record

Data field protection interaction: No change to logic. If linked bib field is set to be protected then we will honor. 

Scenarios

#Scenario

Manual Outcome Option (Nolana/Orchid development) -  ARCH-22 - Getting issue details... STATUS

Auto-link Outcome selection (Orchid/Poppy development) Comments
1Create new MARC bib record via data import app

No change. Nothing happens as far as linking.


JAC- Would want to run some sort of authority matching process with $0, but would prefer authority control process is not linked to data import. 

JE: I'd like to see sort of utility where institutions can set what they want to do and when.


2Create new MARC bib record via single record import functionality 

No change. Nothing happens as far as linking.

JAC- Same as above. Would want linking process to happen separately from record creation. 


3Derive a new MARC bib record via quickMARC from a bib record with linked authorities

Allow a user to decide to keep links or remove them ONCE user hits the Derive a new MARC bib record action




4

Overlay a MARC bib record with fields linked to authority records. (user case is occasional)

  1. A MARC bib record has several bib field(s) linked to authority records
  2. Then user overlays the MARC bib record via single record import 

If the incoming bib field contains a $0 that matches the existing $0 then keep linking









5

Update bib record via data import with NO change to the linked bib field

  1. User updates a linked bib record via data import.
  2. The import file contains a bib record with a  
    1. No change to authority linked MARC 100 bib field
      1. Indicators
      2. Controlled  values
      3. Uncontrolled values
    2. Assume that the matched $0 or $ 9is included in the import file

No change thus no impact to linking. (also applies to repeated fields)


Same as manual


6

Update bib record via data import with A Change to linked bib field value(s) NOT controlled by authority

  1. User updates a linked bib record via data import.
  2. The import file contains a bib record with a  
    1. A linked 100 field has a change to uncontrolled $e. For example update $e from author to $e author $e narrator
    2. No change to controlled values 
    3. No change to indicators  
    4. Assume that the matched $0 0r $9 is included in the import file
  • No impact to linking. (also applies to repeated fields) 
  • Only the uncontrolled $e will be updated so it will now be $e author $narrator


Same as manual


7

Update bib record via data import with a Change to a linked bib field value Controlled by authority (happens occasionally)

  1. User updates a linked bib record via data import.
  2. The import file contains a bib record with a  
      1. change to Linked MARC bib 100 field $a  Angeloo, Maya BUT is linked to authority record 100 $a Angelou, Maya 
    1. Assume that the matched $0 or $9 is included in the import file

If $0 is the same then no update. Remains 100 $a Angelou, Maya. 



 


JE: I think having some sort of utility where you can look at the report and then take action on it -auto correct, manually correct, or something else.



8

Update bib record via data import AND Linked bib field has a different $0 or $9 value  (occasional use case) 

  1. User updates a linked bib record via data import.
  2. The import file contains a bib record with a  
    1. Linked MARC 100 bib field includes a $0 or $9 but the value stored  (ex. no234556) is not the same as what is in the import (ex. no234349). No other change made this field
Update bib field and unlink from authority record (Unless field protected) 

9

Update bib record via data import AND Linked bib field has a different $0/$9 or no $0/$9 and change to a controlled value. 

  1. User updates a linked bib record via data import.
  2. The import file contains a bib record with a  
    1. Linked MARC bib 100 field includes a $0/$9 but the value stored  (ex. no234556) is not the same as what is in the import (ex. no234349) OR no $0/$9 at all 
    2. And subfield $d has changed from 1900 - 1998 to 1900 - 2000 
  • Update bib field including updates to $0 and $d
  • and unlink from authority record (Unless field protected) 

 

JE: I feel that institutions should be able to schedule this and perhaps even the types of updates that take place.

10

Update bib record via data import AND Linked bib field has a different $0 or no $0  and change to a uncontrolled value. (occasional use case) 

  1. User updates a linked bib record via data import.
  2. The import file contains a bib record with a  
    1. Linked MARC bib 100 field includes a $0 but the value stored  (ex. no234556) is not the same as what is in the import (ex. no234349) OR no $0 at all 
    2. And subfield $e has changed from  $e author to $e author $e narrator
  • Proceed with update of $0 and $e. 
  • Remove linking.

 


JAC-We want to update the data we are bringing in; we don't always want authorities app to be doing field protection for us, and when we do we want to turn it off and on.

11

Delete a linked/controlled MARC bib field via quickMARC

  1. Existing bib record has a MARC =600  07$aBlack Panther$c(Fictitious character)$2fast$0(OCoLC)fst02000849
  2. Cataloger deletes the field 
  3. Saves the bib record
  • MARC 600 will no longer exist for this bib record
  • Unlink bib field from authority record 


12

Delete a linked/controlled MARC bib field via data import AND no data field protection applied

  1. Existing bib record has a MARC =600  07$aBlack Panther$c(Fictitious character)$2fast$0(OCoLC)fst02000849
  2. Incoming bib record does not have this field 


  • No change to data import process 
  • MARC 600 will no longer exist for this bib record
  • Unlink bib field from authority record 


13Data field protection handling (need to write a scenario)


14Handling multiple $0  (need to write a scenario)


15Additional subfield $9 scenarios


16Is there a scenario where data import should reject updating the entire bib record due to authority linking errors?  Please post your scenario under Comments section. 


Data import should let us upload what we want to, even if the records are poor.


JE: Linking errors should be reporting in a separate report to look at and resolve separately.