Page tree
Skip to end of metadata
Go to start of metadata

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

Unlike many MARC-based library systems, Symphony distinguishes between the bibliographic 001 field and its own internal system control number, called the CKEY, usually referred to as the_ {}catkey_. While the source 001 is usually retained on load and is one of several fields that may be used as the basis for a bib record's title control number or flexkey, the CKEY in most Sirsi/Dynix Symphony catalogs is hidden from view until reported out for some purpose, such as for outputting a file of records. However, because the catkey is the only control number that can uniquely identify a record in Sirsi (flexkeys can be changed), NCSU Libraries has made this number explicit by automatically adding it to a 918 field when a new record is filed.  This allows the public Endeca catalog, whose bibliographic data is refreshed only an hourly basis, to point back to our backend ILS to enable the display of live holdings and circulation information. _The 918 should never be deleted unless there are multiple copies of the field!  _If you accidently delete the last 918 on a record, you can find out what it was by creating a temporary auto call number or item record.  The relationship between CKEY and other auto numbers (items, call numbers, title control numbers) is shown in the following chart where the root CKEY is bolded

Sirsi tag

Number construction

CKEY (918)

1234567

Auto title control number

a1234567

Auto call number

XX(1234567.1)

Auto item ID

1234567-1001

Thus, an auto 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 been assigned 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 disables) overlays from proceeding. This number will reflect the load criteria you set to get a MARC record into Symphony. For records loaded through the Symphony 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:

Code/Prefix

Name source

Tag source

a

System-assigned #

auto

c

Gaylord #

001

g

Local #

001

h

Local #

035

i

ISBN

020

j

ISBN

021

l

LCCN #

010

m

Marcive #

900

n

LCCN #

001

o

OCLC #

001

p

OCLC #

035

q

Laserquest #

001

r

RLIN #

001

s

ISSN

022

S

SIRSI #

035

w

WLN #

035

Except under the two local number policies (g and h), 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:

tag

field contents

load policy

flexkey

010

58004233

l

l58004233

001

ocm58004233

o

o58004233

035

(OCoLC)58004233

p

o58004233

With the advent of outsourcing for copy cataloging, a lot of records are now entering Symphony with non-unique vendor-supplied numbers, such as those from YBP, Serials Solutions, UMI, and Gale. These numbers usually, but don't always, use a system prefix which Sirsi will not strip off. These are generally loaded using the two local policies with the following outcomes:

tag

field contents

load policy

flexkey

001

ssj0069760

g

ssj0069760

001

ssib001237482

g

ssib001237482

001

ybp2358984

g

ybp2358984

035

tmp97407602

h

tmp97407602

035

(Safari)0130385603

h

0130385603

Acquisitions and Discovery is currently using the following hierarchy in both SmartPort and batch loading for general cataloging (not outsourced): opil (OCLC # in 001, OCLC # in 035, ISBN # in 020, LCCN in 010). Remember that you can always change the flexkey, either temporarily to enable an overlay, or permanently.

Authority control number (authkey)

For authority records, our main source is LC authority records from our Marcive subscription. It is also 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:

Code/Prefix

Name source

Tag source

c

Authority control #

001

h

Authority control #

035

n

Authority control #

010