- Article Type: Q&A
- Product: Voyager
- Product Version: 8.2.2
We had two authority records for different people with the same name. One authority record was updated, and when I processed the heading change, the second authority record was updated as well. Why?
Both authority records were linked to the same entry in the HEADINGS table. For example, if you have a 100 subfield a for
auth_id 123 : Doe, John
auth_id 456 : Doe, John
then both authority records will be linked to the normalized heading DOE JOHN in the HEADING table (via AUTH_HEADING). When one authority record updates that heading, the heading change cascades out to any other records that link to that row in the HEADING table when you process the heading change with Global Headings Change (GHC).
If you update auth_id 123
Doe, John, 1932 - 2011
then after you run catjob 12, if you fully expand the record tree for that heading change in the GHC queue, you will see that auth_id 456 is now queued for change as well. At this point, you can remove the heading from the queue and manually update records to differentiate them.
- Article last edited: 11/20/2013