856 - Electronic Location and Access (R)
MARC 21 Authority - Concise
2007
Information needed to locate and access electronic information. The field may be used in
an authority record to provide supplementary information available electronically about
the entity for which the record was created.
Field 856 is repeated when the location data elements vary (the URL in subfield
$u or subfields $a, $b, $d, when used). It
is also repeated when more than one access method is used, mirror sites are recorded,
different formats/resolutions with different URLs are indicated, and related items are
recorded.
See the Guidelines for the Use of Field
856 for a more thorough discussion on the use of field 856.
Indicators
First - Access methodValue that defines the access method to the electronic resource. If the resource
is available by more than one access method, the field is repeated with data
appropriate to each method. When recording a URL in subfield $u, the
value corresponds to the access method (URL scheme), which is also the first
element in the URL string.
# - No information provided
0 - Email
1 - FTP
2 - Remote login (Telnet)
3 - Dial-up
4 - HTTP
7 - Method specified in subfield $2
Second - RelationshipRelationship between the electronic resource at the location identified in field
856 and the entity described in the record.
# - No information provided
0 - Resource
1 - Version of resource
2 - Related resource
8 - No display constant generated
Do not apply these indicator values to authority records.
Subfield Codes
$a - Host name (R)
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)
Access number associated with a host. It can contain the Internet Protocol (IP)
numeric address if the item is an Internet resource, or a telephone number if
dial-up access is provided through a telephone line. This data may change
frequently and may be 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)
Username, or processor of the request; generally the data which precedes the
at sign (@) in the host address.
$i - Instruction (R)
Instruction or command 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. 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)
Conventional name of the location of the host in subfield $a, including
its physical (geographic) location.
$o - Operating system (NR)
$p - Port (NR)
Portion of the address that identifies a process or service in the host.
$q - Electronic format type (NR)
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)
Uniform Resource Identifier (URI), which provides standard syntax for locating an
object using existing Internet protocols or by resolution of a URN. 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. 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)
Link text is 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)
$3 - Materials specified (NR)
$8 - Field link and sequence number (R)
Examples
|
|
|
|
|
|
|
|
|
|
| 856 |
4#$uhttp://plato.stanford.edu/entries/russell/russell.jpeg$yphotograph
|
|
|
|
|
|
|
|
|
|
|
| 856 |
4#$uhttp://www.ibiblio.org/wm/paint/auth/vinci/joconde/$ydescription
|
| 856 |
4#$3image$uhttp://www.ibiblio.org/wm/paint/auth/vinci/joconde/joconde.jpg
|
|
|
|
|
|
|
|
|
|
|
| 856 |
4#$uhttp://www.loc.gov/copyright
|
|
|
|
|
|
|
|
|
|
|
| 856 |
4#$uhttp://www.collectionscanada.ca/jsc/
|
|
|
|
|
|
|
|
|
|
|
| 856 |
4#$uhttp://www.firstladies.org/
|