*** This version of Confluence is for testing only and contains a copy of content from June 29th 2026. No changes will be preserved. ***
Overview: This document d/ocu/ment outlines the ways in which Cornell’s Voyager records are reflected in the OCLC WorldCat database starting in January 2020, when cataloging activities moved from Voyager to OCLC Connexion.
...
Contact: Laura Wright
Date last reviewed: (still in process)9/29/2020
Two main things to remember:
...
(2) There must be a one-to-one correspondence between the Voyager bib ID and an OCLC record #.
(3) Cataloging is now done in OCLC and pushed into Voyager.
- Record of record for holdings, items, local data = Voyager
The CUL database of record is Voyager. Local and copy-specific notes will only be found there. As much as possible, however, updates to bibliographic data Updates to the bibliographic data, such as added contents notes, changes or additions to publication statements, or updated access points, should be made in OCLC and pushed into the same changes made to our local version of the record. It will often be easier to edit the record in OCLC and then "merge" in Voyager.
- Records created in Voyager are no longer sent to OCLC
Batch processing will send our holdings only back to OCLC, not the MARC records. If you have a record started in Voyager, you can export it to OCLC, open it in the local save file, and work from there. (insert link to procedure hereexporting records from Voyager to OCLC)
- Only one OCLC 035 per monograph bib record
If you are working on an existing OCLC record and then decide that a different OCLC record is better for your purposes, and overlay the first record with a second record, you will have multiple, different 035s on your bib. You have to delete the ones that are not your intended match. Multiple 035 subfield z’s and 019s are fine, but if you have two or more OCLC 035s subfield a’s, the machine will make the choice of which to attach Cornell’s holdings—and you may not like the machine’s choice.,
- OCLC has some different encoding levels
...
In Voyager, you must change the E/Lev in Voyager from an OCLC letter code to a MARC number code. The LTS statistics code does not count your original cataloging statistic 948:1 : if the E/Lev is an OCLC letter. (However, if you give yourself a copy stat in the 948:1 : $b c, you can use any code and the stats program doesn’t care). (talk to batch processing about changing this)
- Some records in Voyager get replaced
Any Voyager record coded 3, 5 or 8 will eventually be completely replaced in Voyager when if the record becomes full in OCLC. We run queries of all our E/Lev 3, 5 and 8 records against WorldCat and bring in any records coded blank, 4, I or (recently) M. Your record will be completely overlaid. A Voyager record coded blank or 7 is more protected, but it will still be subject to changes that you as a cataloger do not know about. if the record in OCLC is updated.
- FAST comes in automatically
...
If there is an authority record behind an access point in OCLC, that access point can be “controlled” by in OCLC (either manually or, to a limited extent, automatically). Then whenever the authority record changes the string in the 1XX, the controlled heading in OCLC automatically changes. This does not happen in Voyager. The changes to controlled fields in the OCLC record do not change anything on the Voyager record. automatically update the record Voyager.
- Authority control in Voyager—different!
...