Subject validation

Potential requirement

Action: Manual link a MARC bib 6XX field to an authority record

UXPROD-4033 - Getting issue details... STATUS

MODELINKS-56 - Getting issue details... STATUS

Name & Name-title headings

Uniform title heading

Geographic name heading

Subject/Topical term heading

Genre heading

Logic order

1. The authority 1XX must be eligible to be linked to bib field 6XX.
   1. If it is not, then do not link regardless of authority record’s 008/11
2. If the authority 1XX is eligible to link to bib field 6XX then check bib field indicator 2 value is a matched to authority record’s 008/11
   1. If not, then do not link authority record.
3. Assuming the first two are satisfied. When the bib field indicator 2 = 7 then check that the bib subfield $2 matches the authority record 040$f.
   1. If not, then do not link authority record.
4. TBD requirement: Handling bib field indicator 2 = 4

Subject validation rules

Rules table based on Bib indicator 2 value AND Authority 008 position 11 value

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

Use cases

Authority record controls a 6XX bib field

Requirements

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

1. If the linked bib field contains the same $0 then
   1. No change to controlled fields including subfield $2
   2. Update uncontrolled fields
   3. Retain same $9
2. If the linked bib field has a different $0 then no change from Orchid implementation. Unlink bib field and update fields
3. If the linked has no $0 or $9 then unlink bib field and update field.
4. If the linked

Questions

• Does this apply to 7XX?
• Does this only apply to 650/655? 
• How should we handle a blank indicator 2? 
• How should we handle when indicator 2 = 4? Does it match to 008/11 = null/blank?