SIRSI CONVERSION: CALL NUMBER |z INSERTION PROBLEM
8/5/10spg
Sirsi records
A record in Sirsi comprised several levels:
 Control or title information record that carried the Sirsi control number, format, date
created/cataloged/modified, etc.
 Bib record
 One or more Volume/Copy records--"Call/Vols"--that carried call number information and copy (item)
information, sort of like a MFHD and item record combined
 One or more MARC holdings record--"MFHLs" or "MHLDs"--that could be associated with Call/Vols
with the same location and base call number. They were not incorporated as a middle layer between
bib and item and were, in fact, optional, since Call/Vol information showed in the OPAC anyway. We
used them for multi-volumes (maybe just serials?) only, and not consistently since the MARC
holdings format was not developed until the late '90's.
Records could be "shadowed" (suppressed) at the Control, Call/Vol, or Copy level. Shadowed records
were not converted.
Call/Vol:
[Copied from a 2005 Indiana University document.]
Variable data was input as part of the call number in |z, e.g.:
H35 .E36|zno.13
AE5 .E363 2010|zv.2
The data before |z constituted the "base" call number. In order to correctly demarcate the base call
number, |z's had to be constructed exactly the same as to capitalization, punctuation, and spacing.
While the MHLD was essentially independent of Call/Vols, those with the same location and same base
call number could be associated with a particular MHLD. [I'm unsure of the exact relationship.] If a
location or call number was changed in the Call/Vol it had to be changed in the MHLD, too. MHLDs were
useful for public notes about holdings because they could not be displayed from the Call/Vol.
Summary of problem
Holdings converted largely on the basis of Call/Vol records. Call/Vols with the same location and same
call number became, in Voyager, one MFHD with one or more item records attached. The base call
2
number went into 852 |h and |z information into the Enum of each item record. Associated MHLD data
went into the 866. This worked well when |z correctly demarcated the base call number from variable
data, and when the MHLD was in harmony with the Call/Vols.
Unfortunately, adding |z was not consistently done at Wesleyan. Furthermore, while Sirsi supplied |z
automatically for the LC class scheme and certain common captions (v., no., pt., ser., Suppl., no, Bd. and
months), the |z was not always in the right place and we did not always bother to correct it. Missing or
incorrectly-placed |z's meant that base call numbers might not be grouped together, creating multiple
MFHDs. Prior to the conversion we inserted as many |z's in batch as we could; this was done for LC
serials, for SuDocs items, and for as many WMA items as could be managed.
If locations in the MHLD and Call/Vols differed, multiple MFHDs were created. For example:
 First MFHD has location "o,", no call number or item records, correct holdings statement in the
866: v.1-3
 Second MFHD has location "e," a call number, a series of 866's that came from the attached item
records: v.1, v.2, v.3.
One explanation is that the Sirsi MHLD had location Olin and the Call/Vols Sci. But it could also be a
conversion error where the MHLD location could not be determined for some reason and Olin, as the
default location, was supplied. It's likely we'll see a pattern as we look at more records.
Another, more convoluted, example:
 First MFHD has location "o," call number, correct holdings statement in the 866: no.24-32, item
record with a system-supplied barcode from the NOTIS-Sirsi conversion (001ADA3021), no
Enum
 Second MFHD has location "o," same call number, 866 with "no.24," no item record
There are in fact two copies of no.24, but how can we tell this without checking the shelves? It will take a
few more examples to be sure of a pattern, so what follows is conjecture for now. Unlike the previous
example, the first MFHD has both a correct 866 and an item record, albeit without an actual barcode or
Enum. Item records did not willy-nilly migrate from one Call/Vol to the other during conversion, so the
item record was always attached to that Call/Vol which was in turn associated with a MHLD. The second
MFHD is odd in that it lacks an item record, so how did "no.24" get into the 866? It must have been in |z
of a second Call/Vol. or, less likely, second MHLD associated with the Call/Vol. Apparently an item
record for the second Call/Vol was never created. Could it be, though, that the item record was
shadowed and did not convert?
Cleanup needed
Our biggest concern may be variable data that does not show in the OPAC. A MFHD was created for
each instance of location + base call number, but where the variable data went into the item record Enum
it was lost from public display. Cleanup involves pulling the various MFHDs/items under one MFHD and
constructing correct holdings statements, but it may not be possible to identify these records as a discreet
group. There is talk that the next full version of Voyager will allow the display of item record information-that could be good or bad! Fortunately, circulation is not affected by this problem, and items with certain
statuses do show in the OPAC.
At the other end of the spectrum are records with multiple MFHDs whose call numbers are the same
except for variable data, a result of missing |z's. They look odd but at least the variable data displays.
Again, it is unlikely that these can be identified as a group. The variable data does not show in the
circulation status message but at least it's in the call number.
The situation is murkier than the above paragraphs would indicate since any number or combination of
missing/incorrect call numbers and holdings may present themselves. Until clear patterns emerge some
checking in the stacks will be necessary.
Serials did a lot of work to clean up what were current receipts at the time.
3
SPG email 9/22/03
To those who might be interested in the call number |z problem: Call numbers without |z's or with |z's in
the wrong place will generate unnecessary MFHDs in Voyager. (The |z itself will not convert to Voyager,
rather it will demarcate the base call number from the volume caption so that one MFHD is created with
multiple item records under that one MFHD, rather than an MFHD for each.) Alan is ready to do what he
can to preprocess our call numbers. The most important thing seems to be to insert |z where it does not
exist, for serial-format records, but I'm open to other suggestions.
Some of you have seen a report from Alan--copied below--attempting to identify "prefixes" (i.e "volume
captions," also called "analytics" by Endeavor) that lack |z. Alan supplies a count, but the point is that he
can use the logic to insert |z automatically, or at least he can report them out for us to review. I am
interested in hearing your thoughts on his logic and what, if anything, needs to be changed or added-please let me know by end of day Tuesday, or come to the VCG meeting on Wed. at 9:30 in Develin.
For example, it might make sense for Alan to confine identification of "v.," "no.," "pt.," "Bd.," and certain
other prefixes to class schemes other than LC and SUDOC, because Sirsi has reliably (?) inserted |z
ahead of certain captions for these class schemes:
v. no. no pt. Bd. (ser. and Suppl. are also set up for auto |z in Sirsi but should NOT be, necessitating cleanup)
Jan. Feb. Mar. Apr. May Jun. (we use June, needs cleanup) Jul. (we use July, ditto) Aug. Sept. Oct. Nov. Dec.
(Scott, did this help or hinder SUDOC or have no effect?)
Subfield z's appear for other class schemes when the class scheme has been changed from LC or
SUDOC, or when staff have inserted the |z. In other words, seldom.
Problems that Alan's logic probably cannot address, when applied to the LC and other class schemes:
1) Due to the auto-insertion of |z for captions "ser." and "Suppl." in the LC class scheme, and also staff
error, |z's are in the wrong place on lots of records, but it may be asking too much at this time to identify
and fix them. But I think these usually will not result in the creation of multiple MFHDs, only a not-quitecorrect indication of Enum in the item record:
new ser. n.s.
n. s.
Folge
F.
n.F.
n. F.
sec.
Examples:
Entire title is series 3: QC721 .P4|zser.3 v.39 1989 p.2457-3206 should be QC721 .P4 ser.3|zv.39 1989 p.2457-3206
Entire title is new series: JN7001 .S3 new|zser. v.11 1988 should be JN7001 .S3 new ser.|zv.11 1988
Entire title is Folge 7: QC1 .A6|zFolge 7 Bd.46 1989 should be
QC1 .A6 Folge 7|zBd.46 1989
Entire title is section C: QD901 .A18|zsec.C Index v.C54 1998 should be QD901 .A18 sec.C|zIndex v.C54 1998
2) I can't think of anything brilliant to do about our annuals differentiated by year only, which generally do
not have |z's (unless a staff member has put them in). Staff view of an annual with just year and no |z's:
31841005330840 WUo31273000
JN15 .E875
Title
WU-OLIN
Location
Library has
JN15 .E875 1993
:The European Union : annual review of activities.
-: STACKS
: 1993-2001/2002
(Displaying 9 of 9 volumes; Copies on order)
JN15 .E875 1993
copies:1
library:WU-OLIN
copy:1 ID:31841005330840 BOOK (STACKS)
JN15 .E875 1994
copies:1
library:WU-OLIN
copy:1 ID:31841005397203 BOOK (STACKS)
JN15 .E875 1995
copies:1
library:WU-OLIN
4
< snip >
copy:1 ID:3184100811622 BOOK (STACKS)
JN15 .E875 2001/02
copies:1
library:WU-OLIN
copy:1
ID:31841010303402 BOOK (STACKS)
copies:1 status:ON-ORDER
parts:Standing order
5
But here's one with year first, then |z automatically input by Sirsi to precede "no.": QD1 .C5845
2002|zno.22-24 p.2419-End. Obviously, the |z should be before the year instead:
31841008929309 WUo44000773
QD1 .C5845
QD1 .C5845 2000 no.1-3 p.1-470
Electronic access :2000-2002 http://www.rsc.
org/is/journals/current/perkin1/p1con.htm
Title
:Perkin 1 : an international journal of organic and bio-organic chemistry.
WU-SCIENCE
-Location
: PER-STACKS
Library has
: 2000-2002
(Displaying 25 of 25 volumes)
QD1 .C5845 2000 no.1-3 p.1-470
copies:1
library:WU-SCIENCE
copy:1 ID:31841008929309 BOUND-VOL (PER-STACKS)
QD1 .C5845 2000 no.4-6 p.471-1044
copies:1
library:WU-SCIENCE
copy:1 ID:31841008929358 BOUND-VOL (PER-STACKS)
QD1 .C5845 2000 no.7-9 p.1045-1470
copies:1
library:WU-SCIENCE
< snip >
copy:1 ID:31841009658477 BOUND-VOL (PER-STACKS)
QD1 .C5845 2002 no.22-24 p.2419-End
copies:1
library:WU-SCIENCE
copy:1 ID:31841009658535 BOUND-VOL (PER-STACKS)
QD1 .ELECTRONIC JOURNAL
copies:1
library:WU-SCIENCE
copy:1
ID:2332225-2001
E-JOURNAL (ONLINE)
ORDERS:NONE
3) Ditto ordinals, where Sirsi automatically supplied |z before the "v."--e.g. AS22 .E5 40th ed.|zv.1 pt.3-rather than 1st, 2nd, 3rd, etc.:
31841004284568 WUo01223579
AS22 .E5
AS22 .E5 18th ed. 1984 v.1 pt.1/ep
Electronic access :http://www.galenet.com/servlet/AU
Title
:Encyclopedia of associations. International organizations.
WU-OLIN
Location
-: OVERSZ-X-- Note: Later editions in Olin Reference
and Science Reference
Library has
: 5th ed.:v.1 (1968)
Library has
: 6th ed.:v.1-2 (1970)
Library has
: 9th ed.:v.1-2 (1975
Library has
: 11th ed.:v.1-2 (1977)
Library has
: 12th ed.:v.1-2 (1978)
Library has
: 13th ed.:v.1 (1978)
Library has
: 14th ed.:v.1 (1979)
Library has
: 16th ed.:v.1 (1981)
Library has
: 18th ed.:v.1:pt.1-2 (1984)
Library has
: 20th ed.:v.1:pt.1-3 (1986)
Library has
: 22nd ed. (1988)
Library has
: 26th ed. (1992)-28th ed. (1994)
Library has
: 30th ed. (1996)
Library has
: 32nd-33rd ed. (1997)
WU-OLIN
-Location
: REFERENCE-- Note: Earlier editions in Science
Reference and Olin Oversize Stacks
Library has
: 38th ed.
Library has
: 40th ed.
WU-SCIENCE
-Location
: REFERENCE-- Note: Later edition in Olin Reference,
6
Library has
Library has
earlier editions in Olin Oversize Stacks
: 34th ed. (1999)
: 36th ed.
(Displaying 41 of 41 volumes; Copies on order)
AS22 .E5 18th ed. 1984 v.1 pt.1
copies:1
library:WU-OLIN
copy:1 ID:31841004284568 BOOK (OVERSZ-X)
AS22 .E5 18th ed. 1984 v.1 pt.2
copies:1
library:WU-OLIN
copy:1 ID:31841004284626 BOOK (OVERSZ-X)
AS22 .E5 20th ed. 1986 v.1 pt.1
copies:1
library:WU-OLIN
< snip >
copy:1 ID:31841008800658 REF-BOOK (REFERENCE)
AS22 .E5 36th ed. v.1 pt.2
copies:1
library:WU-SCIENCE
copy:1 ID:31841008800716 REF-BOOK (REFERENCE)
AS22 .E5 36th ed. v.1 pt.3
copies:1
library:WU-SCIENCE
copy:1
ID:31841008800773 REF-BOOK (REFERENCE)
library:WU-MUSIC
copies:3
status:ON-ORDER
Date: Mon, 28 Jul 2003 15:01:43 -0400
To: sgrucan@wesleyan.edu
From: Alan Hagyard <ahagyard@wesleyan.edu>
Subject: prefixes
Sally Here is a list of "prefixes" and the number of occurrences within call numbers which have no |z.
The logic used to identify these:
1) call number has 3 or more segments (e.g. XX1 YY2 ZZ3 ...)
2) look at the LAST segment
3) split the last segment on a period (".")
e.g. v.1 becomes part1="v" and part2="1"
v1 becomes part1="v1" and no part2
tome.99 becomes part1="tome" and part2="99"
4) if the first character of part1 is lowercase, print part1
5) count the number of occurrences
[NOTE : a call number like "F625 P94 v.3 pt.1" will give "pt"
a call number like "Z699.A1 D37 v.19 1996" will give nothing (does not start with lowercase)
a call number like "F4563 9P1 v.1 (bw1)" will give nothing (starts with parenthesis)
14 abs
14 horn
15 curr
16 b
16 d
16 maps
16 sec
17 suppl
18 s
19 v2
20 booklet
20 piano
22 atlas
22 e
22 manual
24 plates
25 nr
25 sup
28 viola
28 vyp
31 cello
31 parts
33 ed
36 kn
39 a
40 violin
43 c
43 nos
47 comp
50 text
51 number
62 index
64 p
77 bk
78 op
82 disc
84 pt
87 fasc
88 guide
99 cassette
105 score
136 disk
169 supp
248 original
362 cop
543 v
642 dub
874 set
983 t
1321 no