Authority Linking: Authority Name (no title) + Bib Field

Overall rules

MARC bib fields 100/600/700 can only be controlled by MARC authority field 100
MARC bib fields 110/610/710 can only be controlled by MARC authority field 110
MARC bib fields 111/611/711 can only be controlled by MARC authority field 111

MARC bib field to MARC authority field mapping table

Description	Controlled MARC bib field	Indicator 1	Indicator 2	required subfield code(s)	Has subfield $t	bib subfields that cannot be controlled	Controlling MARC authority field	Indicator 1	Indicator 2	Required subfield code(s)	additional subfields that can control a bib field

Description	Controlled MARC bib field	Indicator 1	Indicator 2	required subfield code(s)	Has subfield $t	Controlling MARC authority field	Indicator 1	Indicator 2	Required subfield code(s)	additional subfields that can control a bib field
Personal name	100	n/a	n/a	$a NOTE: If matching authority field contains $b-$u then also control those fields and populate bib field	N	100	N/A	N/A	$a	Name portion $a - Personal name (NR) $b - Numeration (NR) $c - Titles and other words associated with a name (R) $d - Dates associated with a name (NR) $e - Relator term (R) $j - Attribution qualifier (R) $q - Fuller form of name (NR) Name and title portions $g - Miscellaneous information (R) Control number
Corporate name	110	n/a	n/a	" "	N	110	" "	" "	$a	Name portion $a - Corporate name or jurisdiction name as entry element (NR) $b - Subordinate unit (R) $c - Location of meeting (R) $e - Relator term (R) Name and title portions $d - Date of meeting or treaty signing (R) $g - Miscellaneous information (R) $n - Number of part/section/meeting (R) Control subfields $6 - Linkage (NR) $7 - Data provenance (R) $8 - Field link and sequence number (R)
Meeting name	111	n/a	n/a	" "	N	111	" "	" "	$a	Name portion $a - Meeting name or jurisdiction name as entry element (NR) $c - Location of meeting (R) $e - Subordinate unit (R) $j - Relator term (R) $q - Name of meeting following jurisdiction name entry element (NR) Name and title portions $d - Date of meeting or treaty signing (R) $g - Miscellaneous information (R) $n - Number of part/section/meeting (R) Control subfields $6 - Linkage (NR) $7 - Data provenance (R) $8 - Field link and sequence number (R) $4 - Relationship (R)
Subject Added Entry - Personal Name	600			$a NOTE: If matching authority field contains $b-$u then also control those fields and populate bib field	N/A	100	" "	" "	$a
Subject Added Entry - Corporate Name	610			" "	N/A	110	" "	" "	$a
Subject Added Entry - Conference Name	611			" "	N/A	111	" "	" "	$a
Added Entry - Personal Name	700			$a NOTE: If matching authority field contains $b-$u then also control those fields and populate bib field	N/A	100	" "	" "	$a
Added Entry - Corporate Name	710			" "	N/A	110	" "	" "	" "
Added Entry - Meeting Name	711			" "	N/A	111	" "	" "	" "
Series Added Entry - Personal Name	800				N/A	100	" "	" "
Series Added Entry - Corporate Name	810				N/A	110	" "	" "
Series Added Entry - Meeting Name	811				N/A	111	" "	" "

Example

Bib record: https://bugfest-lotus.int.aws.folio.org/inventory/view/3e05afde-c5e3-4641-92c2-9bd96f51b033?filters=source.MARC&qindex=contributor&query=chin%2C%20staceyann&sort=title (see below screenshot)

Authority record: https://bugfest-lotus.int.aws.folio.org/marc-authorities/authorities/1907249d-d31b-4609-bd2a-32abc3fde687?authRefType=Authorized&headingRef=Chin%2C%20Staceyann%2C%201972-&query=chin&segment=search (see below screenshot)

Validation rules

The MARC bib tags listed in this document can only be linked to an authority record tag listed in this document.
A MARC tag field can only link to one MARC authority tag
A MARC authority record can be linked to multiple bib records

How to link a MARC bib field to a MARC authority record

Manual

When user is on the quickMARC - bib record then provide an option to find the authority record for each MARC bib tag listed in the above table.
When user gets to the Select a MARC authority record modal then also pass a query to auto-populate the results list
1. First query to pass > If the MARC bib field contains a subfield $0 then conduct an Authority identifier search for the record
  1. Need to search MARC authority 010 $a OR 024 $0
    1. Additional requirements needed to handle a MARC bib field $0 that is a URL
2. If MARC bib field does not contain a $0 then conduct a search for MARC bib subfields $a-u$ that appear in the field
3. If MARC bib field does not contain any subfields then do not pass a query, user will conduct search
4. Also when user views the Select a MARC authority record modal then the search options default should be based on MARC bib field to be linked. For example, If MARC bib tag = 100 then Select a MARC authority modal should default Search/Browse option to Personal name

Automated

For automation - matches are based on the MARC bib field containing a subfield $0 and the MARC authority record containing the same $0 in either MARC authority 010$a OR 024 $0 OR 001

What happens when you link?

Controlled MARC bib fields
- Edit quickMARC bib - updated with MARC authority field details
- Edit quickMARC bib - become read only
Additional requirements will be created as to additional areas impacted (i.e. Browse lists/MARC authority app)

How to unlink a MARC bib field to a MARC authority record

Manual: Edit quickMARC - bib record and Unlink field
No automation for initial release

What happens when you unlink?

Edit quickMARC bib - Unlink the bib field from the authority record. Data persists in MARC bib field. The data is now editable.
Additional requirements will be created as to additional areas impacted (i.e. Browse lists/MARC authority app)

What about data import?

Librarians have stated that they do not want data import to modify link state.
1. So, in the case that there is a change to the MARC bib field that makes the link MARC authority record inconsistent then we need to flag this inconsistency so that librarians can check and resolve inconsistency
  1. Additional requirements to support a widget or in-app report
  2. Additional requirements to show an indication on quickMARC
2. In the case that the controlling MARC authority record has been changed via data import then we need to flag this inconsistency so that librarians can check and resolve inconsistency
  1. Additional requirements to support a widget or in-app report
  2. Additional requirements to show an indication on quickMARC
  3. Additional requirement will be created to support a job to be run to update MARC bib records based on the fact that the MARC authority record changed
3. If changes were made to match points $0 then we need to flag this inconsistency so that librarians can check and resolve inconsistency
  1. Additional requirements to support a widget or in-app report
  2. Additional requirements to show an indication on quickMARC
  3. Additional requirement will be created to support a job to be run to unlink