1. CJK NACO Session Charlene Chou East Asia Library, University of Washington July 24 th, 2014

2. Agenda Goal & documentation Personal names Family names Geographic names Corporate/conference names Works/expressions Case studies--updating existing records

3. Goal & documentation Goal: – This session only emphasizes on the CJK specific issues & examples, esp. not covered by Adam’s training (PCC) Documentation: – CJK specific issues RDA & CJK Workshop – What’s new? – Q&A – 2014 CJK NACO training materials – 2013 CJK NACO training materials CJK NACO Project – CJK NACO Best practices CJK NACO Best practices – General DCM Z1 & DCM updates available from CDSDCM updates available from CDS MARC 21 encoding to accommodate new RDA elements 046 and 3XX in NARs and SARs (Word: 139 KB) Recommended interim PCC practice when giving 046 and 3XX data in NACO authority records MARC 21 encoding to accommodate new RDA elements 046 and 3XX in NARs and SARs

4. Personal names CJK specific issues and examples

5. 370 Form as of Sept. 2013 (DCM Z1) Use the authorized access point form as found 5

6. LC-PCC PS for 9.2.2.5.3 NAMES WRITTEN IN A NON-PREFERRED SCRIPT Language and script preferred by LC/PCC – For the instructions related to RDA 9.2.2.5.3, the language preferred by the Library of Congress for reference sources is English; the preferred script is the Latin script. Applicability – LC practice/PCC practice: Persons who bear names derived from a non-Latin script but who write in a Latin script language should not be treated under this instruction. The decision that the person is writing in a Latin script language is based on the first item cataloged, i.e., the fact that the text of this item was originally written in a Latin script language. If it becomes evident later that most of the person’s works were written in a non- Latin script, apply the provisions of this policy statement. Challenges: – Chinese authors writing in the Japanese language supplying WG romanization (together with original Chinese characters) in their publications, not involving any English form of the name

7. Example

8. Fictitious or Legendary person and Real Non- human Entities: Examples

10. Fictitious Entities & Real Non-Human Entities (9.0) Established only in the name authority file using RDA instructions When no LCSH authority record exists  Create a name authority record whether needed as a creator, contributor, or only for subject access When LCSH authority record exists  Create a name authority record if needed as a creator, etc. Submit a SACO proposal to cancel the heading (H193 sec. 14);  Optionally, create a name authority record if needed only for subject access. If a NAR is created, notify PSD or submit a SACO proposal to cancel the heading

11. Recording Other Designations Associated with Persons (9.6.1.9) Record an appropriate designation if none of the following attributes are sufficient or appropriate for distinguishing between two or more persons with the same name  Date, fuller form, period of activity, profession or occupation, term of rank, honour, or office Record the designation in a language preferred by the agency creating the data. Example – 100 0# $a Yaśodharā $c (Wife of Gautama Buddha) – 100 1# $a Zhong, Kui $c (Spirit) – 100 1# $a Yi, Mi-ok $c (Korean cuisine researcher)

12. Undifferentiated Personal Name 12 General Do not use code “b” in an RDA name authority record ; all personal name authority records coded RDA should be differentiated Do not add a new identity to an existing personal name authority record coded 008/32 “b” Instead, apply one of the following RDA attributes to create a unique authorized access point for the person being established (See RDA 9.19) DCM Z1 (2014 update 2): http://www.loc.gov/cds//PDFdownloads/dcm/DCM_2014- 02.pdf

13. Undifferentiated Personal Name Maintenance When information is found to distinguish a person included in an existing undifferentiated NAR: Create a new NAR for that person, add an indication that the person was formerly on an undifferentiated record (667 note) Transfer information pertaining to that person from the undifferentiated NAR If more than one identity remains in the undifferentiated NAR, and there is no sufficient info. in the NAR to create new NARs for each name, leave the NAR coded AACR2 13

14. Undifferentiated Personal Name 14 When only one identity is left on an undifferentiated NAR, in order to facilitate machine processing of authority record (e.g., matching, linking), take the following steps:  Assure that the undifferentiated NAR only contains info. relevant to the single identity remaining (e.g., 670)  Keep the following fixed fields unchanged:  Name (008/32): b (undifferentiated name)  Rules (008/10): c (AACR2)  Add in the MARC data field for Cataloging source:  040 ## … $d institution’s MARC code

