MARC 21 Concise Classification: Location and Alternate Graphics (8XX)
Fields 856 and 880 are the only 8XX fields defined in the MARC 21 classification format
at the present time.
Information for Translators and Other Users
Items highlighted in red indicate changes made after
the 2004 edition of the MARC 21 Concise Formats was published and are
included
in the 2005 printed edition
of the MARC 21 Concise Formats.
The information required to locate an electronic item. The information identifies
the electronic location containing the item or from which it is available. It also contains
information to retrieve the item by the access method identified in the first indicator position.
The information contained in this field is sufficient to allow for the electronic
transfer of a file, subscription to an electronic journal, or logon to a library catalog.
Field 856 is repeated when the location elements vary (subfields $a, $b, $c). It is also
repeated when more than one access method may be used, mirror sites are recorded, different
formats/resolutions with different URLs are indicated, and related items are recorded.
In MARC 21 classification records, this field may be used to link an electronic resource
intended to supplement the classification scheme, such as an image of a map
in a table related to the classification of geographic names.
See the Guidelines for the Use of Field 856
for a more thorough discussion on the use of field 856.
Indicators
- First - Access method
A value that defines how the rest of the data in the field will be used. The value
in this indicator position determines which subfields are appropriate.
- # - No information provided
- 0 - Email
Access to the electronic resource is through electronic mail (email).
- 2 - Remote login (Telnet)
- 3 - Dial-up
Indicates that access to the electronic resource is through a conventional telephone line.
- 4 - HTTP
Indicates that access to the electronic resource
is through the Hypertext Transfer Protocol.
- 7 - Method specified in subfield $2
- Second - Relationship
A value that identifies the relationship between the electronic resource at the
location identified in field 856 and the entity described in the record. Only value # (no
information provided) is used for classification records.
- # - No information provided
- 8 - No display constant generated
Subfield Codes
- $a - Host name
(R)
The fully qualified domain (host name) of the electronic location. It contains a
network address which is repeated if there is more than one address for the same host. - $b - Access number
(R)
The Internet Protocol (IP) numeric address associated with a host. This data
changes frequently and is generated by the system, rather than statically
stored. - $c - Compression information
(R)
Information about the compression of a file, in particular, whether a specific
program is required to decompress the file. - $d - Path
(R)
- $f - Electronic name
(R)
- $h - Processor of request
(NR)
The username, or processor of the request; generally the data which precedes the
"@" in the host address. - $i - Instruction
(R)
An instruction needed for the remote host to process a
request. - $j - Bits per second
(NR)
- $k - Password
(NR)
- $l - Logon
(NR)
Characters needed to connect (i.e.,
logon,
login, etc.) to an electronic
resource or FTP site. This subfield is used to record general-use
logon strings which do not require special
security. - $m - Contact for access assistance
(R)
- $n - Name of location of host
(NR)
The full name of the location of the host in subfield $a, including its geographical
location. - $o - Operating system
(NR)
- $p - Port
(NR)
The portion of the address that identifies the process or service in the
host. - $q - Electronic format type
(NR)
An identification of the electronic format type,
which is the data representation of the resource, such as
text/HTML, ASCII, Postscript file, executable application,
or JPEG image. Electronic format type may be taken
from enumerated lists such as registered Internet Media
Types (MIME types). - $r - Settings
(NR)
- $s - File size
(R)
- $t - Terminal emulation
(R)
- $u - Uniform Resource Identifier
(R)
The URI, which provides standard syntax
for locating an object using existing Internet
protocols. Field 856 is structured to allow for the creation of a
URL from the concatenation of other separate 856 subfields.
Subfield $u may be used instead of those separate subfields or in
addition to them.
Subfield $u may be repeated only if both a URN or a URL or more than one URN are recorded. - $v - Hours access method available
(R)
- $w - Record control number
(R)
- $x - Nonpublic note
(R)
- $y - Link text
(R)
Used for display in place of the URL in subfield $u (Uniform resource identifier). When subfield $y is present, applications should use the contents of it as the link instead of
subfield $u linking to the destination in subfield $u. - $z - Public note
(R)
- $2 - Access method
(NR)
- $3 - Materials specified
(NR)
- $6 - Linkage
(NR)
See Control Subfields
- $8 - Field link and sequence number
(NR)
See Control Subfields
Example
856 |
7#$uhttp://minaret.loc.gov/images/gschedule/G1350a.gif$yMap of West south central states |
Go to top of document
The full content-designated representation, in a different script, of another field in the same record. Field 880 is linked to the associated regular field by subfield
$6 (Linkage). A subfield $6 in the associated field also links that field to the 880 field. When
an associated field does not exist in the record, field 880 is constructed as if it did and a
reserved occurrence number (00) is used to indicate the special situation. The data in field 880
may be in more than one script.
Indicators
- First - Same as associated
field
- Second - Same as associated
field
Subfield Codes
- $6 - Linkage
(NR)
See Control Subfields
- $a-z - Same as associated
field
- $0-5 - Same as associated
field
- $7-9 - Same as associated
field
Examples
880 |
##$6680-02/N$i[Explanatory text in Cyrillic script] |
880 |
##$6153-01/(B$aHA1$cHA4737$jStatistics |
Go to top of document
Go to:
MARC 21 Concise Classification Format |
MARC Home Page
Library of Congress
Library of Congress Help Desk (
12/19/2006
)