CJK NACO Best Practices CJK Pseudonyms Best Practices on Non-Contemporaries (update) Recording occupational terms in 374: prefer LCDGT over LCSH if available Recording date of “jin shi” (進士) or “ju ren” (舉人) in 046$s Determining AAP of Chinese or Korean personal names appearing in Japanese publications “From a linked data perspective, LCDGT will generally be a better controlled vocabulary, where appropriate, since it does not “mix” terms like LCSH can. For example, in LCSH:   African American women chemists  That is a mix of ethnicity, gender, and profession/occupation. In LCDGT, the three terms are separate (although they also are separate in LCSH) but there is no mixing of the terms: African Americans Women Chemists” Updates provided by Shi Deng, CJK NACO Project Coordinator Mieko Mazza and Japanese NACO Reviewer Group In collaboration with members of the CJK NACO Reviewer Group 2019 CEAL Cataloging Workshop March 19, 2019

Recording occupational terms in 374: prefer LCDGT over LCSH if available From a linked data perspective, LCDGT will generally be a better controlled vocabulary, where appropriate, since it does not “mix” terms like LCSH can. For example, in LCSH: African American women chemists  That is a mix of ethnicity, gender, and profession/occupation. In LCDGT, the three terms are separate (although they also are separate in LCSH) but there is no mixing of the terms: African Americans Women Chemists From Paul Frank, shared by Chiharu Watsky

Recording date of “jin shi” or “ju ren” in 046 $s CJK NACO Best Practice, use 046$s for date of “jin shi” or “ju ren” Under RDA instruction 9.19.1.5, the date of “jin shi” (進士) or “ju ren” (舉人) is considered as a period of activity of a person Distinguish one authorized access point from another when the person's date of birth or date of death is not available MARC 21 on 046 defining $s as Earliest date in a period of activity, and In consultation with Paul Frank, PCC NACO Coordinator Examples: LCCN nr2003032497 (DLC-R) 046  ǂs 1676 1001 Guo, Wenbing, ǂd jin shi 1676 LCCN no2003050966 (HkUST) 046 ǂs 1826 ǂ2 edtf 1001 Bao, Zuoyu, ǂd ju ren 1826

Romanization of Chinese or Korean personal names appearing in Japanese publications Mieko Mazza (Stanford University) Prepared by Japanese NACO Reviewer Group in consultation with Hideyuki Morimoto (Columbia University) 2019 CEAL Cataloging Workshop, March 19, 2019

Romanization of Chinese or Korean personal names appearing in Japanese publications Cataloging Service Bulletin(CSB), No. 24 (Spring 1984), p. 24 https://www.loc.gov/cds/PDFdo wnloads/csb/CSB_024.pdf CSB No. 24, p. 24 (Spring 1984) provides instructions for DESCRIPTIVE cataloging. Cite forms in 670 Follow RDA 9.2.2.2 in order to determine the form of AAP CSB, no.24, p. 24: Acknowledgement: This slide was previously provided by Shi Deng, CJK NACO Project Coordinator in collaboration with members of the CJK NACO Reviewer Group at CEAL 2018 Cataloging Workshop, held on March 20, 2018. CSB No.24, p.24 is for bibliographic description. It is not meant to be used for authority record formulation.

(1) Chinese personal name Author’s name appears in Chinese characters and in Chinese and Japanese reading (first entry in OCLC; no other publication information available) Title page Title page: 鄒庭雲

(1) Chinese personal name Author’s name appears in Chinese characters and in Chinese and Japanese reading (first entry in OCLC; no other publication information available) cont. Colophon Colophon: 鄒庭雲 (すう・ていうん Zou Tingyun) Zou Tingyun

(1) Chinese personal name Author’s name appears in Chinese characters and in Chinese and Japanese reading (first entry in OCLC; no other publication information available) cont. LCCN no2019023673 RDA, 9.2.2.5.2, paragraph 3: “If the form of name chosen is in a script that differs from a preferred script of the agency creating the data, apply the instructions at 9.2.2.5.3.” Then, RDA, 9.2.2.5.3, paragraph 4: “If a name of person is found in more than one transliterated form in manifestations associated with the person, choose the form that occurs most frequently.” Kana transliteration: すう・ていうん [appearing once] Roman alphabet transliteration: Zou Tingyun [appearing twice--on line 1 and also toward the bottom under copyright information] Therefore, the form of "Zou Tingyun" that appears more often is chosen.

