How will I know if a record has been pre-populated with non-Latin script references?
A8. Name authority records that have been through the pre-population process will initially exhibit several characteristics: 008/29 (Reference evaluation) will be set to value ‘b’ (Tracings are not necessarily consistent with the heading); a 667 field (Nonpublic general note) will indicate that non-Latin references have been added programmatically (the note will read: Machine-derived non-Latin script reference project.”); an additional 667 note will be added to indicate that the non-Latin script references have not been evaluated; non-Latin references will be found in field 4XX; 670 (Source found) citations will not be made. After the initial pre-population, catalogers will be able to add 670 citations, and will be able to add, modify, or delete non-Latin references, but all records with non-Latin script references should continue to have 008/29=b.
Related Questions
- If I create a new authority record with a romanized heading, am I required to add non-Latin script data to the authority record?
- How long will it take to pre-populate the authority file with non-Latin script references?
- How long will it take to pre-populate the authority file with non-Latin script references?
- How will I know if a record has been pre-populated with non-Latin script references?
- Can I ‘evaluate’ non-Latin script references on name authority records?
- Can I ‘evaluate’ non-Latin script references on name authority records?
