[Evergreen-catalogers] Authority control

[Mary Llewellyn]

Hi all,

 

We are starting to think about resuming our authority control workflow. We
haven't done it since migrating from our old system, and I'd like to compare
notes with other libraries.

 

Ideally, we would export our entire database and send it to our authority
control vendor to establish a new base file. In our old system, we used a
command line "marc-in" to reload the bibs once the vendor had processed and
returned them to us, replacing the old version of the records in the
database with the new ones. We would then load the accompanying authority
record files, and they would link to the bib records. 

 

For ongoing auth work, we would, on a quarterly basis, export the bibs that
had been added to the database since the previous export, send them to the
vendor and get back the bibs and auths to load and link. We would also get
files of auth records that had changed headings, so that we could load and
replace the earlier auth records.

 

Has anyone started doing this kind of auth work in Evergreen 2.2? What
should we be aware of? ? Since the files will be large, I'd imagine we
wouldn't be importing through the client. Are there scripts to match bibs
and auth records during batch loads like this?

 

Any guidance would be greatly appreciated.

 

Mary

 

Mary Llewellyn, Database Manager

Bibliomation

Middlebury, CT

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.evergreen-ils.org/pipermail/evergreen-catalogers/attachments/20120711/2df1ce30/attachment.html>