711 Established Heading Linking Entry

Field definition and scope:

Field 711 contains a meeting name that is equivalent to the name contained in the 111 field of the same record. It links headings within a system or from different thesauri or authority files.

The National level record requirement for this field is Optional.

Field 711 is repeatable.

Guidelines for applying content designators:

The content designators identify the subelements occurring in meeting name headings 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)].

A named meeting that is entered under a corporate name is contained in the X10 fields. Corporate names that include such words as conference or congress are also contained in the X10 fields. For example, the Congress of Neurological Surgeons, a professional group, is a corporate name.

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

Position	Description	NLR	Repeatability
Field 711	Established Heading Linking Entry - Meeting Name	O	R
Indicator:
First	Type of meeting name entry element	M
0	Inverted name	A
1	Jurisdiction name	A
2	Name in direct order	A

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	Meeting name or jurisdiction name as entry element	M	NR
$c	Location of meeting	A	R
$d	Date of meeting or treaty signing	A	R
$e	Subordinate unit	A	R
$f	Date of a work	A	NR
$g	Miscellaneous information	A	R
$h	Medium	A	NR
$i	Relationship information	A	R
$j	Relator term	O	R
$k	Form subheading	A	R
$l	Language of a work	A	NR
$n	Number of part/section/meeting	A	R
$p	Name of part/section of a work	A	R
$q	Name of meeting following jurisdiction name entry element	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 "meeting" name)

Display constant for X11 fields

Display constants for 7XX Linking Entries

Content designator history:

Subfield $b - Number [obsolete]: In 1980, the definition of subfield $n was expanded to include meeting numbers and subfield $b was made obsolete. Records created before this change may contain the number of the meeting in subfield $b.

Subfield $c - Location of meeting [changed, 2014]: In 2014, subfield $c was made repeatable.

Subfield $d - Date of meeting [redefined, 2017]: In 2017, subfield $d was redefined and made repeatable.

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

Subfield $i - Relationship information [new, 2014]

Subfield $j - Relator term [new, 2006]

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:

711 Established Heading Linking Entry - Meeting Name

DCM Z1 Instructions:

7XX Heading Linking Entries