(2) Chinese personal name Author’s name appears only in Chinese characters and Romanization (no Japanese reading is given) Title page Title page: 李春霞 Li Chunxia Author’s name in Chinese character

(2) Chinese personal name Author’s name appears only in Chinese characters and Romanization (no Japanese reading is given) cont. Colophon: 李春霞 李春霞 (LI CHUNXIA) Li Chunxia

(2) Chinese personal name Author’s name appears only in Chinese characters and Romanization (no Japanese reading is given) cont. LCCN no2019025055  As long as both forms of the name appear at the same frequency inside the manifestation cat. and as long as the manifestation cat. is the sole resource used, then, the provision RDA, 9.2.2.5.3, para. 2: “If a name is found in more than one non-preferred script, transliterate it according to the scheme for the original language of most of the works.” does NOT apply.  Name is found in:   non-preferred script:             李春霞 preferred script [Latin script]:  LI CHUNXIA Therefore, in reference to: LC-PCC PS, 9.2.2.5.3: For the instructions related to RDA 9.2.2.5.3, ... the preferred script is the Latin script.

(3) Chinese personal name Author’s name appears only in Chinese characters (reading not given) RDA9.2.2.5.2: “If a person’s name has appeared in different language forms in manifestations associated with the person, choose as a preferred name the form that corresponds to the language of most of the manifestations.” LCCN n 2012016601 Son, Hishū, 1970- 670  Tenkanki o mukaeru Higashi Ajia no kigyō keiei, 2011: ǂb t.p. (孫飛舟 = Son Hishū) From LC bibl.: https://lccn.loc.gov/2011528240 Tenkanki o mukaeru Higashi Ajia no kigyō keiei : soshiki inobēshon to senryaku tenkan / Son Hishū hencho. 転換期を迎える東アジアの企業経営 : 組織イノベーションと戦略転換 / 孫飛舟編著.

(4) Korean personal name Author’s name appears only in Chinese characters (Korean reading is given) Made-up example RDA9.2.2.5.2: “If a person’s name has appeared in different language forms in manifestations associated with the person, choose as a preferred name the form that corresponds to the language of most of the manifestations.” Title page:      姜 賢 colophon:      姜 賢                   カン ヒョン [no romanized form]   --> preferred name:  Kan, Hyon

(5) Korean personal name Author’s name appears in Chinese characters and Romanization (Korean reading is given)

(5) Korean personal name Author’s name appears in Chinese characters and Romanization (Korean reading is given) cont.

(5) Korean personal name Author’s name appears in Chinese characters and Romanization (Korean reading is given) cont. LCCN: n 2017040676 670 (Source Data Found) Citations for Name Authority Records with Non-Latin Script (http://www.loc.gov/catdir/cpso/non-Latin670.pdf) 2. In 670 $b, use the equals sign to equate the found non-Latin script form found on the item to the systematically romanized form (or to another supplied non-Latin form, e.g., Hangul characters supplied for a Korean entity represented only by Chinese characters in the source). ... 670 $a Han'gukhwa non, 1989: $b t.p. (金 鍾太 = 김 종태 = Kim Chongt'ae) (Korean entity that appears only in Chinese characters; additional Hangul reading and systematically romanized forms supplied following equals signs) *** DCMZ 1 670 page 3 (https://www.loc.gov/catdir/cpso/dcmz1.pdf) Data must be given in romanized form. Normally it is understood that the cataloger has provided the romanization; therefore, when transcribing romanization found in the source, add after it the bracketed phrase [in rom.]. In such languages as Arabic and Hebrew, where vowels are commonly omitted from the orthography of texts, the cataloger supplies the missing vowels when transcribing data. When transcribing text that does include the vowels, add after it in brackets [voc.] or [part voc.] as appropriate. If a cataloger chooses to provide nonroman script variant access points, the 670 $b should contain both the nonroman script transcription(s) found in the source, and the systematically romanized form(s). Example: 670 ## $a Seun sangga kŭ isang, 2015: $b t.p. (세운 상가 = Seun Sangga) Hancha to Hangul : http://hanja.suminb.com/ Hangul to Hancha : https://hanjaro.juntong.or.kr/text_translater.aspx?hh=2&hu=1&hl=111111111