730 Established Heading Linking Entry

Field definition and scope:

Field 730 contains a uniform title that is equivalent to the title contained in the 130 field of the same record. It links equivalent headings within a system or from different thesauri or authority files.

The National level record requirement for this field is Optional.

Field 730 is repeatable.

Guidelines for applying content designators:

The content designators identify the subelements occurring in a title that identifies an item or a series that is not entered under a name in a name/title heading. The title is constructed according to the generally accepted cataloging and thesaurus-building rules [e.g., Anglo-American Cataloguing Rules (AACR 2), Library of Congress Subject Headings (LCSH)].

Uniform titles used in phrase subject headings (e.g., Bible and atheism) are contained in the X50 fields.

A title entered under a name is contained in subfield $t (Title of a work) in the field appropriate for the author's name (X00, X10, X11).

For indicator and subfield code definitions and examples, National level (NLR) record requirements, and designator repeatability, see table below:

Position	Description	NLR	Repeatability
Field 730	Established Heading Linking Entry - Uniform Title	O	R
Indicator:
First	Undefined; contains a blank	M

Second	Thesaurus	M
0	Library of Congress Subject Headings/Name authority file	A
1	LC subject headings for children's literature	A
2	Medical Subject Headings/NLM name authority file	A
3	National Agricultural Library subject authority file	A
4	Source not specified	A
5	Canadian Subject Headings/LAC name authority file	A
6	Répertoire de vedettes-matière	A
7	Source specified in subfield $2	A

Subfield code:
$a	Uniform title	M	NR
$d	Date of treaty signing	A	R
$f	Date of a work	A	NR
$g	Miscellaneous information	A	R
$h	Medium	A	NR
$i	Relationship information	A	R
$k	Form subheading	A	R
$l	Language of a work	A	NR
$m	Medium of performance for music	A	R
$n	Number of part/section of a work	A	R
$o	Arranged statement for music	A	NR
$p	Name of part/section of a work	A	R
$r	Key for music	A	NR
$s	Version	A	R
$t	Title of a work	A	NR
$v	Form subdivision	A	R
$w	Control subfield	A	NR
	/0 Link display	M
	/1 Replacement complexity	A
$x	General subdivision	A	R
$y	Chronological subdivision	A	R
$z	Geographic subdivision	A	R
$0	Authority record control number or standard number	A	R
$1	Real World Object URI		R
$2	Source of heading or term	A	NR
$4	Relationship	O	R
$5	Institution to which field applies	A	R
$6	Linkage	A	NR
$8	Field link and sequence number	O	R

See: Example for this field.

Input conventions:

Ambiguous headings (what is considered a "uniform title")

Display constant for X30 fields

Display constants for 7XX Linking Entries

Content designator history:

Subfield $g - Miscellaneous information [changed, 2014]: In 2014, subfield $g was made repeatable.

Subfield $i - Relationship information [new, 2014]

Subfield $s - Version [changed, 2017]: Subfield $s was made repeatable.

Subfields $u - Record control number [obsolete, 1997] [USMARC only]

$v - Record control number [redefined, 1995] [USMARC only]

$0 - Record control number [new, 1997]

$0 - Record control number [redefined, 2010]

$v - Form subdivision [redefined, 1995] [USMARC only]

$3 - Authority record control number [obsolete, 1997] [CAN/MARC only]

In USMARC, from 1993 to 1995, subfield $v was defined as Record control number in the 7XX Heading Linking Entry fields. When subfield $v was adapted for form subdivisions in MARC bibliographic and authority heading fields in 1995, subfield $v was redefined as Form subdivision and subfield $u was defined as Record control number. In 1997, subfield $0 was added as Record control number in 5XX and 7XX fields and $u was made obsolete.

Subfield $w/1 - Replacement complexity [new, 2002]: In 2002, subfield $w/1 was defined with the following codes: a (Heading replacement does not require review); b (Heading replacement requires review); and n (Not applicable).

Subfield $1 - Real World Object URI [new, 2017]

Subfield $4 - Relationship code [new, 2014]

Subfield $4 - Relationship code [renamed, 2017] [redescribed, 2017]: Subfield $4 was renamed to Relationship and redescribed to allow for the recording of relationship URIs in addition to MARC and non-MARC codes.

LC Guidelines:

730 Established Heading Linking Entry - Uniform Title

DCM Z1 Instructions:

7XX Heading Linking Entries