MARC 21 Format for Bibliographic Data: Appendix A: Control Subfields (Network Development and MARC Standards Office, Library of Congress)

This is an ARCHIVED VERSION of the 2008 electronic edition of the MARC 21 Concise Formats. Please see loc.gov/marc/concise/ for the most up-to-date version of the electronic MARC 21 Concise Formats.

Five subfields that are used to link field data to specific institutions or to other fields. These subfields are defined for several ($w (Bibliographic record control number), $0 (Authority record control number), $5 (Institution to which field applies) or most ($6 (Linkage), $8 (Field link and sequence number) fields in the format, thus their descriptions are brought together in this appendix. The subfields are included in field level subfield lists wherever they are defined, with pointers to this appendix.

$w - Bibliographic record control number

System control number of the related bibliographic record preceded by the MARC code, enclosed in parentheses, for the agency to which the control number applies. See Organization Code Sources for a listing of sources used in MARC 21 records.


800	1#$aNegt, Oskar$tSchriften.$vBd. 2$w(DE-101b)967682460

$0 - Authority record control number

System control number of the related authority record preceded by the MARC code, enclosed in parentheses, for the agency to which the control number applies. See Organization Code Sources for a listing of sources used in MARC 21 records.


100	1#$aBach, Johann Sebastian.$4aut$0(DE-101c)310008891

$5 - Institution To Which Field Applies

MARC code of the institution or organization that holds the copy to which the data in the field applies. Data in the field may not apply to the universal description of the item or may apply universally to the item but be of interest only to the location cited.

See Organization Code Sources for a listing of sources used in MARC 21 records.


500	##$aFrom the papers of the Chase family.$5DLC
500	##$aThe Library of Congress copy has bookplate of the Benedictine Monastery in Grafschaft; inscribed by Thomas Jefferson.$5DLC
500	##$aPlates 4, 5, and 9 are wanting.$5DLC
500	##$aUniversity Library's copy has ms. notes by author on endpapers.$5WU
583	##$aQueued for preservation$c19861010-$ePriority$fTitle IIC project$5DLC
655	##$aAnnotations (Provenance)$zSweden$y18th century.$2rbprov$5MH-H
710	2#$aBridgewater Library,$dformer owner.$5NjP
700	1#$aKissinger, Henry,$d1923-$5DLC

$6 - Linkage

Data that links fields that are different script representations of each other. Subfield $6 may contain the tag number of an associated field, an occurrence number, a code that identifies the first script encountered in a left-to-right scan of the field, and an indication that the orientation for a display of the field data is right-to-left. A regular (non-880) field may be linked to one or more 880 fields that all contain different script representations of the same data. Subfield $6 is structured as follows:

$6 [linking tag]-[occurrence number]/[script identification code]/[field orientation code]

Subfield $6 is always the first subfield in the field.

Descriptions of multiscript record models, with examples, are in Multiscript Records; specifications for field 880 are under that field; specifications for character sets and repertoires for scripts are found in MARC 21 Specifications for Record Structure, Character Sets, and Exchange Media.

Linking tag and occurrence number
Linking tag part contains the tag number of the associated field. This part is followed immediately by a hyphen and the two-digit occurrence number part. A different occurrence number is assigned to each set of associated fields within a single record. The function of an occurrence number is to permit the matching of the associated fields (not to sequence the fields within the record). An occurrence number may be assigned at random for each set of associated fields. An occurrence number of less than two digits is right justified and the unused position contains a zero.


100	1#$6880-01$a[Heading in Latin script]
880	1#$6100-01/(N$a[Heading in Cyrillic script]


245	10$6880-03$aSosei to kako :$bNihon Sosei Kako Gakkai shi.
880	10$6245-03/$1$a[Title in Japanese script] :$b[Subtitle on Japanese script] . [Primary script is Latin; alternate script is Japanese]


100	1#$6880-01$a[Name in Chinese script] .
880	1#$6100-01/(B$aShen, Wei-pin. [Primary script is Chinese; alternate script is Latin]

When there is no associated field to which a field 880 is linked, the occurrence number in subfield$6 is 00. It is used if an agency wants to separate scripts in a record (see Multiscript Records). The linking tag part of subfield $6 will contain the tag that the associated regular field would have had if it had existed in the record.


880	##$6530-00/(2/r$a[Additional physical form available information in Hebrew script] [Field 880 is not linked to an associated field. The occurrence number is 00.]

Script identification code
Occurrence number is followed immediately by a slash (/) and the script identification code. This code identifies the alternate script found in the field. The following codes are used:

Code	Script
(3	Arabic
(B	Latin
$1	Chinese, Japanese, Korean
(N	Cyrillic
(S	Greek
(2	Hebrew


880	1#$6100-01/(N$a[Heading in Cyrillic script]

Entire field need not be in the script identified in subfield $6. If more than one script is present in the field, subfield $6 will contain the identification of the first alternate script encountered in a left-to-right scan of the field.

Note also that the script identification code is used in field 880, subfield $6, but this data element is not generally used for subfield $6 of the associated regular field. In the associated field, the data is assumed to be the primary script(s) for the record.

Orientation code
In a MARC record, the contents of field 880 are always recorded in their logical order, from the first character to the last, regardless of field orientation. For a display of the field, the default field orientation is left-to-right. When the field contains text that has a right-to-left orientation, the script identification code is followed by a slash (/) and the field orientation code. The MARC field orientation code for right-to-left scripts is the letter r. The orientation code is only included in fields with right-to-left orientation, since left-to-right orientation is the default orientation in 880 fields. (See MARC 21 Specifications for Record Structure, Character Sets, and Exchange Media for a detailed description of field orientation.)


110	2#$6880-01$a[Heading in Latin script]
880	2#$6110-01/(2/r$a[Heading in Hebrew script linked to associated field]

Note that the orientation code is used in field 880, subfield $6, but this data element is not generally used for subfield $6 of the associated regular field. In the associated field, the data is assumed to be the usual orientation of the primary script(s) for the record.

$8 - Field Link and Sequence Number

Identifies linked fields and may also propose a sequence for the linked fields. Subfield $8 may be repeated to link a field to more than one other group of fields. The structure and syntax for the field link and sequence number subfield is:

$8 [linking number].[sequence number]\[field link type]

Please note that subfield $8 is defined differently in field 852 where it is used to sequence related holdings records. Please see the description of field 852, subfield $8 in the MARC 21 Format for Holdings Data for more information.

Linking number is the first data element in the subfield and required if the subfield is used. It is a variable-length whole number that occurs in subfield $8 in all fields that are to be linked. Fields with the same linking number are considered linked.

Sequence number is separated from the linking number by a period "." and is optional. It is a variable- length whole number that may be used to indicate the relative order for display of the linked fields (lower sequence numbers displaying before higher ones). If it is used it must occur in all $8 subfields containing the same linking number.

Field link type is separated from preceding data by a reverse slash "\". It is a code indicating the reason for the link and it follows the link number, or sequence number if present. Field link type is required except when $8 is used to link and sequence 85X-87X holdings fields. The following one-character field link type codes have been defined in MARC for use in subfield $8:

a - Action

Links one or more fields with another field to which the processing or reference actions relate. This code is typically used only when there is more than one 5XX that relate to another 5XX field.


541	##$81.1\a$3Public School and College Authority and Trade School and Junior College Authority project files$aFinance Dept.$cTransferred
583	##$81.2\a$aAppraised$c198712-$ltjb/prr
583	##$81.3\a$aScheduled$c19880127$ksrc/prr
583	##$81.4\a$aArranged$c19900619$kmc/dmj
583	##$81.5\a$aProcessed level 2$b90.160$c19901218$kmc/dmj

c - Constituent item

Used in a record for a collection, or a single item consisting of identifiable constituent units, to link the fields relating to the constituent units. All other non-linked data elements in the record pertain to the collection or item as a whole.


245	10$aBrevard Music Center$nProgram #24$h[sound recording].
505	0#$aFrom my window / Siegmesiter (world premiere) - Don Giovanni. Il mio tesorof [i.e. tesoro] / Mozart - Martha. M'appari / Flotow - Turandot. Nessun dorma / Puccini - Pines of Rome / Respighi.
650	#0$81\c$aSuites (Orchestra), Arranged.
650	#0$82\c$83\c$84\c$aOperas$xExcerpts.
650	#0$85\c$aSymphonic poems.
700	1#$82\c$84\c$aDi Giuseppe, Enrico,$d1938-$4prf
700	12$81\c$aSiegmeister, Elie$d1909-$tFrom my window;$oarr.
700	12$82\c$aMozart, Wolfgang Amadeus,$d1756-1791.$tDon Giovanni.$pMio tesoro.
700	12$83\c$aFlotow, Friedrich von,$d1812-1883.$tMartha.$pAch! So fromm, ach! so traut.$lItalian
700	12$84\c$aPuccini, Giacomo,$d1858-1924.$tTurandot.$pNessun dorma.
700	12$85\c$aRespighi, Ottorino$d1879-1936.$tPini di Roma.

r - Reproduction

Used in a record for a reproduction to identify fields linked because they contain information concerning only the reproduction. Other descriptive information in the record pertains to the original (with the exception of field 007 (Physical Description Fixed Field), 008 (Fixed-Length Data Elements: Books, Music, Serials, or Mixed Material) position 23 (Form of item), field 245 subfield $h (Title Statement / Medium), and field 533 (Reproduction Note)).


007/00	h <microform>
008/23	a <Microfilm>
245	04$aThe New-York mirror, and ladies' literary gazette$h[microform]
533	##$aMicrofilm$bAnn Arbor, Mich. :$cUniversity Microfilms,$d1950.$e3 microfilm reels ; 35 mm.$f(American periodical series, 1800-1850 : 164-165, 785)
830	#0$84\r$aAmerican periodical series, 1800-1850 ;$v164-165, 785.

x - General sequencing

Used in a record to make a link between fields to show a sequence between them. The sequence could be one that orders the pieces of a long field that has been broken up, indicates the relative importance of fields within the sequence, or is used for some other sequencing purpose. Use of the sequence number in $8 is required when this code is used.


505	00$81.1\x$tThree articles reviewing Hoeffding's work.$tWassily Hoeffding's Work in the Sixties /$rKobus Oosterhoff and Willem van Zwet.$tThe Impact of Wassily Hoeffding's Work on Sequential Analysis /$rGordon Simons.$tThe Impact of Wassily Hoeffding's Research on Nonparametrics /$rPranab Kumar Sen ...
505	80$81.2\x$tThe role of assumptions in statistical decisions.$tDistinguishability of sets of distributions. (The case of independent and identically distributed random variables) /$rWassily Hoeffding and J. Wolfowitz ...
505	80$81.3\x$tUnbiased range-preserving estimators.$tRange preserving unbiased estimators in the multinomial case.$tAsymptotic normality.$tHajek's projection lemma. [This example shows a long 505 field broken up into smaller pieces]