RE: III and MarcEdit (loading records back?)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Date: Fri, 16 Jan 2004 12:03:16 -0500
- From: "Strouse, Mary" <STROUSE@xxxxxxxxxx>
- Subject: RE: III and MarcEdit (loading records back?)
And there's yet a third way. You can edit the overlay protection list for that load table in Set database options. Load table training isn't required. Thus, you can keep the original cat date by protecting the cat date field. But the function is a bit fussy. Be sure to read the documentation careful before setting it up. See the manual at #101871.
Mary
Mary M. Strouse
Head of Technical Services
Judge Kathryn J. DuFour Law Library
The Catholic University of America
Washington, DC
(202) 319-5547 strouse@xxxxxxxxxx
http://law.cua.edu/library/
-----Original Message-----
From: innopac-bounces@xxxxxxxxxx
[mailto:innopac-bounces@xxxxxxxxxx]On Behalf Of Kyle Banerjee
Sent: Thursday, January 15, 2004 7:14 PM
To: IUG INNOPAC List
Subject: RE: III and MarcEdit (loading records back?)
> We've just started using Terry Reese's MarcEdit software to do some
> database maintenance activities, including a 10,000+ file of netlibrary
> records that needed 856 proxy and |z edits and |h replacement, it was
> blazingly fast to fix.
> Loading the records back into III was not quite as simple, but we figured
> it out.
>
> The question at hand is this, when a record overlays (on OCLC number) the
> catalog date is changed from the original one to the date of the new
record
> load, we report our cataloging statistics based on catalog date, so this
> would be a problem? Is there a way to craft a load table that protects
the
> original catalog date or a 949 command that would spare the original
> catalog date?
There is (just put ct=yourdate in subfield a of the 949), but you may want
to consider specifying a blank cat date in the 949 instead so that they
don't show up at all in your regular cataloging statistics. Importing
thousands of records at a time is very different than cataloging them the
old fashioned way. If a couple record loads (e.g. aggregate databases) are
mixed in with regular cataloging statistics along with your NetLibrary
titles, it will make your unit look like they periodically go insane and
start cataloging everything in site :)
kyle
--
This message was distributed through the Innovative Users Group INNOPAC list
Public replies: INNOPAC@xxxxxxxxxx
Update your subscription options: http://innopacusers.org/mailman/listinfo/innopac