RE: [IUG] Managing overlays and duplicate bibs

["Strouse, Mary" <STROUSE at law dot edu>]

Pat, there are a couple places where this can go wrong.

First, the instruction to overlay based on matching on a particular
field (such as the OCLC number) must be included in a load table. This
setting is not viewable in the load table parameters you can see (unless
you've had the load profiling training/module).  Pretty much, all oclc
load tables contain the instruction to overlay on oclc record number.
The initial load table used to populate the database, however, does not
contain any overlay instruction because it isn't needed.

So, one possibility is that you are not on the right load table. If no
load table is defined by a "949" field in the OCLC record, Millennium
may be using whatever is the first load table in the list.

We use the command line
949    *recs=b; routinely to ensure the right load table is used.  This
equals load table m2btab.b.

Another possibility is that the "target" bib records (the ones already
in your database) don't contain an oclc number in the 001 field?

To some extent, default load table settings can be overridden by the
contents of the 949 field in the oclc record (sometimes inadvertently).

Here, the following command apply.

Ov=o; (overlay on oclc number)
Ov= ; (do not overlay, even if the oclc number matches)
Ov=.b; (will overlay on a specific bib. Record number in millennium, if
provided. Otherwise, won't overlay.

The manual pages to look at are Page # 101512 and 101516.  And, no, it
isn't clearly laid out in the documentation how all this fits together.
See also Page # 101524 (additional considerations), esp. re authority
downloads/overlays. 

Call if you need to.

Mary

Mary M. Strouse
Head of Technical Services
Judge Kathryn J. DuFour Law Library
Catholic University of America
(202) 319-5547
(202) 319-4447 FAX
http://library.law.cua.edu

-----Original Message-----
From: innopac-bounces at innopacusers dot org
[mailto:innopac-bounces at innopacusers dot org] On Behalf Of Burke, Patricia
Sent: Thursday, December 21, 2006 12:29 PM
To: IUG INNOPAC List
Subject: [IUG] Managing overlays and duplicate bibs

Hello to anyone still working out there!

 

We are a new III library on Millennium 2006.  We are practicing
importing records from OCLC and are having a difficult time
understanding the overlay/duplicate process.  The manual doesn't seem to
have any instructions on merging or overlaying records, so if I've
missed it, please point me to the pages.

 

Even faster and easier for me would be to have someone explain the
process step by step.  I've tried to overlay twice and it seems to want
to keep the existing bib instead of the new one.  Then once I get past
this step, then I really do have two bibs, the old one and the new one.
I've spent a couple of hours fooling with this now, and since I haven't
gotten instant gratification, I'm starting to get a bit frustrated with
this process.  In our old system you could see both and select one to
keep and the other to merge away.  M2006 isn't quite as literal.

 

Any help would be most appreciated.

 

Thanks,

 

Pat

 

Patricia Burke

Bishop Payne Library

Virginia Theological Seminary

pburke at vts dot edu

703-461-1794

 

 

 



--- StripMime Report -- processed MIME parts ---
multipart/related
  multipart/alternative
    text/plain (text body -- kept)
    text/html
  image/gif
---
--
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