Advanced RDA CJK NACO Training

1. Advanced RDA CJK NACO Training Council on East Asian Libraries Annual Meeting March 24, 2014 Jessalyn Zoom Library of Congress

2. Learning Objectives At the end of the training, you will be able to: • Learn policy and guideline updates in the area of name authorities since March 31, 2013 • Gain in-depth understanding of RDA instructions on creating and updating the authorized access point in the areas of Identifying Persons, Corporate Bodies, and Works and Expressions • Learn how to exercise cataloger’s judgment when questions arise • Learn how to navigate RDA instructions and related documentations during the course of authority creation or updating existing authority records • Gain hands-on experience in working with LC/NACO Authority File

3. Agenda • Highlights of RDA Authorities since April 2013 • Identifying Persons • Identifying Corporate Bodies (Conferences) • Identifying Works and Expressions • Applying Relationship Designators • Practicum Note: what will be covered in this training are the updates since April 2013 and best practices , not the fundamentals already addressed in the LC RDA training material on Authorities

4. Pop Quiz : Self-assessment • I can add geographic subdivision in the 372 for field of activity. • I should keep the undifferentiated NAR coded AACR2 if I need to use it in my bibliographic record and do not have more information to add to the undifferentiated NAR. • The conference name of the individual instance varies thus the authorized access point for single instance is not always the same as the one chosen for the name of the collective conference. True or false? True or false? True or false?

5. Pop Quiz : Self-assessment • My institution’s practice allows for additional characteristic other than language to be added to the expression NAR, so I can update the existing NAR to do so. • The preferred title of the work is always the original title in the original language. True or false? True or false?

6. Pop Quiz : Self-assessment • If you did not get most of questions correctly, the workshop is definitely right for you • If you answered most of the questions correctly, it’s your opportunity to ask questions and share your knowledge with others and help others in the workshop • We’re all in this together!

7. Documentations • RDA Toolkit & LC-PCC PSs • Descriptive Cataloging Manual (DCM) Z1 • Post RDA Implementation Guidelines and Standards http://www.loc.gov/aba/pcc/rda/PCC%20RDA%20guidelines/Post-RDA-Implementation-Guidelines.html

8. We’re Not Covering Series Authorities • PCC Series Policy Task Force Interim Report submitted for PoCo to review • DCM Z1 64X Series Treatment Section will be updated to indicate “documentation will be changed when the PCC makes new SAR policies in the context of RDA” in April update of the Cataloger’s Desktop • We’ll discuss choosing preferred title which is considered as one type of series (at least in AACR2, uniform title was considered series)

9. Identifying Persons (Chapter 9)

10. Date Information for Persons (9.3.1.3, 9.19.1.3) • When no conflict, can I create a new AAP with more complete date information? • Generally do not add more complete date information in the authorized access point reserving that for conflict • Record a more complete date in MARC field 046, if considered important • Let’s take a look at the RDA Toolkit

11. Date Information for Persons (9.3.1.3, 9.19.1.3) Example

12. Date Information for Persons (9.3.1.3, 9.19.1.3) • When conflict , • Can use [year][month] alone, or [year][month][day] • Use English spelled-out form for the month in access point Examples: Zhang, Tong, $d 1978 October- Kang, Sang-gyu, $d 1965 January 16-

13. Recording Period of Activity of the Person (9.3.4.3, 9.19.1.5) • RDA CORE ELEMENT: Period of activity of the person is a core element when needed to distinguish a person from another person with the same name • Treatment of certain CJK terms, e.g., jin shi, ju ren is different from AACR2 • What to do when updating AACR2 NARs with jin shi date, etc.?

14. Recording Period of Activity of the Person (9.3.4.3 & 9.19.1.5) Original AACR2 record:  100 1# Chen, Hao, $d jin shi 1724 670 ## …. (…1695-1772; jin shi 1724) Updated RDA record: 008/10 (Rules): z 040 ## … $e rda … 046 ## $f 1695 $g 1772 100 1# Chen, Hao, $d jin shi 1724 670 ## …. (…1695-1772; jin shi 1724) *May optionally add other relevant RDA elements

15. Qualifying Name with (Author)? (9.16.1.3) • RDA 9.16.1.3 Recording Professions or Occupations includes a list of term including “Author, Folklorist, Anthropologist” What do you think of the following examples? NAR 1: 100 1# Chang, Lin $c (Author) NAR 2: 100 1# Zhang, Ting $c (Young adult author) • Best practice: Avoid using terms that do not help to differentiate identities. Use cataloger judgment when providing a qualifying term.

16. What’s More in 374 Occupation? (9.16) • Is this 374 field correctly formulated? 374  Research assistant $s August 2010 $t 2012 • Date in the 37x fields also needs to follow ISO format: 374  Research assistant $s 2010-08 $t 2012