15. Undifferentiated Personal Name If a differentiated NAR has not been created for the last identity:  Add a 667 field to the undifferentiated NAR: 667 ## $a Last identity on undifferentiated record; reported for deletion.  Report the undifferentiated NAR for deletion to naco@loc.gov; LC will create a new replacement NAR, add a 667 note to the new NAR, and delete the old record naco@loc.gov 15

16. Undifferentiated Personal Name If a differentiated NAR has been created for the last identity:  Add that information in the 667 note on the differentiated record to assure that a duplicate NAR will not be created: 667 ## $a Last identity on undifferentiated record; reported for deletion in favor of [LCCN of NAR].  Report the undifferentiated NAR for deletion to naco@loc.gov; LC will delete the NAR and add the LCCN of the deleted NAR in field 010 subfield $z of the newly created NAR naco@loc.gov 16

17. Undifferentiated NAR Example 17 Undifferentiated NAR

18. Undifferentiated NAR Example 18 New NAR for this identity

19. Undifferentiated NAR Example 19 Undifferentiated NAR, to be deleted

20. Undifferentiated NAR Example 20 Differentiated NAR created for the last entity

21. What Do We Do With Non-Latin Script References? 21 When updating a NAR containing multiple 4XX non-Latin script references  Adhere to the PCC guideline on undifferentiated authority records  Stop coding 008/32 Name using “b” as undifferentiated NAR  Remove all irrelevant and incorrect 4XX non-Latin script references  Update and convert the NAR to RDA with additional data elements if possible  Same apply with explicitly coded undifferentiated authorities  Do not delete or change:  667 Machine-derived non-Latin script reference project.  667 Non-Latin script references not evaluated.

22. Stage Names of Kabuki Actors (9.2.2.8 Exception) Use stage name as a preferred name  Choose the one that is most commonly known, and then the one appear most frequently in resources or reference if necessary Give the other stage names and real name as variants Different from author who writes under more than one pseudonym 22

23. Stage Names of Kabuki Actors Example (9.2.2.8 Exception) 23

24. Name authority records with “jin shi” ( 進士 ) or “ju ren” ( 舉人 ) Under RDA, these types of dates are treated as “period of activity” and can be used to distinguish one access point from another when no dates of birth/death or fuller form of name (usually not applicable to CJK names) are available. However, these types of dates can be retained in pre-existing authority records converted from AACR2 to RDA even when no conflicts exist. This is to minimize the need for bibliographic maintenance. If birth/death dates are available at the time of recoding (or later), record them in 046/670 field as appropriate without changing the form in 100 field

25. Example

26. Ancestral/family origin ( 籍貫 / 本籍 / 原籍 / 祖籍 ) These terms could mean ancestral/family origin, birth place, or residence of a person. Determine its nature based on readily available information and use appropriate terminology in 670 and corresponding 370 code to record the information. The following is recommended best practice: (Note: The below refers to geographic names below the country level.) 670: Use “native of ” or “ancestral home ” as appropriate. For example, for people from diaspora communities, if 祖籍 refers to the origin of one's ancestors and not the place directly relate to the person’s immediate family, use “ancestral home”. Record the information for ancestral home only if considered important. 370: – $a - Place of birth – $e - Place of residence – $f - Other associated place (Use when neither $a nor $e is appropriate.)

27. Treatment of 字 & 號 / 号 for personal names Recording data in 670 $b – A long-term practice for CJK cataloging has been to use abbreviations of romanizations to represent these terms, e.g., "t." (i.e., tzu; Wade- Giles romanization) or “z.” (i.e., zi; pinyin) to represent " 字 ", and "h." (i.e., hao) to represent " 號 / 号 " in Chinese names. However, the meanings of these abbreviations are not always apparent to other catalogers, especially non-native speakers. To address this issue, catalogers are encouraged to spell out the romanization and add the English translation in brackets. Example: – 字 : record as “zi [courtesy name] …” – 號 / 号 : record as “hao [alias] …” or “hao [pseudonym] …” as appropriate. – (Note: Use equivalent romanizations for Japanese and Korean terms.) Form of names in 400 fields – Traditionally, 字 is used in conjunction with one's family name even though it is usually not explicitly indicated in the texts. On the other hand, 號 / 号 is usually used without the family name, with few exceptions. – When providing cross references in 400 field for 字 and 號 / 号, follow this principle: Add the family name to 字 but not 號 / 号, unless examples for the contrary are found.

