X11 Meeting Names - General Information

Field definition and scope:

Each meeting name field is unique in its definition and scope. For specific information, select from the list below.

711 Established Heading Linking Entry - Meeting Name (R)

Record requirements: The National level record requirement for the meeting name fields is Mandatory if applicable, except for field 711 which is Optional. For the national level requirements by subfield, see the specific field.

Field repeatability: See the specific field for its repeatability.

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.

The indicators, subfield codes, and input conventions for the meeting name fields 111, 411, 511, and 711 follow similar patterns. Guidelines for applying them are below. Subfields are grouped by type of entry.

For indicator and subfield code definitions and examples, National level (NLR) record requirements, and designator repeatability, see table below. An asterisk ( * ) in the column indicates that the requirement varies. See table in the specific field.:

Position	Description	NLR	Repeatability
Field X11	Meeting Names	*	*
Indicator:
First	Type of meeting name entry element	M
0	Inverted name	A
1	Jurisdiction name	A
2	Name in direct order	A

Second
111, 411, 511	Undefined; contains a blank	M

711	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:
	Name portion
$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
$j	Relator term	O	R
$q	Name of meeting following jurisdiction name entry element	A	NR

	Title portion
$f	Date of a work	A	NR
$h	Medium	*	NR
$k	Form subheading	A	R
$l	Language of a work	A	NR
$p	Name of part/section of a work	A	R
$s	Version	A	R
$t	Title of a work	A	NR

	Name and title portions
$g	Miscellaneous information	A	R
$n	Number of part/section/meeting	A	R

	Subject subdivision portion
$v	Form subdivision	A	R
$x	General subdivision	A	R
$y	Chronological subdivision	A	R
$z	Geographic subdivision	A	R

	Tracing and linking subfields
$i	Relationship information [411, 511, 711]	current - A earlier - A	R
$w	Control subfield [411, 511, 711]	A	NR
$0	Authority record control number or standard number [511, 711]	A	R
$1	Real World Object URI [511, 711]		R
$2	Source of heading or term [711]	A	NR
$4	Relationship [411, 511, 711]	O	R
$5	Institution to which field applies [411, 511, 711]	A	R
$6	Linkage	A	NR
$8	Field link and sequence number	O	R

Input conventions:

Ambiguous headings (what is considered a "meeting" name)

Punctuation

Spacing

Display constant for X11 fields

Content designator history:

Second Indicator - Nonfiling characters [111, 411, 511] [obsolete]: The second indicator position was made obsolete in fields 111, 411, and 511 in 1993. The values were: 0-9 (Number of nonfiling characters present).

Subfield $b - Number [obsolete, 1980]: 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 - Reference instruction phrase [411, 511] [redefined, 2009]

Subfield $i - Relationship information [711] [new, 2014]

Subfield $j - Relator term [new, 2006]

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

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

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

$0 - Record control number [511, 711] [new, 1997]

$0 - Record control number [511, 711] [redefined, 2010]

$v - Form subdivision [redefined, 1995]

$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. In 1997, subfield $0 was added as Record control number in 5XX and 7XX fields and $u was made obsolete.

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

Subfield $4 - Relationship code [411, 511] [new, 2009]

Subfield $4 - Relationship code [711] [new, 2014]

Subfield $4 - Relationship code [411, 511, 711] [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.