Re: [IUG] Call Number Commas in Bib Records

["Boggs, John" <boggs at plsinfo dot org>]

Hi Clay,

I don't know whether you can do this through OCLC or a load table, but
if you can't remove the commas from the OCLC end, and if Innovative
can't set up your load table to do this, you can use Global Update to
remove commas from the call number fields after you've loaded the
records.  I just tested this and it works.  You just choose "change a
variable length field," enter a comma into the Data field on the Find
line and nothing on the Replace line, and all commas in the field will
be removed.

John D. Boggs, PLAN Database Manager
Peninsula Library System
2471 Flores Street
San Mateo, CA  94403-2273
(650)571-6799 x3062
boggs at plsinfo dot org

-----Original Message-----
From: innopac-bounces at innopacusers dot org
[mailto:innopac-bounces at innopacusers dot org] On Behalf Of Workman, Clay
Sent: Friday, June 20, 2008 10:04 AM
To: IUG INNOPAC List
Subject: [IUG] Call Number Commas in Bib Records

I've been out of Cataloging for awhile and time has passed me by.

We use Dewey classification.  We do not like commas in our bib record
call numbers.

We also use OCLC Connexion client to create spine labels.  In many
circumstances, Connexion software requires you to enter a comma-space in
the MARC call number field in order to have your label data print on a
new line.

The result, for us, is a nice-looking label, and a bib record that has a
call number which has imported those commas.

My catalogers, and my own dim memory, tell me that OCLC software used to
have a way to strip out those commas and not export them.  I've looked
at the help guide for the current version of the Connexion client (2.1)
and can't find any notes about this.

Does anybody know if it's still possible to have those records leave the
OCLC software without the commas?  If not, is it possible to adjust our
bib load table to strip them on the way in?  I haven't had load table
training, but it's my understanding that load tables will only deal with
whole MARC fields, not individual characters within a field.  Am I
right?

Thanks for any tips.

Clay Workman
Tempe (Ariz.) Public Library


--- StripMime Report -- processed MIME parts ---
multipart/alternative
  text/plain (text body -- kept)
  text/html
---
--
This message was distributed through the Innovative Users Group INNOPAC
list
Public replies:  INNOPAC at innopacusers dot org
Update your subscription options:
http://innopacusers.org/mailman/listinfo/innopac