OCLC-MARC Format Update 2002
The OCLC-MARC format changes announced in Technical Bulletin 247 "OCLC-MARC
Format Update 2002" (<http://www.oclc.org/technicalbulletins/247/>) are
effective December 1, 2002.  In addition to the bibliographic format changes
and the newly defined codes, users should follow the new practices for
coding field 041 (Language Code) and for cataloging integrating resources
that are outlined in TB 247.  Here are a few highlights of the 2002 Update.
Please see Technical Bulletin 247 for additional details.
DVD code "v" for 007 subfield $e
A new code "v" specifically for DVD format videorecordings has been defined
for the Videorecording 007 field subfield $e.  The existing value "g" has
been redefined more narrowly and should no longer be used for DVDs.
Form code "s" for Sound Recordings
Form of Item code "s" (electronic) is now valid for the Sound Recordings
fixed field (REC 008/23) and the Sound Recordings 006/06.
Field 041 Coding
Every subfield in the Language Code field 041 is now repeatable.  OCLC users
should cease the practice of placing multiple language codes in one subfield
and begin using the single code per repeatable subfield practice.
Integrating Resources
According to AACR2, 2002 revision, an integrating resource is:  "A
bibliographic resource that is added to or changed by means of updates that
do not remain discrete and are integrated into the whole.  Integrating
resources can be finite or continuing.  Examples of integrating resources
include updating loose-leafs and updating Web sites."

Starting on 2002 December 1 and continuing until the future full
implementation of Bibliographic Level code "i", follow these guidelines for
integrating resources:

--Continue to use Bibliographic Level code "m" (Monograph) when coding a
record for an integrating resource.  Do not use code "s" (Serial) for an
integrating resource.

--Add a serial 006 field to records you input or replace for integrating
resources.  OCLC will likely use data included in the serial 006 field to
formulate fixed-field elements in a future conversion of integrating
resource records from BLvl code "m" to code "i" following implementation of
Phase 2.

--In the serial field 006
<http://www.oclc.org/bibformats/en/fixedfield/006.shtm>, use code "k" in
Frequency (Freq <http://www.oclc.org/bibformats/en/fixedfield/freq.shtm>),
when appropriate, to indicate that an integrating resource is continuously
updated.

--In the serial field 006
<http://www.oclc.org/bibformats/en/fixedfield/006.shtm>, use codes "d," "l"
and "w" in Type of Continuing Resource (SrTp
<http://www.oclc.org/bibformats/en/fixedfield/srtp.shtm>, formerly Type of
Serial), when appropriate, to indicate that an integrating resource is an
updating database, updating loose-leaf, or updating Web site.

--In the serial field 006
<http://www.oclc.org/bibformats/en/fixedfield/006.shtm>, use code "2" in
Entry Convention (S/L
<http://www.oclc.org/bibformats/en/fixedfield/succ.shtm>, formerly
Successive/Latest Entry) to indicate that the record was formulated using
the revised rules for integrated entry.

OCLC has changed online data validation rules on a number of other existing
fields that had previously been used almost exclusively in serials
cataloging.  The change permits these fields to be used in records for
integrating resources during the interim period.  These include fields 022,
222, 247, 310, 321, 362 and 547.
URIs and LCRIs 9.7B and 21.3B for Remote Access Electronic Resources
Two Library of Congress Rule Interpretations, 9.7B and 21.3B, offer some
guidance about how to deal with remote access electronic resources based on
the new more serial-like treatment of integrating resources and the
disposition of the resource's Uniform Resource Identifier (URI).  When the
original URI is no longer accessible, but the resource (or a new iteration
thereof) is now accessible at another URI, you may edit the existing record
to reflect this.  When the original URI is still active but now represents
an entirely different resource, rather than a new iteration of the original
resource, you may create a new record for the new electronic resource.  In
cases where you are unable to edit, or prefer not to edit the existing
record, you are encouraged to report the necessary changes to OCLC.

Additional details regarding the treatment of integrating resources are
available in a newly revised version of "Cataloging Electronic Resources:
OCLC-MARC Coding Guidelines"
(<http://www.oclc.org/connexion/documentation/type.htm>).

This announcement has been distributed to several lists; please excuse any
duplication.

Jay Weitz
OCLC WorldCat Content Management Division