The discussion of authority control vendors reminds me that I don't have
a solid grasp of authority record processing.
This is what I have been able to figure out. Let me know if I have made
any incorrect assumptions.
Let's assume a 2.5 system.
Initial record loading
1. Authority records are loaded into the system.
2. The script authority_authority_linker.pl is run. This script links
reference headings in authority records to main entry headings in other
authority records.
3. The script authority_control_fields.pl is run. This script goes
though each bib record and creates a $0 in any field with a matching
authority record.
Does it matter what order this is done in?
Ongoing Processing
1. As new bibs are added to the database, run
authority_control_fields.pl on the range of new bib id's.
2. As new authority records are added to the database, run
authority_authority_linker.pl on the range of new authority record id's.
Do old bib records ever need to be run through
authority_control_fields.pl again? What if they are updated? What if
they are overlaid via vandelay? Is there ever a circumstance where a
new or updated authority record now matches old bibs? How would you
identify the bibs, or do you have to run authority_control_fields.pl
through the bib database periodically?
--
Martha Driscoll
Systems Manager
North of Boston Library Exchange
Danvers, Massachusetts
www.noblenet.org
