599 field (CDL records)
Author: Renee Chin
Created: September 16, 2002
Revised: January 08, 2008
[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 material if applicable: DB, cadocs, clone, separate] $b [actions taken] $c [yymmdd]
$a : Indicate the type of update: NEW, UPD and DEL.
$b : If the resource is a database (integrating resource) or California document, add $b DB or $b cadocs, respectively, after the $a NEW, UPD, or DEL for all >599 notes. If the title is both a database and California document, use $bcadocs DB. If the title is a monograph, specify whether it is a clone (in-house reproduction) or separate record (OCLC computer file record). Add $b clone or $b separate after the $a NEW, UPD, or DEL. Do not add any specification in the $b for "born-digital" monographs.
$b : List actions taken. Use a semi-colon to separate different actions. Be as brief as possible, however, do not use abbreviations. Use the symbol ">" as notation for the MARC field, e.g., >530, >740.
$c : Enter today's date [yymmdd]
EXAMPLES OF >599 FIELDS
NEW (for new records added)
For a serial or born-digital monograph: NEW|c051018
For a database: NEW|bDB|c051018
For a California doc (serial or monograph): NEW|bcadocs|c051018
For a California doc (database): NEW|bcadocs DB|c051018
For a mono, if in-house generated electronic reproduction: NEW|bclone|c051018
For a mono, if OCLC separate record: NEW|bseparate|c051018
For new records (serial or monograph) with more than one >856 field: NEW|badded access for LexisNexis and open access|c071213 [Specify the access points/packages in $b]
DEL deleted records (indicate reason for deletion in $b):
DEL|bNoUC holdings|c051018
DEL|bDB|bNo access|c051018
DEL|bNot licensed|c051018
DEL|bcadocs|bNo longer available online|c051018
UPD updates (several categories)
UPDATES TO SPECIFIC FIELDS (spell out fields in $b, use semi-colon to separate actions):
UPD|bupdated >530, >776, >793; added >793|c051018
UPD|bupdated >856 $z|c071213
COVERAGE UPDATESUPD|bupdated holdings in >856|c051018
UPD|bupdated holdings in >856 for Sage and Blackwell|c071213
TITLE CHANGE with no other changes:
UPD|bTC|c051018
UPD|bcadocs|bTC|c051018
(no need to spell out exact fields updated because review of specific fields is standard)
TITLE CHANGE with other changes:
UPD|bTC; updated holdings in >856|c051018
ADDING ADDITIONAL ELECTRONIC ACCESS:
UPD|bAdded access for LION|c051018
UPD|bAdded access for Blackwell-Synergy and OUP|c051018
(do specify the package but there is no need to spell out exact fields added because >793 and >856 are standard)
DELETING ELECTRONIC ACCESS POINTS (i.e., when there are multiple providers):
UPD|bclone|bDeleted access for IEEE|c060918
UPD|bDeleted access for Blackwell-Synergy and OUP|c060918
(no need to spell out exact fields deleted because >793 and >856 are standard)
REPLACING AN EXISTING CDL RECORD WITH A CURRENT/CHANGED COPY OF THE SAME OCLC RECORD:
UPD|bReplaced with current CONSER record|c051018
UPD|bcadocs|bReplaced with current OCLC record|c051018
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|breplaced by OCLC#987654321|c070123Single-/successive entry-/PCC record:
>599 __ NEW|breplaces OCLC#12345678|c070123CEASED TITLE:
UPD|bCeased title|c051018
