[ List Archives Home ] [ Thread index for 2008 ] [ Date index for 2008 ] [ Author index for 2008 ]


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
On a related note, how you structure the command line affects overlay
as well as addition of item data. Are you specifying an overlay point
in the command line, or just counting on default behavior?

You may want to consider load table training. While this may sound
like using a chainsaw to cut butter, being able to create and modify
load tables is extremely handy since libraries often need to load data
from different sources. Aside from specifying overlay, you can decide
things like which fields are loaded, how they are indexed, and you can
add or modify fields on the fly (e.g. routing URLs through your proxy
or supplying standardized link text). Load tables can also be helpful
for complex large scale maintenance that cannot be handled through
global update and the other utilities. Once you have access to your
load tables, problems like the one you are having now can easily be
solved in a couple minutes.

kyle

> I think this depends on how your load tables have been set up some users
> have an overlay field of 001 others have one at 020. Ours is at 020 and
> if the contents of this field are identical on the record that you are
> importing our load table will overwrite the bib record with the new bib
> record (I think you have to set the default behaviour with Innovative -
> but it can be changed).

>> We are looking at contracting with Ingram to catalog bibs and items. We
>> would add the data via ftp. In all the test loads we can add bibs, but
>> load table will not create items and if bib already exists, a new one is
>> created, and the existing one is not overlayed. Any help would be
>> appreciated.



--
----------------------------------------------------------
Kyle Banerjee
Digital Services Program Manager
Orbis Cascade Alliance
banerjek at uoregon dot edu / 541.359.9599