When GPO first began cataloging remote serials and monographs in 1993, our cataloging of remote files was limited to the Federal Bulletin Board and our cataloging instructions for remote files were less than one page long.

In 1995, we began to consult CONSER Cataloging Manual, Module 31, when cataloging remote serials. Then in early 1996, GPO expanded its cataloging of remote files and we began to develop additional GPO guidelines for them. From the beginning, these guidelines have been consistent with national standards, particularly CONSER standards.

When cataloging remote serials, we follow the special instructions in the GPO Cataloging Guidelines that were designed to reduce the time needed to catalog remote files.

The physical form and remote file records GPO creates using the single record approach are, with a couple of exceptions, the same as they would be if we created separate records and linked them only with linking note fields.

The special GPO standards for remote serials are as follows:

Another thing that GPO does differently when cataloging serials is to create individual availability records for specific issues. GPO does not create these for periodicals.

Now let’s turn to some examples of serial cataloging records that appear in the Monthly Catalog.

The first serial example is a "remote file record" which we recently created for the online version of the Commerce Business Daily. It has the same special "remote file" fields that Wil and Eileen pointed out in their examples. In addition, it contains special serial fields and it was created following special serial cataloging practices.

Fields of note are:

• The 010 field, which has a CONSER authentication number that was added by the GPO cataloger.

• Next, the 130 "main entry-uniform title" field. At the end of this field, we see a qualifier, which begins with the word "Online."

• Note the absence of a 300 field.

• Further down is a 310 field, with the frequency, which is daily.
• We have a 520 "summary" note, which can be included in full-level remote file records.

• There is 538 "mode of access" note.

• A 580 "linking field complexity" note, with information on the paper version.

• And a 787 "nonspecific relationship entry" field, linking this record to the catalog record for the paper.

The second example is an availability record for the quadrennial serial that is known as the Plum Book, but actually has the title: United States Government Policy and Supporting Positions. Here, we have used a physical form record to provide information on the paper and online versions of this publication. As mentioned earlier, this does not mean we are cataloging both on the same record. Only the rules in AACR2, chapter 12, were followed when this record was updated to include information on the online version. Information on the online version is provided only in three fields. These are the 074 field, item number; 530 field, additional forms available note; and the 856 field, URL address.

• We have three 074 item number fields in this record since it is providing information on three different versions of this publication. The first is for the paper, the second for the microfiche, and the third for the online version.

• In the 300 field is the physical description for the paper.

• We have a 530 note, which begins with the words "Some issues...." This is GPO’s standard style for serials.

• Note that are no 776 linking entry fields since we have chosen to represent all versions (paper, microfiche, and online) in a single record.

• At the bottom, we have a 949 field with the initials AVR, which means this record is an availability record.

United States government policy and supporting positions /. 1960-. Quadrennial. United States. Y 4.G 74/7:P 75/6/996. GPO stock no.: 052-070-07076-5. [[1016-A]].

http://www.access.gpo.gov/plumbook/toc.html

While most of the time GPO uses the single record approach when cataloging remote files, there are special circumstances where we create separate records for the physical form and online versions.

The first circumstance is when there is a significant difference in the contents.

The second circumstance is when we discover that an existing physical form record is unsuitable for use to catalog the remote file version because of known or suspected bibliographic problems.

The third circumstance is when we catalog the remote file first and must create a remote file record because there are no existing physical form records on OCLC.

The fourth circumstance is when we catalog publications of major significance. In the final example, we have an instance where GPO has created separate records for the online and physical form versions of a publication. The record for the remote file version of the Analytical Perspectives part of the Budget of the United States Government and a comparable record for the paper version are good examples this circumstance.

In this record, the fields of note are:

• The 240 field with a uniform title which has the word "online" as a qualifier.

• There is 538 "mode of access" note.

This time we have included a 776 "linking entry" field, linking this record to the catalog record for the paper version, and a 787 "nonspecific relationship" field, linking this record to records for the other online budget publications and the CD-ROM. We did not include these kinds of fields in the previous example, because we chose the single record approach for that document.