17. What’s More in 374 Occupation? (9.16) • Best practice: Avoid LCSH terms that indicate the gender or ethnicity of persons engaged in an occupation, unless this aspect is considered important 374 $a Accountants Not 374 $a Women accountants 374 $a Lawyers Not 374 $a African American lawyers

18. What’s More in 374 Occupation? (9.16) • If they are available, prefer terms for wider professions or occupations over terms for specific posts or positions 374 $a Librarian rather than 374 $a Authority Control team leader

19. What’s More in 374 Occupation? (9.16) • What do you think of these two following options? 370 $f Nagasaki-shi (Japan) 374 $a Elementary school teachers OR 374 $a Elementary school teachers--Japan--Nagasaki-shi (Japan--Nagasaki-shi is a valid geographic subdivision) • Best practice: Keep the attributes “clean” when using subdivisions in $2 lcsh

20. 372 exercise (9.15) • How do you evaluate the 372 field in this record?

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

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

23. Fictitious or Legendary person and Real Non-human Entities (9.6.1.7, 9.6.1.8) • Fictitious or Legendary person: record Fictitious character, Legendary character, or another appropriate designation • Real Non-human Entities: record a designation for type, species, or breed

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

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

26. Fictitious Entities & Real Non-Human Entities (9.0) • Established only in the name authority file using RDA instructions •  No LCSH authority record exists • Create a name authority record whether needed as a creator, contributor, or only for subject access • LCSH authority record exists • Create a name authority record if needed as a creator, etc.. Notify PSD (policy@loc.gov) or 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

27. Fictitious Entities Example

28. 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 • Choose a term that is sufficiently specific to distinguish the person from other persons with the same name • Record the designation in a language preferred by the agency creating the data (English for NACO catalogers)

29. Recording Other Designations Associated with Persons (9.6.1.9) RDA examples 100 1# $a Chen, Feng $c (Writer on Chinese art) 100 1# $a Yi, Mi-ok $c (Korean cuisine researcher) 100 1# $a Zhong, Kui $c (Spirit)

30. Undifferentiated Personal Name 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) http://www.loc.gov/aba/pcc/rda/PCC%20RDA%20guidelines/Z01%20008%2032%202014rapril.pdf

31. Undifferentiated Personal Name Maintenance • When information 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

32. Undifferentiated Personal Name • 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

33. 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

34. 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

35. Undifferentiated NAR Example Undifferentiated NAR

36. Undifferentiated NAR Example Undifferentiated NAR

37. Undifferentiated NAR Example This NAR remains coded as AACR2 “c” Undifferentiated NAR

38. Undifferentiated NAR Example Undifferentiated NAR

39. Undifferentiated NAR Example New NAR for this identity

40. Undifferentiated NAR Example Undifferentiated NAR, to be deleted

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

42. Undifferentiated NAR Exercise Title in hand: 野生的红高梁 T.p. (叶开) Bio. Data (also wrote秘密的蝴蝶 (Mi mi de hu die))

43. What Do We Do With Non-Latin Script References? • 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.

44. Individual With More than One Identity (9.2.2.8 Exception) • If an individual uses only one pseudonym and does not use his or her real name as a creator or contributor, choose the pseudonym as the preferred name • LC-PCC practice: If an authorized access point is needed for a bibliographic identity recorded as a variant name in a 400 field in an existing name authority record, create a separate RDA name authority record for that identity. Modify the existing authority record to convert the 400 field to 500 field

45. Individual With More than One Identity (9.2.2.8 Exception) Author originally wrote only under “Sting” 1 NAR: 100 0# Sting $c (Musician) 400 1# Summer, G. M. Author started to also publish under “Summer, G. M later on NAR 1: 100 0# Sting $c (Musician) 500 1X Summer, G. M. NAR 2: 100 1X Summer, G. M. 500 0# Sting $c (Musician)

46. 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

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

48. 500 See Also From Tracing – Personal Name (DCM Z1) • An addition should be made to either the 400 or 100 when a variant name (400) and an authorized access point (100) are in conflict • When encountering a variant form in a 500 field during the course of updating a NAR, resolve the conflict and change the field to a 400 • Available attributes: 9.1.9.1.2-9.19.1.7

49. 500 See Also From Tracing – Personal Name Exercise Q: What should you do in the course of updating one of the NARs?

50. Coding Variant Access Point When AACR2 NAR is evaluated to RDA • Make a see reference for the old valid form of heading, with $w nnea, unless the reference itself is a valid RDA variant access point, in which case use $w nne.  In case of doubt, use $w nnea • Don't forget about NACO Normalization! NAR 1: 100 1# Jobs, Steve, $d 1955-2011 400 1# Jobs, Steve, $d 1955- $w nne NAR 2: 100 1# Cho, Sin-sŏng, $d 1874-1953 400 1# Cho, Sin-sŏng, $d b. 1874- $w nnea