Skip to main content

SCP 599 Fields

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

Revised July 2019 by SCP

Approved July 2019 with minor changes by SCP-AC

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

Use only one 599 field per record at a time. If needing 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. Since SCP updates are sent once a week, if adding 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] $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), add $b DB after the $a NEW, UPD, or DEL for all 599 notes.

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

$c: Enter today’s date [yymmdd]

Types of 599 Fields

Field Description
DEL $c 090526 DELETED ESERIAL OR EMONOGRAPH TITLE (includes deleting a record that has been replaced by a different/new OCLC bib record for the same title)
DEL $b DB $c 090526 DELETED DATABASE TITLE
DEL $b rc $c 190417 REPLACEMENT COPY for the implementation of separate records for serials (e.g PRINT record being deleted and replaced by the online record, always paired with an online replacement record: NEW $b rc $c date)
NEW $c 090526 NEW ESERIAL OR EMONOGRAPH TITLE (includes replacement record for a previously deleted record with a different/new OCLC bib record for the same title)
NEW $b DB $c 090526 NEW DB TITLE
NEW $b rc $c 190417 REPLACEMENT COPY for the implementation of separate records for serials  (e.g ONLINE record being added to replace the print record, always paired with a print record to be deleted: DEL $b rc $c date)
UPD $b add ev $c 190417  ADDED ELECTRONIC VERSION(S)
UPD $b cat $c 090526 CATALOGING MAINTENANCE (e.g., changes to the OCLC bib record only).  For title changes and cessations, use “tc” and “ceased,” respectively.
UPD $b ceased $c 090526 CEASED TITLE (e.g., changes to the OCLC bib record as a result of cessation (no 785). If making additional changes to the record, apply other codes as needed such as “add ev”, “cov”, “del ev”, and/or “scp”.
UPD $b cov $c 090526 COVERAGE UPDATE(S) (e.g., changes to 856 $3, includes updates to the embargo length)
UPD $b del ev $c 090526 DELETED ELECTRONIC VERSION(S)
UPD $b scp $c 090526 SCP UPDATES (e.g., changes to local scp fields 793 and 856 $u, $x and $z).  
UPD $b tc $c 090526 TITLE CHANGE (e.g., changes to the OCLC bib record as a result of a title change (785 present). If making additional changes to the record, apply other codes as needed, such as “add ev”, “cov”, “del ev”, and/or “scp”.

Examples

MULTIPLE ACTIONS (RECORD IN ALPHABETICAL ORDER):

UPD $b add ev; cov; del ev; 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 updated record. Therefore, CDL Acquisitions or Electronic Resource Team (ERT) will 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 bib record for the same title. Because some campuses overlay their records by matching on OCLC numbers, do not replace/ overlay existing SCP records with different OCLC bib records.

During the implementation of separate records for serials, if replacing an existing CDL print record with a separate online record, use “rc” code above.

For SCP records, use the following 599s when:

Ejournals: You are replacing a minimal level record with a fuller or CONSER record, latest entry/non-PCC catalog record with a successive entry/PCC catalog record.

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

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

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

 

MERGED RECORDS:

When records have been merged (i.e. the OCLC number has changed and the number currently in the 001 in the SCP record is now in the 019 field), add a 599 note below:

For the record SCP is deleting:

599 DEL$c190419

For record with the new control number

599 NEW$c190419

 

SCP catalogers–see TPOT document “Removing Electronic Resource Access Points from Millennium and Melvyl” for internal notes to add to the item and checkin records for these.