Page Comparison

...

Subject/Topical term (650/655 bib/150/155 authority) default validation rules

Handle 7 - Source specified in subfield $2

• Default rules : MARC authority 008 position 11 = z AND must have a MARC bib subfield 2 value
• Tenant can override
  • Default 008/position 11 value with

...

• • any authority heading (150) regardless of 008/position 11

...

• • value OR can be set to multiple 008/position 11 values

...

• • Default 008/position 15 value with any

...

If 6XX has Bib Indicator 2 = 7 then check bib subfield $2 for the codes listed below AND only link authority records that contain the same code in the authority record 040 $f (Cataloging Source / Subject heading / thesaurus conventions) OR we can use the same logic as what we use to determine authority source file value

• Support codes: aat,fast,lcdgt,lcsh,lctgm,local,mesh,naf,nal,nalnaf,wikidata,gsafd,lcgft,rbmscv
• Development should be flexible to support additional codes based on Subject Source codes listed https://www.loc.gov/standards/sourcelist/subject.html AND Genre/Form Source code https://www.loc.gov/standards/sourcelist/genre-form.html in the future 

Additional requirements: If 6XX has Bib Indicator 2 = 7 then check bib subfield $2

• If successfully linked, then bib subfield $2 must be set to read only
  • If successfully linked, then user cannot manually enter a bib subfield $2 OR multiple bib subfield $2s{}
  • If successfully linked AND user can imports a different bib subfield $2 THEN do not change $2 UNLESS $0 / $9 is not valid or is does not exist 
  • If successfully linked AND user can imports multiple bib subfield $2s THEN do not change $2 UNLESS $0 / $9 is not valid or is does not exist 
  • If not linked then allow for multiple $2s and allow for subfield $2 to be edited
• Cannot link if
  • Authority 1xx is not eligible to be linked to bib field 6xx
  • Authority record 008/11 does not match to bib field Indicator 2 value
  • Authority record 040 $f does not match to bib field subfield $2 value when bib field indicator 2 = 7
  • When authority record contains multiple 040 $f values
  • When bib field contains multiple bib subfield $2 values
• If the 6XX was linked prior to the implementation of these requirements, then allow the links to be maintained. Only impacts new linking.

Additional Requirements

• Setting > Authority control > Enable subject validation
  • If not enabled then no change to Orchid implementation
• If successfully linked, then bib subfield $2 must be set to read only
• If successfully linked, then user cannot enter a bib subfield $2 this is regardless of bib subfield $2 as the matching value
• Cannot link if
  • Authority 1xx is not eligible to be linked to bib field 6xx
  • Authority record 008/11 does not match to bib field Indicator 2 value
  • Authority record 040 $f does not match to bib field subfield $2 value when bib field indicator 2 = 7
  • When authority record contains multiple 040 $f values
  • When bib field contains multiple bib subfield $2 values
• If the 6XX was linked prior to the implementation of these requirements, then allow the links to be maintained. Only impacts new linking.
• TBD requirement: Handling bib field indicator 2 = 4
  • value. It is all OR a (default).
  • Tenant can define MARC bib subfield 2 handling by 
    
    • Setting the MARC authority field number and subfield to check for matching bib subfield 2 value 
      • Can only set multiple MARC authority field numbers and subfields AND cannot set to null 
    • Default MARC authority field number and subfield: 040 $f
    • Removing MARC authority field number and subfield will trigger a warning message that the link bib fields will become unlinked
    • Editing MARC authority subfield value will trigger a warning message and will result in the bib subfield 2 value being updated 

Subfield 2 > Create/Edit/Derive a MARC bib requirements

• Unlinkable fields > Allow user to enter/edit a subfield 2 (including multiples) 
• Linkable fields > Allow user to enter/edit a subfield 2 (including multiples)  
• Linked fields that are not 6XX > Not read only AND user can enter/edit subfield 2 (including multiples) 
• Linked fields that are 6XX > Read only AND user cannot enter/edit subfield 2 (including multiples) 

