Document: OSUPFW in 910
Date: March 7, 2001
Issued by: Cataloging Department (nvp)
This document provides some further background and guidance for using or omitting 'osupfw' in field 910.
BACKGROUND
The phrase 'osupfw' in field 910 is used to allow weekly collection of OSCAR
full cataloging records to send to OCLC to set the OSUL holding. This process is done by
Catalog Maintenance. The only reason to have 'osupfw' in a 910 is that the OCLC holding is not
set for OSUL.
This group of records MUST include full OCLC bibs which were not added as Promptcat records OR which were exported to OSCAR but not 'updated' or 'produced' on OCLC. Usually, this latter group comprises OCLC bibs that are exported to OSCAR individually. (Note: GPO full records loaded as a group to replace shipping list records are collected separately and sent to OCLC to set holdings.) See SPECIAL SITUATION TO WATCH FOR, below, for multiple cataloging centers using the same record.
This group of records should NOT include Promptcat bibs or bibs that were 'updated' or 'produced' on OCLC.
There is a charge (ca. 27 cents) for setting the OCLC holding, whether it is done individually (via 'update' or 'produce') or by sending a file of records in a batch. A double charge will be incurred if the record is 'updated' (as copy) on OCLC and is then later collected and sent with a group to set holdings. Original records should never include 'osupfw.'
Promptcat bibs are excluded because holdings are pre-set by OCLC. If the material is not selected and the record is not to be 'cataloged' then the OCLC holding must be deleted.
Catalogers may use a single constant data that either excludes or includes 'osupfw' and adjust as needed, or have different constant data depending on their typical workflows.
Effective March 1, 2001, The Cataloging Dept. will use 'update' in most cases and discontinue use of 'osupfw' when working in OCLC.
1) DO NOT add 'osupfw' in 910 if:
-
the OCLC record is original cataloging (new record)
OR
-
full OCLC record is on OSCAR and the record has 910 = YBP (IS a Promptcat bib)
OR
-
the OCLC record is NOT yet on OSCAR and the OCLC record is 'updated' or 'produced' while working in OCLC
2) DO add 'osupfw' in 910 if:
-
full OCLC record is NOT on OSCAR and the OCLC record is NOT 'updated' or 'produced' while working in OCLC
OR
-
full OCLC record is on OSCAR and the record lacks 910 = YBP (is NOT a Promptcat bib) and no other OSUL copy is shown in OSCAR
SPECIAL SITUATION TO WATCH FOR:
If the existing OSCAR record has a CAT DATE but
the only copy on OSCAR is for a cataloging center other than OSUL (LAW, HEA, CHI,
regional) AND
the bib was not added via Promptcat (910 = YBP),
then set the holding by working
in OCLC and using 'u' (update) without exporting the record.
Case 1 - Full bib downloaded individually
Full bib (not Promptcat) is present on OSCAR but OSUL copy is not yet received/processed.
LAW adds item record for its copy, adds CAT DATE and unsuppresses bib.
MAI copy is received/processed, item record added.
THEN OSUL cataloger must go to OCLC and 'update' (u) the record but not export again.
Case 2 - Promptcat bib
Promptcat (910=YBP) bib is present on OSCAR but OSUL copy is not yet received/processed.
LAW adds item record for its copy, adds CAT DATE and unsuppresses bib.
MAI copy is received/processed, item record updated.
THEN do not update on OCLC to add OSUL holding.
Other cataloging agencies using an OSUL bib and adding a copy to OSCAR will need to set their own holding by 'updating' on OCLC.
Return to Technical Services Documentation menu.
Cataloging Department Home