CATALOGING PROCEDURES FOR NETWORKED ELECTRONIC RESOURCES


Back to TSmanual | Back to Procedures Contents

Field-by-Field Instructions

General considerations

- PCC standards for Internet resources are not available at this time. The MARC fields 245 to 975 below are required if applicable for CUL.

- Follow the guidelines in "Cataloging Internet Resources: A Manual and Practical Guide," 2d ed., edited by Nancy B. Olson, available electronically at http://www.purl.org/oclc/cataloging-internet.

- For serials, follow the rules and practices in the CONSER Cataloging Manual: Module 31, Remote Access Computer File Serials (a few exceptions are noted). http://lcweb.loc.gov/acq/conser/module31.html

- CONSER does not catalog the following as serials: 1) Online public access catalogs or databases; 2) Gopher servers; 3) Discussion lists or their digests; 5) WWW home pages without designated parts; 5) Online services such as America Online. [NOTE 12/1/97: CONSER is reconsidering item 1) above. Databases which in their print manifestations are cataloged as serials will probably be cataloged as serials in their electronic manifestations.]

Procedures

1XX: 130
2XX: 245, 246, 250, 260
3XX: 300, 310, 362
5XX: 500, 505, 506, 516, 520, 530, 538, 556
6XX: 653
7XX: 710, 740
8XX: 856, 899
9XX: 975

Copy Holdings, Trial subscriptions, Item Records, MHLD records

Use the computer file format (RT=m) if the content of the record is primarily computer software, numeric data, computer-oriented multimedia, or online systems or services. However, for these classes of materials, if there is a significant aspect that causes it to fall into another Leader/06 category, code for that significant aspect instead (e.g. vector data that is cartographic is not coded as numeric but as cartographic). Other classes of electronic resources are coded for their most significant aspect (e.g. language material, graphic, cartographic material, sound, music, moving image). In case of doubt or if the most significant aspect cannot be determined, consider the item a computer file.

In any case, follow the USMARC Bibliographic Cataloging Manual guidelines for the use of 006, 007 and 008 fields. In the 007 field, GMD should be "c" for computer file and SMD should always be "r" if the material is networked. Other fields should be used when and how appropriate.

007 GMD c SMD r O/R ? COLOR g DIM n SOUND


130 - Uniform titles. When a uniform title is needed to distinguish an online version of a serial from its print version, the qualifier "Online" may be used. Uniform titles are not given for reproductions.

130 Migration news (Davis, Calif.)
130 Migration news (Davis, Calif. : Online)

245 - Title. For non-serials, follow the guidelines in Olson's "Cataloging Internet Resources: A Manual and Practical Guide" to determine the chief source of information:

a) title screen either online or on printout,
b) information from the file itself,
c) online documentation,
d) title from "home page" or menu choice,
e) published description,
f) file name, or
g) cataloger supplied title.
Chief source for title for serials. The rule for printed serials (AACR2 12.0B1) identifies the chief source as the title page, or title page substitute, in the first available issue, while the rule for nonprint serials (AACR2 12.0B2) directs catalogers to the chapter for the physical format. Catalogers continue to look to the first issue for bibliographic information in online serials and AACR2 9.0B1 establishes the "title screen" as the chief source for computer files (see also 31.4.2). When cataloging online serials, catalogers should also consider common sources for bibliographic information: journal home page, "publisher's statement" page, volume contents page, current issue contents page, etc. The first issue may provide us with the best benchmark for basing the description but electronic serials often necessitate a description of the entire publication that is available at the time of cataloging.

For a remote access serial distributed via email, with no title screen or title statements found anywhere in the file, use the statement found in the subject line of the header information as a formal title statement. Use a file name, menu listing, or home page presentation for the title, as found in an FTP site, or Web or gopher server, if no formal title statement appears anywhere in the text. Other situations may require the cataloger to supply a title within brackets per AACR2 9.0B1 and 9.7B4.

GMD. Use [computer file].

Statement of responsibility. Give in |c only if a formal statement is given on the chief source of information. Don't try to create one if it isn't there.

246 - Variant titles. Any variation in the form of the title pertaining to the entire work is entered in this field. For example, use 246 if the title displayed in the title bar differs from the title chosen as main entry, or if a prominent title on the help screen differs. Use |i to explain where the varying title comes from.

246: 1 : |i Title on title bar: |a ABCD
246: 1 : |i Title on help screen: |a ABCDE

Remote access serials may contain variant titles on the title screen or in other locations in the file. Such variants could include "at head of title" phrases, running titles, or abbreviated titles in header information or at the end of the file. File or directory names may constitute other legitimate variant titles if it may be reasonably assumed that a user would search for the serial using those names. The title bar in the Web browser displays the HTML document title as coded in the document source. Such a title can be recorded as a title variant or can confirm as the title proper one that is not clearly presented in the publication.

