610 Subject Added Entry - Corporate Name

Field definition and scope:

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

Meeting names that are not entered subordinately to a corporate body are recorded in field 611 (Subject Added Entry - Meeting Name).

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

Field 610 is repeatable.

Guidelines for applying content designators:

The defined content designators identify the subelements occurring in corporate 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 corporate name, a form subheading, a title of a work, and/or a city section name entered under the name of a jurisdiction are X10 corporate names.

A name of a jurisdiction that represents an ecclesiastical entity is an X10 corporate name.

For subject purposes, other names of jurisdictions used alone or followed by subject subdivisions are geographic names and are contained in field 651 (Subject Added Entry - Geographic Name).

For non-subject purposes, other names used alone are contained in 110 and 710 fields.

A named meeting that is entered under a corporate name is contained in the X10 fields.

A meeting entered directly under its own name is contained in the X11 fields.

Corporate names used in phrase subject headings (e.g., Catholic Church in art) are contained in field 650 (Subject Added Entry - Topical Term).

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 610	Subject Added Entry - Corporate Name	A	O	R
Indicator:
First	Type of corporate 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	Corporate name or jurisdiction name as entry element	M	O	NR
$b	Subordinate unit	A	O	R
$c	Location of meeting	A	O	R
$d	Date of meeting or treaty signing	A	O	R
$e	Relator term	O	O	R
$f	Date of a work	A	O	NR
$g	Miscellaneous information	A	O	R
$h	Medium	O	O	NR
$k	Form subheading	A	O	R
$l	Language of a work	A	O	NR
$m	Medium of performance for music	A	O	R
$n	Number of part/section/meeting	A	O	R
$o	Arranged statement for music	A	O	NR
$p	Name of part/section of a work	A	O	R
$r	Key for music	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 "corporate" name)

Punctuation

Spacing

Display constant

Initial articles (includes information on diacritics or special characters)

Content designator history:

Subfields $c - Location of meeting [new]

$d - Date of meeting or treaty signing [new]

The location and date of a meeting and the date of signing of a treaty entered under a corporate body or jurisdiction were not separately subfield coded but included in subfield $p prior to the definition of subfields $c and $d in 1980.

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

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

Subfield $k - Form subheading: Prior to 1981, the title "Treaties, etc." was considered a form subheading and coded in subfield $k.

Subfields $n - Number of part/section/meeting [new]

$p - Name of part/section of a work [redefined]

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.

In 1980, the definition of subfield $n was expanded to include meeting numbers. Prior to this change, the number of a meeting entered under a corporate body was not separately subfield coded.

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.