Access and Relationship Fields

ACCESS POINTS

130 Preferred Title (under AACR2 called Uniform Title): CCM 31.5

The 130 field is not used to differentiate the print from the online serial. If a qualifier was used for the print serial, use the same qualifier with the online serial. Do not use Online as a qualifier for a born-digital 130 if a qualifier is needed to differentiate titles proper.

RELATIONSHIP DESIGNATORS

Per PCC Relationship Designators in Bibliographic Records guidelines, assign a relationship designator subfield to the primary creator (formerly main entry) in 110 (‡e) or 111 (‡j) if there is one. The usual designator for a corporate body is "author." Multiple RDs can be assigned; in such cases, the primary RD is always first.

Example. Online resource:

LCSH

Use –Periodicals not  –Electronic journals as a form subdivision.

Print/Online Title Change Problems CCM 31.17.1

CONSER practice is to align print and online versions to the extent possible.

Case 1.  The online serial has the same content as the print version but the online serial has a different title. CONSER: create a new record for the online serial, but use the print title in 245 and the online title in 246 1 (former practice was to use 247), and make a 588 description based on the print version.

Case 2. In many cases, vendors use the opportunity of digitizing the serial back issues to eliminate title changes. If a serial in printed form changes from Title A to Title B, the vendor may change the title on the Title A backfile issues to Title B when the serial is digitized, so all issues of the serial in electronic form will have Title B. CONSER: create successive records for the e-serials for Title A and Title B, with the 245s based on the 245s of the successive print serial records, even though Title A no longer appears on the e-serial.

Case 3. Title A of a born-digital serial changes to title B; title B incorporates all of the content of Title A with ongoing new issues. Close (do not delete or suppress) the record for title A. Add a note (All issues originally published with the title: A have been reformatted and issued under the later title: B. Make a 785 linking field to the title B record. Make a new record for Title B. Add the same note used on the earlier record. Make a 780 linking field to the title A record.

Note that in Cases 2.-3., the 856 URLs for records A & B will point to the same website.

Linking Relationships CCM 31.15

Use 776 to link from the online resource record to the print record, and vice versa, even if the print version ceased and was continued by the online version.

Example for the online version from CCM 31.15, showing link to the print version.

If there is both a print and online version, and a title change occurs, use 780/785 for the title change and 776 to link print to online and vice versa.

Example from CSM 31.15. The earlier title of the online version with a link to the print version. The example has been modified: in 785, the CONSER manual included a ‡e after ‡a, but ‡e should not be used with author/title combinations, per

The later title of the online version. The print version has ceased at this point, so no 776 field is made. Note that the 780 fields have the same title but different ‡w's representing the OCLC ID numbers for the records for the earlier print and online titles. As indicated in the ACCESS POINTS section, the preferred title of the print and online versions should not use a qualifier to differentiate between the two formats.

See CCM 31.15 for the reciprocal records for the print versions.

Linking Field 856 CCM 31.14

The CONSER workflow assumes the cataloger creates a master record in OCLC and then downloads a copy to the local ILS. The cataloger then edits out 856 URIs that are not authorized for the Yale community and adds 856 URIs that are authorized. Under CONSER, catalogers cannot include 856 links that prevent users from outside the cataloger's institution from accessing the serial. This is not possible with YUL workflows where catalog records are created in Orbis. YUL catalogers should enter 856 fields authorized for Yale even though they cannot be accessed by non-Yale IP addresses.

For YUL catalogers who work directly in OCLC, any link to a serial limited to the Yale community should be entered only in the YUL institution record.

If a serial cannot be accessed without an institutional license, CONSER practice is to create a link to the aggregator site or sites that function as portals to the serial for licensed institutions.  To avoid confusing our users locally, if YUL has not purchased access to an online serial, a link to the aggregator portal or portals  should not be added to the YUL bibliographic record. However, if YUL has an institutional license but journal titles can only be accessed via the provider portal, the cataloger may catalog the portal website as an integrating resource (updating website) and provide an 856 link to the website. In addition, if requested by public services, the cataloger may provide selected added entries for the portal record for individual journal titles. See General Website Cataloging Policies & Procedures.

CONSER indicator practice for 856 is the same as YUL's. See Linking Text Subfields in 856.

CONSER practice also differs to some degree for choice of subfields used in 856. CONSER practice is to use subfields u, 3, and z. CONSER uses ‡u for the URI, ‡3 for "information that specifies the part of the bibliographic item to which the field applies, when there is not a fully one-to-one relationship between the 856 and the resource described in the record," and ‡z for public notes such as access restrictions or subscription information.

YUL practice is the same as CONSER's for ‡3 and ‡u. However, YUL uses ‡y for all public notes and limits notes to the category of material documented in Standard Terms for Use in 856 ‡y or ‡3. CONSER expects the URI to display; the Orbis OPAC display for 856 only displays ‡y, but the text of the note is hotlinked via ‡u to the online resource. See Linking Text Subfields in 856.