Non-LatinScripts:CULGuidelines

Non-Latin Script Data in name Authority Records: CUL Guidelines

July 21, 2008

Scope: Until further notice, please follow these instructions when recording non-Latin script data in name authority records (NARs). For more complete and authoritative information, see the Library of Congress FAQ at: http://www.loc.gov/catdir/cpso/nonlatinfaq.html. You may also direct questions to David Banush or Jim LeBlanc.

1. Beginning July 22, 2008, NACO catalogers may optionally add non-Latin script data to new name authority records and certain pre-existing NARs.

   CUL policy: We will add non-Latin script data only to new corporate and personal name authority records. When the pre-population period has ended, we will re-evaluate this policy.

2. Languages: Chinese, Japanese, and Korean only.
3. Existing NARs: Do not touch existing records unless pre-population of that record is complete or until the pre-population period is over. Pre-populated records will contain the 667 notes: ?Machine-derived non-Latin script reference project? and "Non-Latin script reference not evaluated." LC will let us know when the pre-population period has ended.
         
           Note: If pre-population of an existing record is complete, do not edit or delete programmatically-added 4XX data unless the error is obvious (e.g., a typo) or the reference has clearly been added to the wrong NAR.
4. New NARs: Add non-Latin script and other data according to the instructions in #5
5. Data: Add non-Latin script data to 4XX, 667, 670, and 675 fields only, as appropriate. Do not record non-Latin script data in any other field (no 880 fields!). Follow existing guidelines in AACR2 21-26, LCRI 21-26, and the MARC21 Authority Format.
6. Normalization: Do not record a 4XX that would normalize to the same form of another reference on the same NAR. By definition, non-Latin references will not conflict with authorized headings (1XXs) on other NARs.
7. Reference evaluation: Code fixed field byte 008/29 as ?b? (tracings not necessarily consistent with heading) in all NARs containing non-Latin script. This byte is labeled ?Ref Status? in OCLC and ?Reference Evaluation? in Voyager. You must also add the 667 note ?Non-Latin script reference(s) not evaluated? to any new NAR you create that contains vernacular characters.
8. Workflow: Creation of new records and updates to existing records (when permitted -- see #3) should be done in OCLC only. Do not export the authority records to Voyager. We will receive the record with the vernacular references about two weeks after the record has been produced by OCLC and distributed by LC.