MARC 21 Concise Holdings: Control Subfields
This is an ARCHIVED VERSION of the 2001 electronic
edition of the MARC 21 Concise Formats. Please see
www.loc.gov/marc/concise/ for
the most up-to-date version of the electronic MARC 21 Concise Formats.
This section contains descriptions of three subfields that are used to link field data to
specific institutions or to other fields. These subfields are defined for several
($5 (Institution to which field applies)) or most $6 (Linkage),
and $8 (Field link and sequence number)) fields in the format, thus their descriptions are brought
together in this section. The subfields are included in field level subfield lists wherever they are
defined, with pointers to this section.
Information for Translators and Other Users
Items highlighted in red indicate changes made
after the 2000 edition of the MARC 21 Concise Formats was published and
are included in the 2001 printed edition of the MARC 21 Concise Formats.
Subfield $5 contains the MARC code of the institution or organization that holds the copy
to which the data in the field applies. It is used for institution-specific information that may or
may not apply to the universal use of the holdings record.
The sources for the MARC code are the
MARC Code List for Organizations
(maintained by the Library of Congress) and
Symbols and Interlibrary Loan Policies in Canada
(maintained by the National Library
of Canada).
583 |
##$aQueued for preservation;$c19861010;$ePriority;$fTitle IIC project$5DLC |
Subfield $6 contains 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 the
Multiscript
Records
section; 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
The Linking tag part contains the tag number of the associated field
and is always three characters in length. 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.
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 the
Multiscript Records
section). 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.
852 |
4#$6 880-01$a[Location in Latin script] |
880 |
2#$6852-01/(2/r$a[Location in Hebrew script linked to associated field] |
Script identification code
The 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 |
(2 |
|
Hebrew |
880 |
1#$6852-01/(N$a[Location in Cyrillic script] |
The 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.)
880 |
1#$6852-01/(2/r$h[Call number in Hebrew script] |
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.
Subfield $8 contains data that 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>
Linking number
This 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
This number is separated from linking number by a period "." and may be 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
This code 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. In the absence of a field link type, it is assumed
that subfield $8 is used for linking and sequencing 85X, 86X, or 87X fields (captions,
enumeration and chronology, textual holdings, and/or item information). Subfield
$8 is essential to link and order these fields. No explicit field link types have
been defined in MARC 21 Format for Holdings Data.
583 |
##$81.2$aExhibit$c1982/12/01 through 1982/03/01$jMuseum of Fine Arts |
876 |
##$81.2$aXAX1222-1$pA1234567 |
853 |
03$81$aBd.$i(year) |
853 |
03$82$an.F:Bd$i(year) |
863 |
30$81.1$a1-21$i1911-1923/1924 |
863 |
30$82.1$a1-25$i1925/1926-1942/1943 |
853 |
00$81$ano.$i(year)$j(month) |
863 |
40$81.1$a180-226$i1976-1981 |
863 |
44$81.2$a228 |
863 |
40$81.3$a230$i1982$jApr. |
863 |
40$81.4$a235$i1982$jDec. |
863 |
40$81.5$a237$i1983$jMar. |
863 |
40$81.6$a239-242$i1983$jJune-Oct. |
853 |
20$81$av.$bno.$u12$vr$i(year)$j(month) |
863 |
40$81.1$a108$b1-6$i1989$j1-6 |
863 |
40$81.2$a108$b7-12$i1989$j7-12 |
863 |
40$81.3$a109$b1-6$i1990$j1-6 |
863 |
40$81.4$a109$b7-12$i1990$j7-12 |
876 |
##$81.1$aAAA1000-1-1$pA1481283827 |
876 |
##$81.2$aAAA1000-1-3$pA1481283831 |
876 |
##$81.3$aAAA1000-1-2$jLost$pA1481283845 |
876 |
##$81.4$aAAA1000-1-5$pA1481283863 |
Subfield $8 is always the first subfield in the field.
APPLICATION OF SUBFIELD $8 IN FIELDS 866-868 (TEXTUAL
HOLDINGS)
Subfield $8 contains data that links related 853-868
holdings data fields. Only a linking number is used in the Textual Holdings
fields to include whether the field is:
- the only holdings data field in the holdings statement
or the only holdings data field to be used for display,
- an alternative display for one or more portions of
the holdings data in 863-865 Enumeration and Chronology field(s) contained
in the holdings statement, or
- a holdings data field in addition to the 863-865 Enumeration
and Chronology field(s) contained in the holdings statement.
The linking number used in subfield $8 is determined
by the following conditions:
Linking number is 0
Holdings are recorded only in a 866-868 Textual Holdings
field. No 853-855 Captions and Pattern and 863-865 Enumeration and Chronology
fields occur in the holdings statement.
867 |
31$80 $a"Teacher's guide" pt. A-B |
Holdings data are recorded in the linked 853-855 Captions and Pattern/863-865
Enumeration and Chronology fields but the display form of the holdings is recorded
in a Textual Holdings field.
853 |
20$81$a<captions and pattern> |
853 |
20$82$a<captions and pattern> |
853 |
20$83$a<captions and pattern> |
863 |
43$81.1$a<enumeration and chronology> |
863 |
43$82.1$a<enumeration and chronology> |
863 |
43$82.2$a<enumeration and chronology> |
863 |
43$83.1$a<enumeration and chronology> |
866 |
40$80$a<textual holdings for display> |
[No display is generated from any of the 853/863 fields. Field 866 replaces
all of the 853/863 fields for display purposes.] |
Linking number is the same as the linking number in
the linked 853-855 and 863-865 fields
One or more portions of the holdings data recorded in the
853-855 Captions and Pattern/863-865 Enumeration and Chronology fields is also
recorded in an 866-868 Textual Holdings field to provide an alternative form for
display purposes. The linking number in subfield $8 must match the linking number
in subfield $8 of the linked 853-855/863-865 fields that the 866-868 field replaces.
The content of a Textual Holdings field must replace all of the Enumeration and
Chronology fields linked to a Captions and Pattern field.
If multiple Captions and Pattern/Enumeration Chronology fields that have consecutive
linking numbers are to be replaced for display purposes by a single Textual
Holdings field, subfield $8 may be repeated in Textual Holdings field to record
the linking number of each of the Captions and Pattern/Enumeration and Chronology
fields to be replaced.
855 |
20$81$a<captions and pattern> |
855 |
20$82$a<captions and pattern> |
855 |
20$83$a<captions and pattern> |
855 |
20$84$a<captions and pattern> |
865 |
43$81.1$a<enumeration and chronology> |
865 |
43$82.1$a<enumeration and chronology> |
865 |
43$83.1$a<enumeration and chronology> |
865 |
40$84.1$a<enumeration and chronology> |
868 |
40$82$83$a<textual
holdings for display> |
[Field 868 replaces the 855/865 fields having linking numbers 2 and
3. No display is generated from those fields.] |
Optionally, separate 866-868 Textual Holdings fields, each with one subfield $8,
may be used instead of a single 866-868 field with multiple subfields $8.
Linking number is unique and sequences the holdings
data with the enumeration and chronology of the 863-865 fields
When part of the holdings data is recorded in the 853-855
Captions and Pattern/863-865 Enumeration and Chronology fields and part is recorded
in the Textual Holdings fields, displays may be generated from both types of fields.
This situation may occur when the holdings are extremely complex or the publication
pattern varies greatly for only a certain period of time. A unique whole number
is used as the linking number in the Textual Holdings field to sequence the field
among the linking numbers used in the 853-855/863-865 fields according to the
enumeration and chronology recorded in each field.
855 |
20$81$a<captions and pattern> |
855 |
20$83$a<captions and pattern> |
865 |
40$81.1$a<enumeration and chronology> |
865 |
40$83.1$a<enumeration and chronology> |
868 |
41$82$a<textual holdings> |
[The enumeration/chronology of the holdings recorded in field 868 falls
between the fields with linking numbers 1 and 3. A display may be generated
from all of the fields.] |
Go to top of document
Go to: MARC
21 Concise Holdings Format (Archived)
| MARC Home Page
Library
of Congress
Library of Congress Help Desk
(
12/24/2002
)