28. Other names Recording data in 670 $b – Use “original name” for 原名 – Use “pen name” for 筆名 – Use “other name” for 別名

29. Abbreviations in 670 $b--reading To facilitate understanding of non-native speakers, it is recommended that catalogers try to use spelled-out English terms when applicable, e.g., “reading” instead of just “r.” If it is necessary to use romanization to convey specific meanings, prefer spelled out form as well. For clarity, appropriate English terms may also be added in brackets. (Refer to Treatment of 字 & 號 / 号 for personal names above for examples.) Note: Do not abbreviate or translate attributes such as title of the person (RDA 9.4) that appear in conjunction with personal names.

30. Treatment of variant pronunciations of characters ( 多音字 ) Many Chinese characters (in all CJK languages) have multiple pronunciations and sometimes it is not clear which one to use for the authorized access point. Determine the form using a reliable reference source, or exercise your best judgment. If it is possible that others might search the name under another pronunciation, add a cross reference in 400 field for the variant form. Although it is not required to justify the source of variant pronunciations, it may be recorded optionally for the convenience of non-native speakers of the language. – Example 100 1# $a Xiao, Wupo, $d 1979- 400 1# $a 萧无陂, $d 1979- 400 1# $a Xiao, Wubei, $d 1979- 400 1# $a Xiao, Wupi, $d 1979- 670 ## … ( 萧无陂 = Xiao Wupo; variant pronunciations: Xiao Wubei, Xiao Wupi)

31. Family names

32. Family name: example

33. Royal house: example

34. Corporate/conference names

35. Choosing the Preferred Name (11.2.2.3) When choosing a preferred name for the corporate body, choose the name by which the corporate body is commonly identified 670 ## $a Jiangxi Kejia, 2011: $b t.p. ( 江西省赣州市博 物馆 = Jiangxi Sheng Ganzhou Shi bo wu guan) p. 1 ( 赣 州市博物馆 = Ganzhou Shi bo wu guan) Q: What is the preferred name? 35

36. Answer

37. Corporate Names Changes That Resume an Earlier Name (11.2.2.6 and 32) 37 Q: Do we need to create a new, separate NAR if a corporation reverts back to a previous preferred name?  MARC field 5XX is used to connect related bodies  All bodies related with 5XX must be separately established  Add qualifiers per 11.13.1 (place, associated institution, date, etc.)  Change from AACR2 Example: #1: Minami Manshū Tetsudō Kabushiki Kaisha. $b Tōa Keizai Chōsakyoku (1908-1929) #2: Tōa Keizai Chōsakyoku (Japan) #3: Minami Manshū̄ Tetsudō Kabushiki Kaisha. $b Tōa Keizai Chōsakyoku (1939-1945)

38. Conference Names Single Instance vs. Collective Conference (11.13.1.8) 38 Once an official name of a conference is chosen, the names for all NAR should have the same name. In other words, the authorized access point for the conference name of a single instance should be the same as the one chosen for the collective conference

39. Single Instance vs. Collective Conference (11.13.1.8) Exercise 39 Q: Please establish the authorized access point for the 7 th meeting of the conference.

40. Single Instance vs. Collective Conference Exercise Answer 40 Q: In the course of searching database, I found the NAR has been set up. Can I go ahead and use it for my bibliographic record? A: No. The name of the individual instance must be the same as the one for the collective conference.

41. International bodies (LC-PCC PS for 11.2.2.5.3) LC practice/PCC practice: If the name of an international body appears in English on resources associated with it, choose that form as the preferred name. Beijing International Film Festival ‡n (1st : ‡d 2011 : ‡c Beijing, China) vs. Beijing min zu dian ying zhan ‡d (2011 : ‡c Beijing, China)

42. Geographic names

43. LC-PCC PS for 16.2.2.12 RDA 16.2.2.12 option: – Record the name of a state, province, or highest-level administrative division preceding the name of the country. – Example Aba Zangzu Qiangzu Zizhizhou (Sichuan Sheng, China) Ipoh (Perak, Malaysia) LC practice/PCC practice for Alternative: – Apply the alternative only to places in Malaysia. Defer application to other countries until projects can be developed to change existing records. CEAL is more inclined to wait till LC test result for Malaysian names, so won’t apply this alternative to any new Chinese geographic names yet. J & K communities have major concerns on applying this alternative, esp. for the workload of implementation and maintenance issues.

44. ADM vs. PPL LC Workshop on Chinese geographic names in 2007 After Pinyin Conversion, the decision by the LC policy office (CPSO/PSD) is to treat the same geographic names as two entities, administrative district and populated place. For example, Xiamen was called as city traditionally, but is not the same for district called now. They are the same names in China but different from BGN forms. – NAR 1: Xiamen (Xiamen Shi, China) [PPL] – NAR 2: Xiamen Shi (China) [ADM2] If the corporate body is municipality in nature, nation in nature or state-wide or city-wide place, use ADM as qualifier. For a conference, it could be held in a convention center in the center city or in a resort at the outskirt of city, use populated place for qualifier. – 111 2# SNAM (Workshop) $d (2012 : $c Nanjing, Jiangsu Sheng, China) – 110 2# Nanjing pi lu si (Nanjing Shi, China)

45. ADM--example

46. PPL--example

47. Geographic name change

48. Romanization of ambiguous place names Example – 殷墟 (i.e., the extinct city of the Shang dynasty, China) Standard Romanization: Yinxu Established AAP: Yinxu (Extinct city) – Explanation: The Romanization in GeoNet is Yinxu. Even though section 2G of the ALA/LC Chinese Romanization Table states that "Terms for archaeological sites, bridges, and other constructions of geographic extent are capitalized and separated from the names themselves," no specific examples were given to represent archaeological sites. The word 墟 has been used as an integral part of the place name 殷墟 for a long time, so it makes more sense to treat the phrase as a two-character place name. Note: more examples will be added to this category later.

49. Taiwan place names Now, LC instructs us “in general if there is a conventional name established by BGN for a place in GeoNet, we should use the conventional name.” Conventional names were used (in BGN and authority records) for provincial and some city names in China prior to year 2000 (e.g., Peking, Canton, etc.), but now almost all Chinese place names are in standard pinyin romanization in BGN. It’s very likely that the current BGN practice for Taiwan place names may change in the near future. Evidently, using different romanization conventions for place names of the same country creates confusion for catalogers and users alike. CEAL is still communicating with LC, and hopes to use "Pinyin form" (unified practice) for all Taiwan place names in future. A recent update by LC: – LCCN: n 80163881 – cancelled AAP: ​ Hsin-chu hsien (Taiwan) – replacement AAP: Hsinchu County (Taiwan)

50. Works/Expressions Chapter 6

51. Works/Expressions NARs Exercise 51 Q: Should we consider creating authorized access points in the following situations and why? Bib. 1: 130 0# $a Shi jing. $l English. 245 14 $a The Classic of Poetry / $c translation with copious indexes, by James Legge. Bib. 2: 100 0# Laozi. 240 10 $a Dao de jing. $l English 245 10 $a Dao de jing …

52. Authorized Access Point for an Expression (6.27.3) Bilingual and Polyglot resources LC practice: record authorized access point for the work and authorized access point for the language of the translation Shan hai jing (Chinese classic) Shan hai jing (Chinese classic). $l Korean PCC catalogers may follow LC practice or may distinguish between expressions within the same language Shan hai jing (Chinese classic). $l Chinese $s (Yi) Shan hai jing (Chinese classic). $l Korean $s (Yi) 52

53. Intermediate Translations English translated from the Chinese version of a text originally in Sanskrit 100 1# Creator. $t Title in original Sanskrit. $l English 400 1# Creator. $t Title in English 430 #0 Title in English Do not add Chinese translation title in 4XX 53

54. Intermediate Translations Right now translation of a translation is not identified in the NAR, only in BIB using 041 $h and $k (intermediate translations), e.g. – 041 1# $a eng $k chi $h san 377 to possibly code for both the language of the expression ($a) and the language it was translated from (like bib 041 format) Issues on handling expressions will continue to evolve 54

55. DCM Z1 Instruction and 670 $b Best Practice 55 How would you construct the 670 $b? Note : the general principle—English paraphrasing of a corporate body name should provide clear understanding of the name without altering its definition or otherwise causing misunderstanding.

56. Case study Updating existing records: the complex process of searching and reseach

57. Part one: Korean form of author name is not in NAF

58. The record of Romanized form found in NAF

59. Updating Existing Record (After)

60. NACO Module 7—Making Changes to Existing Name & Work/Expression—Authority Records

61. Correcting errors in an existing record (before)

62. After