CAUTION: some Old Yale class numbers resemble LC class numbers in form but differ from LC in scope, e.g.
|Class number||LC scope||Old Yale scope|
|B50-B96||Philosophy||History of civilization|
|CE||Technical chronology||United States history|
|E||United States history||Geography|
|P||Languages and literatures||Law|
As a rule of thumb, even when Old Yale call numbers only use capital letters, they may be identified by their use of lower case letters in some of their cutters and the use of numeric book numbers; also, in most cases Yale adds "(LC)" below the call number for classes that might be mistaken for Old Yale. The number of potentially overlapping situations appears to be quite small. However, since the Voyager call number index in the Orbis OPAC interfiles all classifications, catalogers need to be reasonably alert to the differences when shelflisting. (The interfiling is currently under review.)
See a general table for Old Yale numbers
There is also some letter overlap in the SuDoc (U.S. Superintendant of Documents) and LC classes, e.g. TD. SuDoc numbers can usually be identified by the presence of colons and slashes. When viewed in the Voyager Cataloging Module, the 852 first indicator should be 3.
|852||3||0||‡b muddgdcm ‡h TD 4.2:Ai 7/35|
The classification scheme selected for the call number must have the correct first indicator in the Voyager MFHD record, or the call number will not index properly. LC classification must have first indicator 0 as in the following example:
|852||0||0||‡b ksl ‡h QC793.5.N42 ‡i N47X 2000 (LC)|
Formatting: 050 vs. MFHD
Note that the subfield indicators used to delimit the different parts of the LC call number differ between the 050 on the bibliographic record and the 852 in the MFHD record. Catalogers need to be aware of this when copying and pasting from one field to the other, or when editing a 090 field to 050 _4. (The Voyager ctrl-n command automatically converts the subfield indicators when it copies the call number from 050 or 090 into the MFHD.)
In the bibliographic record's 050 field, the class number is entered in ‡a; the rest of the call number is entered in ‡b when there is a single cutter. If there are 2 cutters, both the class number and the first cutter number are entered in ‡a; the second cutter and the rest of the call number are entered in ‡b.
|050||0||0||‡a NK4165 ‡b .L5 1996|
|050||0||0||‡a NK4156.6.A1 ‡b T53 1993|
In the MFHD record's 852 field, the class number is entered in ‡h; the rest of the call number is entered in ‡i when there is a single cutter. If there are 2 cutters, both the class number and the first cutter number are entered in ‡h; the second cutter and the rest of the call number are entered in ‡i. Note that the location code is entered in ‡b.
|852||0||0||‡b art ‡h NK4165 ‡i .L5 1996 (LC)|
|852||0||0||‡b art ‡h NK4156.6.A1 ‡i T53 1993 (LC) ‡m Oversize|
The period used to expand the classification number is REQUIRED in both 050 and 852, e.g.
The period used to separate the cutter number from the classification number is REQUIRED in 050. Note that a period is not entered before the 2nd cutter.
|050||0||0||‡a PN1993.5.I88 ‡b A2 1995|
In 852 the period preceding the cutter number may be replaced by a space [a legacy of the previous NOTIS ILS; period is preferred in current Voyager cataloging]. There must be either a space or a period separating the first cutter from the class number to ensure proper indexing.
|852||0||0||‡a sml ‡h PN1993.5.I88 ‡i A2 1995+ ‡m Oversize|
|852||0||0||‡a sml ‡h PN1993.5 I88 ‡i A2 1995+ ‡m Oversize|
|852||0||0||‡a sml ‡h PN1993.5I88 ‡i A2 1995+ ‡m Oversize|
For additional call number formatting examples (852 only), refer to: