X85 Form Subdivisions - General Information

Field definition and scope:

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

185 Heading - Form Subdivision (NR)

485 See From Tracing - Form Subdivision (R)

785 Subdivision Linking Entry - Form Subdivision (R)

Record requirements: The National level record requirement for the form subdivision fields is Mandatory if applicable, except for field 785 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 form subdivision headings constructed according to generally accepted thesaurus-building conventions (e.g., Medical Subject Headings).

A form subdivision is used as a subdivision portion of an extended subject or index term access field in bibliographic records.

A form term that is used as the lead element of an established heading record is contained in a 155 (Heading - Genre/Form Term) field.

The indicators, subfield codes, and input conventions for the form subdivision fields 185, 485, 585, and 785 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 X85	Form Subdivisions	*	*
Indicator:
First	Undefined; contains a blank	M

Second
185, 485, 585	Undefined; contains a blank	M

785	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:
	Subject subdivision portion
$v	Form subdivision	M	R
$x	General subdivision	A	R
$y	Chronological subdivision	A	R
$z	Geographic subdivision	A	R

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

Input conventions:

Punctuation

Spacing

Display constant for X85 fields

Use of X85 subfields $v, $x, $y, and $z in LCSH

Content designator history:

Subfield $i - Reference instruction phrase [485, 585] [redefined, 2009]

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

Subfield $0 - Record control number [585, 785] [redefined, 2010]

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

Subfield $4 - Relationship code [485, 585] [new, 2009]

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

Subfield $4 - Relationship code [485, 585, 785] [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.