Cataloging Home

Libraries' catalog
Journals | E-Matrix
WorldCat NCLive | Beta
Public Department page
Staff server
Cataloging wiki

Department
Annual reports
Directory
Forms for staff (pwd)
Help requests (pwd)
Personnel guidelines
Planning and projects
Presentations
Production statistics

Department sections
Continuing & Electronic Resources
Metadata & Database Quality
Monographs

Cataloging tools
Cataloger's Desktop (pwd)
ClassWeb (password)
Cataloging agencies
Cutter tables
Design images classification
Format-specific tools
Library of Congress tools
MARC documentation
OCLC tools
OPAC tools
Reference sources
Remote OPACs
Special call numbers
Unicorn tools

Local procedures
Cataloging guidelines and procedures by topic
Cataloging guidelines and procedures by branch
Memo bank
Metadata project procedures
Rare/special materials

News for catalogers
Recent news/events
Technical service e-journals

Unicorn control numbers

The CKEY and auto-generated title, call number (volume) & item numbers

Unlike many MARC-based library systems, Unicorn distinguishes between the bibliographic 001 field and its own internal system control number, called the catkey or CKEY. While the 001 is usually retained and is one of several that may be used as the basis for a bib record's title control number or flexkey, the CKEY in Unicorn is normally hidden from view until reported out for some purpose, such as for outputting a file of records. Note that for enabling direct links between NCSU Endeca and Web2 displays, Systems has made the CKEY explicit in local MARC field 918. These should not be deleted! This number serves as the root for the auto title control number, auto call number, and auto item ID, as shown in the examples below (root CKEY is bolded):

Note that a call number is simply the CKEY, a decimal, and a number indicating the relative volume number for that title record. .4 would be the fourth volume added, though not necessarily v. 4 bibliographically. In fact, if you had microfiche in three different branch libraries, these would be XX(1234567.1), XX(1234567.2), and XX(1234567.3) respectively. The decimal number is related to the total number of volumes, not just those which have auto call numbers.

Auto-generated item IDs are hierarchically associated with call number records, hence these numbers include both the volume number (red used here) and a copy number (blue) appended to the CKEY by a hyphen. 1234567-83009 would thus be the ninth copy of the 83rd volume attached to the title record whose CKEY was 1234567.

Title control number (flexkey)

The title control key is the field that enables (or disallows) overlays from proceeding. This number will reflect the load criteria you set to get a MARC record into Unicorn. Thus, for records loaded through the Unicorn Z39.50 client, the title control key is determined by "Title control number source" in your SmartPort settings. For batch loads using the bibload report, this will be set through the selection criteria "Title control number source for incoming items" under the "Selection Criteria" tab. In either case, the user provides a preferred hierarchy of potential flexkey sources from the follow codes:

Unicorn strips out parenthetical information such as the 035 "(OCoLC)", as well as 001 prefixes like "ocm", and adds the appropriate alpha prefix for that source of information. This prefix is useful in preventing potential conflicts between similar numbers in different control number schemes, so for three identical incoming control numbers:

010     58004233 --> will yield flexkey of l58004233
001   ocm58004233 --> will yield flexkey of o58004233
035   (OCoLC)58004233 --> will yield flexkey of o58004233

The Cataloging Department is currently using the following hierarchy in both SmartPort and batch loading of records: iopl (ISBN in 020, OCLC # in 001, OCLC # in 035, LCCN in 010). Remember that you can always change the flexkey, either temporarily to enable an overlay, or permanently. We generally prefer to have ISBNs as flexkeys where they are available, as it enables batchload matches of brief order records with later full LC or OCLC records.

Please note: Unicorn 2003 does not accept batch creation of title control numbers from 001 with the new prefix of "ocn" and 9 digit number. If you encounter a Unicorn record without ISBN, but with the new ocn 9 digit 001, check the title control number on the "control" tab to make sure that the OCLC number is reported there. If not, copy and paste from the 001.

Authority control number (authkey)

For authority records, our main source is LC authority records from our Marcive subscription or from SmartPort. It would be possible to load NAF records from OCLC as well, monitoring the source of control number to ensure non-duplication of records from the two sources. LC NAF records will have identical control numbers in 001 and 010, while OCLC records will have an OCLC control number in their 001. Generally, we prefer match on 010 for this reason. Values for control number matches are as follows:

Other control numbers

Since the purpose of the 001 has been served once the title control key has been formulated, it serves no useful end in Unicorn records once the record is loaded. However, there are two other bibliographic control numbers which are used in Unicorn for various purposes. The 919 contains control numbers carried over from the NCSU Libraries' former DRA system while the 035 (Sirsi) is used by the system to enable records sent out for outside processing to be loaded back into the system when that work is complete. We use the latter in particular for reloading records sent to Blackwell North America to have table of contents added and to Marcive for authority heading flips. The 035 (Sirsi) should be identical to the flexkey upon generation, but has the possibility of getting out of synch with that number after extracting files for vendor work. Once generated, the 035 is not automatically deleted. If there is more than one, 035 (Sirsi), the system uses the first to effect an overlay.