245 00 Effector online |h [computer file]
246 1 |i File name: |a EFFON

250 - Edition statement. Any change in intellectual content, programming language or operating system, or change to make the file run more efficiently, constitutes a new edition. See Olson, 2nd ed., p. 13 for examples.

260 - Publication, distribution, etc. Publisher and date are sometimes difficult to find and establish, especially if the target item is issued by an individual. Use the corporate entities or de facto authors and editors listed as responsible for the content. Avoid using the "webmaster" listed on the site since in most cases this is the person responsible for the technical maintenance of the site rather than its content.

Treat all electronic serials as "published" material. If the serial lacks a formal publication statement, but internal or external evidence indicates that it emanates from an institution or organization, consider the institution or organization the publisher and the location of the institution or organization to be the place of publication.

300 - Physical description. Do not include a 300 field for any remote access files. Sound, graphics, or other characteristics can be mentioned in a note and field 007.

310 - Frequency. Consider indications of the frequency of updates to a site to be the frequency of publication.

362 - Designation. When cataloging an online version or reproduction of a printed serial, prefer a "description based on" note if the online version does not begin with the first issue of the printed version. However, provide a note (362 1) to indicate the coverage of the digitized serial at the time of cataloging (LCRI 12.7B8).

362 1 Coverage as of July 16, 1997: Vol. 30, no. 1 (May 1983)-
5XX - Notes. Olson specifies that notes are to be included in the order of the rules themselves. The notes area for electronic serials includes information appropriate both to the serial and to the computer file aspects of the publication. Take into account instructions for notes given in both Chapters 9 and 12 of AARC2. Input notes in numeric tag order. [LGTS Committee decided 10/10/97 to recommend that the order of notes in the OPAC display should not be dependent on the order in which the notes are in the MARC record.]

538 - System requirements. For remote access files, this note identifies a specific program or type of program needed for use with the file, or special hardware requirements.

538 System requirements: Adobe Acrobat Reader software, or a PostScript viewer or PostScript printer.
538 - Mode of access. Mode of access (field 538). A "mode of access" note (field 538) must be given in all records for remote access materials to explain the means by which the they can be accessed (AACR2 9.7B1). If more than one issue of a serial is available, consult the latest issue for this information.

For consistency in CONSER records, begin with the phrase, "Mode of access:". If both a "mode of access" and a "system requirements" note are given, the "system requirements" note should be input first.

538 Mode of access: World Wide Web.
538 Mode of access: Internet email and World Wide Web. For online subscription, mail to listserv@mitvma.mit.edu, with message: subscribe mini-air [firstname lastname]
500 - Source of title proper. For any computer file, the source of title must be specified.

500 Title from home page.
500 Title from TEI header.
500 Title supplied by cataloger.

In addition, Description based on notes are required for serials. This may be combined with notes as to the source of the title proper. If cataloging from a printout as opposed to the online file itself, note that as well.

500 Description based on printout: July 1994; title from title screen.
500 Description based on: Vol. 2, no. 2 (Apr. 1995); title from caption.

Cataloger may add a 500 note describing other means of access to the target item, if readily available from examination of the item.

506 - Restrictions on access. When a publication is not freely available, and the electronic location is given in field 856, the restriction is noted in a 506. Because the bibliographic record, the basis for shared cataloging, should reflect primarily information applying to the title as a whole, only non-Cornell specific information will be recorded in a 506.

506 Access limited to licensed institutions.
506 Restricted to institutions with a print subscription and a site/user ID and password
516 - Type of computer file or data. This field "contains information that characterizes the computer file." Olson, 2nd ed., p. 17-18.

516 Text.
516 Available in ASCII, Acrobat, and PostScript file formats.
556 - Documentation. Make notes about documentation that can be accessed along with the electronic resource.

556 8 User's guide available online via Internet email and FTP access.

530 - Other physical formats. If the site comprises the online version of a print title, for example, or the material is also available on CD-ROM, that fact would be mentioned here.

530 Online version of print publication.
530 Also published in a print version.
530 Electronic version of: LITA newsletter. [776 field used]
530 Later issues available on the World Wide Web.

520 - Summary. According to Olson, "This note provides a brief, objective summary of the purpose and content of the item, if needed." 2nd ed., p. 25. The content of the note may be derived from online resource's introductory information or composed by cataloger (in consultation with the selector, if necessary) and must contain key words that identify the resources's use and purpose. It may be phrases, or complete sentences.

