X10 Corporate Names - General Information

Field definition and scope:

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

410 See From Tracing - Corporate Name (R)

710 Established Heading Linking Entry - Corporate Name (R)

Record requirements: The National level record requirement for the corporate name fields is Mandatory if applicable, except for field 710 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 a name or name/title heading that contains a corporate name 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 an item or a series, 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 the X51 fields.

For non-subject purposes, other names used alone are contained in the X10 fields.

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

Corporate names used in phrase subject headings (e.g., Catholic Church in art) are contained in the X50 fields.

The indicators, subfield codes, and input conventions for the corporate name fields 110, 410, 510, and 710 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 X10	Corporate Names	*	*
Indicator:
First	Type of corporate name entry element	M
0	Inverted name	A
1	Jurisdiction name	A
2	Name in direct order	A

Second
110, 410, 510	Undefined; contains a blank	M

710	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	Corporate name or jurisdiction name as entry element	M	NR
$b	Subordinate unit	A	R
$c	Location of meeting	A	R
$e	Relator term	*	R

	Title portion
$f	Date of a work	A	NR
$h	Medium	*	NR
$k	Form subheading	A	R
$l	Language of a work	A	NR
$m	Medium of performance for music	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

	Name and title portions
$d	Date of meeting or treaty signing	A	R
$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 [410, 510, 710]	current - A earlier - A	R
$w	Control subfield [410, 510, 710]	A	NR
$0	Authority record control number or standard number [510, 710]	A	R
$1	Real World Object URI [510, 710]		R
$2	Source of heading or term [710]	A	NR
$4	Relationship [410, 510, 710]	O	R
$5	Institution to which field applies [410, 510, 710]	A	R
$6	Linkage	A	NR
$8	Field link and sequence number	O	R

Input conventions:

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

Punctuation

Spacing

Display constant for X10 fields

Content designator history:

Second Indicator - Nonfiling characters [110, 410, 510] [obsolete]: The second indicator position was made obsolete in fields 100, 400, and 500 in 1993. The values were: 0-9 (Number of nonfiling characters present).

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 $i - Reference instruction phrase [410, 510] [redefined, 2009]

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

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

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

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

$0 - Record control number [510, 710] [new, 1997]

$0 - Record control number [510, 710] [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 [510, 710] [new, 2017]

Subfield $4 - Relationship code [410, 510] [new, 2009]

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

Subfield $4 - Relationship code [410, 510, 710] [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.