611 Subject Added Entry

Field definition and scope:

Field 611 contains a subject added entry in which the entry element is a meeting or conference name. Subject added entries are assigned to a bibliographic record to provide access according to established subject cataloging principles and guidelines. Field 611 may be used by any institution assigning subject headings based on the lists and authority files identified in the second indicator position or in subfield $2 (Source of heading or term).

Subject added entries for meeting or conference names that are entered subordinately to a corporate body are recorded in field 610.

The National level record requirement for this field is Mandatory if applicable.

Field 611 is repeatable.

Guidelines for applying content designators:

The content designators identify the subelements occurring in meeting name fields 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) and Minimal-level (MLR) record requirements, and designator repeatability, see table below:

Position	Description	NLR	MLR	Repeatability
Field 611	Subject Added Entry - Meeting Name	A	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	A
1	LC subject headings for children's literature	A
2	Medical Subject Headings	A
3	National Agricultural Library subject authority file	A
4	Source not specified	A
5	Canadian Subject Headings	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	O	NR
$c	Location of meeting	A	O	R
$d	Date of meeting or treaty signing	A	O	R
$e	Subordinate unit	A	O	R
$f	Date of a work	A	O	NR
$g	Miscellaneous information	A	O	R
$h	Medium	O	O	NR
$j	Relator term	O	O	R
$k	Form subheading	A	O	R
$l	Language of a work	A	O	NR
$n	Number of part/section/meeting	A	O	R
$p	Name of part/section of a work	A	O	R
$q	Name of meeting following jurisdiction name entry element	A	O	NR
$s	Version	A	O	R
$t	Title of a work	A	O	NR
$u	Affiliation	O	O	NR
$v	Form subdivision	A	O	R
$x	General subdivision	A	O	R
$y	Chronological subdivision	A	O	R
$z	Geographic subdivision	A	O	R
$0	Authority record control number or standard number	O	O	R
$1	Real World Object URI			R
$2	Source of heading or term	A	O	NR
$3	Materials specified	O	O	NR
$4	Relationship	O	O	R
$6	Linkage	A	O	NR
$8	Field link and sequence number	O	O	R

See: Examples for this field.

Input conventions:

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

Punctuation

Spacing

Display constant

Initial articles (includes information on diacritics or special characters)

Content designator history:

Subfield $a - Meeting name or jurisdiction name as entry element [redefined, 1972]

Subfield $b - Number [obsolete, 1980]: In 1980, the definition of subfield $n was expanded to include meeting numbers and subfield $b was made obsolete.

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

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

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

Subfield $j - Relator term [new, 2006]

Subfield $n - Number of part/section/meeting [new, 1979]

Subfield $p - Name of part/section of a work [redefined, 1979]: In 1979, subfield $n was defined for numbered parts/sections and subfield $p (Part) was redefined to include only named parts/sections. Prior to that change, both the number and the name of a part were contained in one $p subfield.

Subfield $q - Name of meeting following jurisdiction name entry element [new, 1972]: The name of a meeting entered under a jurisdiction name was not separately subfield coded prior to the definition of subfield $q in 1972. At the same time, subfield $a was expanded to include a jurisdiction name as entry element.

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

Subfield $0 - Authority record control number [new, 2007]

Subfield $0 - Authority record control number [redefined, 2010]

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

Subfield $4 - Relator 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.