OSUL historically has followed LC practice, and has implemented changes when they appear in LC documentation (e.g. Cataloging Service Bulletin, which is not as current as the LC homepage and email messages to the PCC list).
Therefore, effective today, OSUL will follow LC practice for original cataloging:
OLD: [topic] $x Periodicals (no need to update if used on copy)
NEW: [topic] $v Periodicals (use for original records)
Examples of other form subdivision include:
This policy document will be available on the Cataloging Dept. website:
catdoc.htm
OCLC will be updating its online documentation to reflect this change in LC
practice: http://www.oclc.org/oclc/bib/6.htm
Date: Mon, 15 Feb 1999 09:51:45 -0500 (EST)
To: Noelle Van Pulis
From: Ana Cristan <acri@loc.gov>
Subject: Implementation of $v subfield February 17, 1999 (fwd)
FYI to all PCC Participants:
This message was sent from CPSO to LC catalogers. Please be aware that LC is moving forward with implementation of subfield v as announced on the CPSO homepage. As noted in the announcement Lynn El-Hoshyas agreed that PCC participants may send questions on form subdivisions directly to CPSO.
Date: Thu, 11 Feb 1999 17:35:33 -0500
From: "Kay D Guiles" <kgui@loc.gov>
Team Leaders and Others Listed Below:
Lynn El-Hoshy, CPSO, has asked me to post the following announcement: Team Leaders and others listed below. Please forward to catalogers.
"Changes to the subject authority file and LC bibliographic files to support the implementation of subfield $v for form subdivisions and other data elements that are listed in the announcement 'Authority Data Elements Implementation' that is posted to the CPSO Web site will take place on Wednesday, February 17, 1999. On that date LC catalogers should begin to code subdivisions as $v when they function as forms in subject heading strings assigned to bibliographic records. General instructions on coding form subdivisions are in the Subject Cataloging Manual: Subject Headings H 1075 sec. 1. d. In addition, instructions on many specific subdivisions may be found in individual instruction sheets. The basic guideline is to code a form subdivision for the function that the subdivision performs in a subject heading string. Code a form subdivision as a $v when it represents what the item being cataloging is; code a form subdivision as an $x when it represents a form that the item is about. Over the next two weeks CPSO staff will be holding orientation sessions for catalogers in each division. Questions about form subdivisions may be sent to CPSO at cpso@loc.gov."
Kay Guiles
CPSO
Ana Cristan
Acting BIBCO Coordinator
Cooperative Cataloging
Regional and Cooperative Cat. Div.
Library of Congress, LM537
Washington, DC 20540-4382
(202) 707-7921 (fax): (202) 707-2824
e-mail: acri@loc.gov