Jump to Content
September 20, 2014
 
 
 
 
 

SCP 599 Fields

[NOTE: The information contained in this document was removed from the UCSD Composite record cataloging (serials) guidelines]

OVERVIEW

The Shared Cataloging Program (SCP) utilizes the 599 local note field to earmark CDL records for distribution to the UC campuses. Records with 599 fields are gathered from the Millennium outrecs file every Monday (or Tuesday following a Monday holiday).

GENERAL RULES FOR USE

Use only one 599 field per record at a time. If you need to add a 599 field to a record that already has one, add to the existing 599 field if it is dated for the current week (Monday-Friday). If the 599 field is dated for the previous week, wait until the previous 599 field has been deleted. If the 599s have not been deleted, contact Kate Garvey-Clasby or Karen Peters. Since SCP updates are sent once a week, if you add a 599 field to a record that already has one from the previous week, it might get deleted along with the old one.

599 construction:

599 __ $a [UPD, NEW, or DEL] $b [type of resource other than eserial or emonograph: DB, cadocs] $b [actions taken, in alphabetical order] $c [yymmdd]

$a : Indicate the type of update: NEW, UPD and DEL.

$b (type of resource): If the resource is a database (integrating resource) or California document, add $b DB or $b cadocs after the $a NEW, UPD, or DEL for all 599 notes. If the title is both a database and California document, use $bcadocs DB.

$b (actions taken): List actions taken. Use a semi-colon to separate different actions (see types of 599 fields below).

$c : Enter today's date [yymmdd]

 

Types of 599 FIELDS
DEL $c 090526 DELETED ESERIAL OR EMONOGRAPH TITLE (includes deleting a record that has been replaced by a different/new OCLC record for the same title)
DEL $b cadocs $c 090526 DELETED CALDOCS TITLE
DEL $b cadocs DB $c 090526 DELETED CALDOCS DATABASE TITLE
DEL $b DB $c 090526  DELETED DATABASE TITLE
DEL $b duplicate $c 090526  DELETED DUPLICATE RECORD (e.g., same OCLC record got cloned and distributed twice)
NEW $c 090526  NEW ESERIAL OR EMONOGRAPH TITLE (includes replacing a previously deleted record with a different/new OCLC record for the same title)
NEW $b cadocs $c 090526  NEW CALDOCS (SERIAL OR MONO) TITLE
NEW $b cadocs DB $c 090526  NEW CALDOCS DATABASE TITLE
NEW $b DB $c 090526  NEW DB TITLE
UPD $b cat $c 090526 CATALOGING MAINTENANCE (exceptions: title changes and ceased titles)
UPD $b ceased $c 090526 CEASED TITLE
UPD $b cov $c 090526 COVERAGE UPDATE(S) (i.e., changes to 856 $3)
UPD $b del ev $c 090526 DELETED ELECTRONIC VERSION(S)
UPD $b scp $c 090526 SCP UPDATES (e.g., changes to 856 $u, $z and 793 fields)
UPD $b scp reclamation cleanup $c 100714 UPDATES RESULTING DIRECTLY FROM RECLAMATION CLEANUP
UPD $b tc $c 090526 TITLE CHANGE

EXAMPLES:

MULTIPLE ACTIONS (RECORD IN ALPHABETICAL ORDER):

UPD $b add ev; cov; del ev; TC $c 090526

UPD $b cadocs $b add ev; cov; TC $c 090526

REPLACING AN EXISTING CDL RECORD WITH A CURRENT/CHANGED COPY OF THE SAME OCLC RECORD:

UPD $b cat $c 090526

WHEN CAMPUS PARTICIPANTS ARE ADDED OR DROPPED FROM TIER 1 or Tier 2 LICENSES (one 856 field in the record):

UPD $b scp $c 091112

After updating the 856 $z and adding the 599, don't forget to add and/or delete appropriate 920 fields associated with the 856 $z change.

If campuses are being dropped from the license, they will not be receiving an update. Therefore, also notify the SCP AC liaisons that the license has changed so that affected campuses can identify and remove records as appropriate.

WHEN CAMPUS PARTICIPANTS ARE ADDED OR DROPPED FROM TIER 1 or Tier 2 LICENSES (multiple 856 fields in the record):

UPD $b scp $c 091112

After updating the 856 $z and adding the 599, don't forget to add and/or delete appropriate 920 fields associated with the 856 $z change.

If at least one of the 856 fields corresponds with a Tier 1 access point, retain all ten 920 fields. All campuses will receive an update of the record.

REPLACING AN EXISTING CDL RECORD WITH A DIFFERENT OCLC RECORD

From time to time, we may need to replace an existing CDL record with a different OCLC record for the same title. Because some campuses overlay their records by matching on OCLC numbers, we need to be diligent about not replacing or overlaying existing SCP records with different OCLC records. Local UCSD NET records, however, can be overlaid with different OCLC records for the same title (see circumstances below) because it does not affect Melvyl merging algorithms which match on fields other than OCLC number.

For SCP records, use the following 599s when:

1. Upon subsequent updates to a serial title, you discover that the single print record is now available for a title that was initially cataloged using the separate electronic record.

2. Ejournals: You are replacing a latest entry/non-PCC catalog record with a successive entry/PCC catalog record.

3. Emonographs: You are replacing a non-PCC with a PCC catalog record.

Separate-/latest entry-/non-PCC record: 599 DEL $c 070123

Single-/successive entry-/PCC record: 599 NEW $c 070123

Back to top

Last updated: May 13, 2013
Document owner: Adolfo Tarango