RE: [IUG] LTI, Load Tables and Duplicate 050s
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Our library has just begun to utilize LTI for our authority work. Ideally,
we wish to keep all our "y"-tagged 050s as well as our "c"-tagged 050s.
PROBLEM: A load table was created for downloading the in-coming file of bib.
records once the authority work was done. When we downloaded our first file
we noticed that the Call. No. data was duplicated when reloaded (i.e. a
"c"-tagged 050 + an identical "y"-tagged 050). Our base file is currently
being processed by LTI and we would like to straighten out this matter
before we have to download this exhaustive file of all our bib. records.
QUESTION: Does any other libraries using LTI keep their "y"-tagged 050 data?
If so, how is this set up in the load table? Is it possible to protect all
of our 050 call numbers, whether y-tagged or c-tagged, when loading files
from LTI without creating duplicate "y"-tagged 050s? Would it work if we
protected both the y-tagged and c-tagged 050s, along with the c tagged 090s,
and designate in the load table for authorized bibliographic records from
LTI "bib y 051-055"?
Regent Carey Library
audrey at regent-college dot edu