505 - Formal contents note. If a file breaks down into parts that can be listed formally, this note may be used to list them. Informal contents notes, which might begin Contains ... or Includes ..., would be coded as 500s.

653 - Library Gateway Subject captions (MARC format "Index term--Uncontrolled").

7XX - Added entries. Trace persons or corporate bodies listed in the 245 |c which are not used as main entry, and those listed in the 260. If considered important, persons or corporate bodies mentioned in notes may be traced at the discretion of the cataloger.

710 - Corporate added entry. Generally, trace producers/distributors even if they are not responsible for the content of the item.

740:02: - Added entry uncontrolled related/analytical title. Use if site contains discrete sub-items with titles within it, mentioned in a 505 contents note.
856 - Electronic location and access. Check the URL to be sure it is correct. Subfield "u" contains the URL for the target item. Some characters (underline "_" and tilde "~") found in URLs cannot be input in NOTIS records. Instead, use the ASCII hexadecimal equivalent. When cataloging titles that are available through aggregators (e.g. JSTOR and Project MUSE titles), make the link to the specific title, if possible, not to the aggregator site. If the URL you are given does not match the URL of the specific title you are asked to catalog, check with the selector to make sure the URL is correct and that the title requested is indeed what needs to be cataloged. [Note: in some cases it will be impossible to script to specific titles and linking to the aggregator site may be your only option.]

The |z is standardized and should be included in each 856 for which a corresponding Gateway record is created. The standard note reads: "Internet resource file; accessible through Library Gateway."

If only recent issues of a serial are available and not the whole run, use 856 |3 to show this information. If multiple 856 fields are required, this information may vary from field to field.

EXAMPLES:

856:40: |u http://www.ncts.navy.mil/navpalib/news/navnews |z Internet resource file; accessible through Library Gateway.
856:2 : |u telnet://flora.mannlib.cornell.edu:31424 |z Internet resource file; accessible through Library Gateway
856:41: |u http://abc.xyz.net/%7Edef/folder%5FA/ |z Internet resource file; accessible through Library Gateway.
856:40: |3 Back issues |u http:// ... |z Internet resource file; accessible through Library Gateway. |2 http
856:40: |3 Recent issues |u http:// ... |z Internet resource file; accessible through Library Gateway. |2 http

Library of Congress 856 guidelines are available at http://lcweb.loc.gov/marc/856guide.html

899 - Special use codes for Project MUSE, JSTOR titles, and other collections.

975 - Genre.


Copy holdings. Use subfield k ONLINE before the call number. The call number (class number only if the LC cutter table is not used for the book number) is also transcribed into an 050: 4: on the BIB record, if an 050 is not already present. 090 fields already on the record should be retagged as an 050: 4:.

001 1L CN |a serv,remo |k ONLINE |b HF5429 |c .U542a

Trial subscriptions. Include the copy-specific note, "um=Trial subscription" for titles received on this basis. Remove the note if CUL decides to retain the item at the end of the trial period.

Create an empty item record. This ensures that "Check shelf" doesn't appear in OPAC.


MARC holdings. Check the availability of serial issues. Is the entire run available or only current or recent issues? If an open-ended statement is to be used to describe the availability of the entire run, create a MARC holdings record with E/L 3 and 866 with a first indicator value of 3. If only current issues are available and the specific ones available are not going to be recorded, add an 852 |z note: Recent issues only. In this case, set the E/L to 4. Record "moving wall" limitations in an 866 |z field. If more than one interface is available for the SERV,REMO location, compress the multiple holdings into a single 866 statement whenever possible (it may not be possible if a moving wall for back issues is involved). Do create separate holdings statements in the individual Gateway records, however, to reflect exactly what's available at each respective site.

Note that the summary holdings statement in the Gateway record should reflect what is recorded in the NOTIS MHLD, except when multiple interfaces are involved.

EXAMPLES:

Entire run available.
866:31: |8 0 |a v.1 (1950)-
Recent issues only (no specific holdings recorded).
852:: |z Recent issues only.
Moving wall.
866:31: |8 0 |a v.1 (1950)- |z <Lacks current 5 years>
Compressed holdings (multiple interfaces).
866:31: |8 0 |a v.1-43,47 (1950-1992,1996)-
Non-Compressed holdings (multiple interfaces).
866:31: |8 0 |a v.1 (1988)- |z <Lacks current 5 years>
866:31: |8 0 |a v.9 (1996)-

If the networked resource is an added location to the print version of the serial, add the 007 describing the networked resource. For example:

SMD = r O/R = ? COLOR = u DIM = n SOUND = [blank]

Back to TSmanual | Back to Procedures Contents


rev. 1/15/99 dih