This document summarizes treatment of field 856 in ORBIS records for tangible resources. A tangible resource is a printed text, a graphic print, a DVD, a microform, a CD-ROM, etc. The policies and procedures are not intended to be applied to records for web resources, such as electronic reserves.
The rationale for the policy is that:
*Effectively, any remote electronic resource for which Yale controls the administrative rights, e.g. an electronic image digitized from a tangible resource owned by Yale. In contrast, Yale does not control ("own") the administrative rights to government documents, free websites on the Internet, or to remote electronic serials leased from a vendor.
Basic guidelines for new cataloging:
Basic guidelines for maintenance:
Copy catalogers are not expected to evaluate an 856 link in cataloging copy. Any maintenance will be performed retroactively.
EXCEPTION: Copy catalogers should remove 856 fields from cataloging copy for serials at the time of cataloging.
EXAMPLES. NOTE: examples are from the OPAC and are to be considered illustrative. The Orbis number can be used to retrieve and view the record in the Staff Cataloging Module.
Library of Congress records with detailed tables of contents available through remote links.
Current accepted practices are listed. As a standard procedure, always check any URL added to the record in the OPAC or by using the Voyager link checker (ctrl+k).
Recommendations:
i. Units should document their procedures, including
As these become available, a link will be provided from this document.
ii. Use 856 in the MFHD to link to an online resource related to the print resource represented by the bibliographic record.
Use the following standard construction for 856 fields (in either bibliographic or MFHD records). Second indicator 2 means the link is to a "related resource."
856 42 ‡3 <specific material described, if applicable, e.g. Finding aid; Online guide > ‡u <URL> ‡z <public note, if applicable>
Avoid entering only a ‡u in 856, since this will cause the URL path to display. Use of both ‡3 and ‡z is allowed, but both will display in Orbis as currently configured.
iii. Use 856 in the MFHD if a link is made from a tangible resource to a digital surrogate.
Use the following standard construction for 856 fields (in either bibliographic or MFHD records). Second indicator 1 ("version of the resource") means the link is to a digital surrogate.
856 41 ‡y Digital version. ‡u <URL>
The hotlinked Orbis numbers connect to the record in the OPAC. From the OPAC, click on the appropriate hotlink to open the remote electronic resource. Examples are from the OPAC and are to be considered illustrative of the categories where linking is acceptable for new cataloging. However, they may not represent current best practice for 856 formatting (see standard construction in section iv. above). Examining some of the records in the OPAC that do not follow standard practice may shed light on why the standard has been recommended. The ORBIS number can be used to retrieve and view the record in the Staff Cataloging Module, e.g. if it is unclear whether the link is in the bibliographic record or the MFHD.
1. Link to online finding aid for an archival collection held by Yale.
EXAMPLE: ORBIS # 3976998 [6] Leo Stein collection [Click on the Finding Aid link on the OPAC record to view the linked finding aid to the collection represented by the catalog record]
2. Link from a record for a tangible resource owned by Yale to a remote digital resource owned by Yale.
Batch-loading decisions are case by case. Not every decision will be listed here.
Links on GPO records. Current GPO practice is to use an 856 $u http://purl.access.gpo.gov [12] link to open a PDF copy of the document represented by the catalog record. In this case, the loader program should not strip links from the bibliographic records even though some links may not be live.
ORBIS # 7148544 [13] Starving terrorists of money : the role of Middle Eastern financial institutions ...
ORBIS # 7220081 [14] H.R. 1999--The State and Local Housing Flexibility Act of 2005 ...
In Voyager, the 856 field can be used to create a hotlink from one bibliographic record to another using the following path:
The URL should be entered in a separate 856 field in this form:
856 42 ‡u http://hdl.handle.net/10079/bibid/<bibid [15] of target record>‡z <public note>
CAUTION: Do not use orbstaff.library.yale.edu in the URL; this will cause the linked record to open in a staff session with an extended time-out.
1. If a classed together analyzed series (serial or multipart) has an unanalyzable title, the item records are relinked from the analytics to the cover record. At that time, the unit doing the relinking has the option to link the analytic record to the cover record through an 856 linking field. Catalog Management will add 856 links to analytic record MFHDs if there is a request from Public Services.
EXAMPLE: Orbis # 6306476 [16] Jinsei seibutsugaku sei kagaku. Clicking on the link will send the user to the cover record (Orbis # 6313521) where the item records live and where the circulation status will display.
856 42 ‡u http://hdl.handle.net/10079/bibid/6313521 [17] ‡z Click here for circulation status or to request this title (v. 1 of the series: Yamamoto Senji zenshū.)
2. If a bound with set (particularly one involving serial issues or multipart volumes) requires a separate MFHD or complex note to explain the record relationship, the cataloger and/or Catalog Management have the option to use an 856 MFHD link instead of the Voyager 014 bound with item record link to show the relationship between the records.
EXAMPLE: Orbis # 2346024 [18] Athenaeum and literary chronicle. All issues of the title are actually bound with the last volume of Athenaeum (London, England : 1828). Clicking on the link sends the user to the 1828 Athenaeum record (Orbis # 2410420).
856 42 ‡u http://hdl.handle.net/10079/bibid/2410420 [19] ‡z Click here for circulation status or to request no.41(1828:Aug.)-no.62(1828:Dec.) [bound with no.37(1828:July)-no.40(1828:July) of "The Athenaeum"]
Document created by: Mathew Beacom
Created date: 07/03/2007
Revised date: 03/02/2011
Links
[1] http://web.library.yale.edu/cataloging/editing/856-edit-copy
[2] http://hdl.handle.net/10079/bibid/4559773
[3] http://hdl.handle.net/10079/bibid/7145140
[4] http://hdl.handle.net/10079/bibid/7725886
[5] https://web.library.yale.edu/cataloging/standard-terms-use-856
[6] http://hdl.handle.net/10079/bibid/3976998
[7] http://hdl.handle.net/10079/bibid/7784975
[8] http://hdl.handle.net/10079/bibid/7472703
[9] http://hdl.handle.net/10079/bibid/1186609
[10] http://hdl.handle.net/10079/bibid/7760463
[11] http://hdl.handle.net/10079/bibid/6995910
[12] http://purl.access.gpo.gov
[13] http://hdl.handle.net/10079/bibid/7148544
[14] http://hdl.handle.net/10079/bibid/7220081
[15] http://hdl.handle.net/10079/bibid/<bibid
[16] http://hdl.handle.net/10079/bibid/6306476
[17] http://hdl.handle.net/10079/bibid/6313521
[18] http://hdl.handle.net/10079/bibid/2346024
[19] http://hdl.handle.net/10079/bibid/2410420
[20] https://web.library.yale.edu/cataloging/bound-procedures-serials-multiparts
[21] https://web.library.yale.edu/cataloging/linking-text-subfields-856