Subfield 2 > Create a MARC bib import requirements 

• Unlinkable fields > Allow user to import and create a field(s) with a subfield 2 (including multiples) 
• Linkable fields > Allow user to import and create a field(s) with a subfield 2 (including multiples)  

Subfield 2 > Update a MARC bib import requirements 

• Unlinkable fields > Allow user to import and update a field(s) with a subfield 2 (including multiples) 
• Linkable fields > Allow user to import and update a field(s) a subfield 2 (including multiples)
• Linked fields that are not 6XX > Allow user to import and update a field(s) a subfield 2 (including multiples)
• Linked fields that are 6XX > 
  • If the same subfield 2 then no change 
  • If a different subfield 2 then do not change existing subfield 2 UNLESS $0 has changed or does not exist 
  • If multiple subfield 2 then do not change existing subfield 2 UNLESS $0 has changed or does not exist

Automated linking 

• If user enables automated linking for any 6XX then check against these subject thesaurus validation rules and presence of $0 
• If $0 exist for an authority record and that authority record follows the defined tenant subject thesaurus validation rules then link the bib field 
  • If a single subfield 2 is used to link the bib field then the field should be read only
  • If multiple subfield 2 then only keep the subfield 2 that is tied to the linked authority heading  

Manual linking 

• Apply validation rules 
• If user creates a new field then
  • Check 2nd indicator value for rules to apply 
  • IF 2nd indicator value = 7 then populate subfield 2 with authority field/subfield value defined by library Source code and make read only 
• If invalid then show an error message [You have selected an invalid heading based on the bibliographic field you want controlled. Please revise your selection.]

Authority updates

040f or field/subfield defined by library as Source > Create/Edit MARC authority via UI  

• Must be NR MARC field and subfield.
• If multiple or does not exist then Error: Show an error message > Can only have one <<cataloging source (040 field) and only one subfield f value>>.

040f or field/subfield defined by library as Source  > Create a MARC Authority import requirements 

• Must be a NR MARC field and subfield.
• If multiple then fail record and return Error: Show an error message > Can only have one <<cataloging source (040 field) and only one subfield f value>>. 

040f or field/subfield defined by library as Source > Update a MARC Authority import requirements 

• Must be a NR MARC field and subfield.
• Update to 040f or field/subfield defined by library as Source will also update linked bib fields 
• If 040f or field/subfield defined by library as Source is deleted then fail authority record update and return error message
• If multiple then fail authority record update and return error message 
• Error: Show an error message > Can only have one <<cataloging source (040 field) and only one subfield f value>>. 

008 updates 

Create/Edit Authority via UI 

• Any changes to position 11 and/or 15 that will change the linked bib field second indicator value should result in unlinking the bib field from the authority heading. UI will show an are you sure want to do this warning message. 

Create a MARC Authority import requirements 

• N/A 

Update a MARC Authority import requirements 

• Any changes to position 11 and/or 15 (including entire removal of 008) that will change the linked bib field second indicator value should result in unlinking the bib field from the authority heading

...

Use cases

...

1. Do not allow user to add multiple 040 $f when linked to a bib record AND 008/11 = z. (try to make this simpler and write stories when use edits 040 $f when linked) 
   1. Action: If user attempts to add multiple 040 $f then display an error message
2. Action: User edits the 008/11 value to any valid value but z > Show a “Are you sure you want to change the subject classification for <<total number of linked bib records>>” message. If the user proceeds with change, then update bib field indicator 2 value.
3. Action: User edits the 008/11 value to z AND adds a 040 $f value then Show a “Are you sure you want to change the subject classification for <<total number of linked bib records>>” message. If the user proceeds with change, then update bib field indicator 2 to “7” and subfield $2 to authority 040 $f
4. Action: User edits the 008/11 value to z AND does not enter 040 $f then display error message that the change cannot be saved unless one 040 $f is entered

Authority record controls a 6XX bib field (update bib record via data import) – NO automated linking

...

Questions

...

...

...