CJK NACO Webinar Series – Supplement to the PCC NACO Training Describing Persons and Families Welcome remarks.

Goals of the Webinar Discuss and understand authority work in challenging areas as well as issues pertaining to CJK language materials Goal of training: not intended a systematic review of the general NACO training in CJK context. Rather, it will focus on areas appear to be most problematic or challenging as well as topics relevant to CJK cataloging. Some topics may overlap with Paul’s presentation.

Outline of the Webinar Scope of persons (and family names) Choosing forms for preferred names Non-Latin Script Reference Guidelines Different names Core elements for persons New MARC fields in RDA Undifferentiated personal names Variant access points Family names Relationships between persons, families, and corporate bodies

Scope of Persons: Fictitious and Real Non-human Entities (9.6.1.7-8) Individual fictitious and legendary characters, real or fictitious non-human entities established in Name file 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 Describing Persons (RDA 8 &9): Definition and scope of persons

Fictitious and Real Non-human Entities (9.6.1.7-8)

Fictitious or and Real Non-human Entities

Choosing the Preferred Name: Different Forms of the Same Name (9.2.2) Choose the most commonly found form as the preferred name; if no predominant form, choose the latest form as the preferred name, choose an earlier name if it’s better known; record the other forms as variant names – optional Note: person’s preference trumps cataloging decisions

Choosing the Most Commonly Found Form Example

Transcription of Non-Latin Forms (LC PCC PS 8.4) Record a transliterated form of the name in authorized access points (AAP) by following ALA-LC Romanization Tables. http://www.loc.gov/catdir/cpso/roman.html Cataloger’s Desktop (via subscription) Non-Latin forms that appear on the source may be recorded as variant access points in authority records (4XX)

Non-Latin Script Reference Guideline http://www.loc.gov/catdir/cpso/nonlatingeneral.html Non-Latin scripts are allowed in 4XX, 670, and 675 fields OCLC’s Pre-population Project Adding non-Latin script data is optional No-Latin characters in name authority records

Non-Latin Script Example Ref status – Tracings are not necessarily consistent with the heading

Updating 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.     Pre-Population of the LC/NACO Authority File The result of the Pre-Population Project.

Updating NAR with Non-Latin Script Reference Example 李殿富: not the same person represented in the NAR. 李殿福 李殿福 李殿福 李殿福

Updated NAR with Non-Latin Script Reference Example Updated NAR for 李殿福

Convention of Recording 670 Field (Japanese record) 670 ## $a Kindai Nihon ni okeru shussan to ubuya, 2016: ǂb t.p. (伏見裕子 = Fushimi Yūko) colophon (r; b. 1983; researcher, Sekai Jinken Mondai Kenkyū Sentā) 670 ## $a Hābādo Purojekuto Zero no geijutsu ninchi riron to sono jissen, 2014: ǂb t.p. (池内慈朗 = Ikeuchi Itsurō [in rom.]; Ph.D.) colophon (b. 1957; prof., Saitama Daigaku Kyōiku Gakubu; prof., Tōkyō Gakugei Daigaku Hakushi Katei Gakkō Kyōiku Rengō Daigakuin) Kana reading

Convention of Recording 670 Field (Korean record) 670 ## $a Yunmi ne chip, 1990: ‡b t.p. (전 몽각 = Chŏn Mong-gak; Jeon Mong Gag [in rom.]) p. 152 (全 夢角; b. 1931 in P'yŏngbuk Yongch'ŏn; grad., Sŏul Taehakkyo Kongdae T'omok Konghakkwa; prof., Sŏnggyun'gwan Taehakkyo T'omok Konghakkwa; member, Hyŏndae Sajin Yŏn'guhoe) 670 ## $a Hyŏndaein ŭl wihan Pulgyo, 1981: ‡b t.p. (金 知見 = 김 지견= Kim Chi-gyŏn) colophon (b. 1931; head, Taehan Chŏntʻong Pulgyo Yŏnʼguwŏn)

More Than One Identity (9.2.2.8) If an individual has more than one identity, choose the name associated with each identity as the preferred name for that identity Use subfield $i and “r” in subfield $w when recording pseudonymous relationships for personal names in cases where a person uses one real name and one pseudonym  In all other cases involving pseudonyms, continue to follow the guidance provided in the FAQ – LC/PCC practice for creating NARs for persons who use pseudonyms: http://www.loc.gov/catdir/cpso/pseud.pdf Different names for the same person – a person has changed his or her name; a person has more than one identity.

One pseudonym, one real name Pseudonym Example One pseudonym, one real name Author writes under both real name and pseudonym. Establish two headings. Contemporary author: Three or more names (multiple pseudonyms). Create NARs for each name, choose a “basic” heading, provide 663 field for each NAR, use linking 5XX references coded $w nnnc NOTE: The basic heading does not have to be the person’s “real” name. It should be the most predominantly used name. Multiple Headings—References 2) If more than two headings are created for an author, choose a “basic” heading according to the above guidelines. On the authority record for this heading, trace cataloger-generated see also references from all other headings used, justifying the references in 670 citations, according to normal practice. Provide a 663 cataloger-generated reference field listing all the other names established with the following text: For works of this author entered under other names, search also under: [list names]. On each of the other authority records created for the author, trace a cataloger-generated see also reference from the "basic" heading, justifying that reference in a 670 citation, according to normal practice. (Other names may be mentioned in the 670 if it is convenient to do so.) Provide a 663 cataloger-generated reference field with the following text: Works by this author are entered under the name used in the item. For a listing of other names used by this author, search also under: [basic heading]. When the author uses another new name, create a new name authority record for that name and also add it to the reference structure and 663 listing on the authority record for the "basic" heading. (Do not add information about it to the authority records for other names used by the author.)

More than two names – choose a “basic” hdg. Pseudonym Example More than two names – choose a “basic” hdg. Note the coding and field $663

More than two names – other heading #1 See Also reference: Pseudonym More than two names – other heading #1 This is a record for one of the other names. If author begins to write under another name create an NAR for that heading and add name to the base heading. The 663 in this record points back to the “basic” heading which includes references to all of the names used by this person. The same 663 field would be used on each of the NARs that isn’t the “basic” heading.

Core Elements for Persons (RDA 8.3, 9.19.1.2-9.19.1.8) Always record if the information is known Title of the person (a word or phrase indicative of royalty, nobility, ecclesiastical rank or office, a term of address for a person of religious vocation) Date of birth Date of death Other designation associated with the person Profession or occupation* Identifier for a person When recording data identifying a person, include as a minimum these elements if they are applicable and readily ascertainable. Record the elements either as parts of the authorized access point representing the person or as separate elements, or as both. * In case of no conflict, “core” only for a person whose name consists of a phrase or appellation not conveying the idea of a person.

Core Elements for Persons (9.19.1.2-9.19.1.8) Record if necessary to distinguish Title of the person (another term indicative of rank, honor, or office) Fuller form of name Profession or occupation Period of activity of the person

MARC 046, Special Coded Dates (RDA 9.19.1.3, DCM Z1 046) Use EDTF (Extended Date Time Format) schema in all cases except for centuries Supply dates using the pattern, yyyy, yyyy-mm, or yyyy-mm-dd Always add subfield $2 edtf except after a century The more consistent use of $2 edtf is based on a PCCLIST discussion suggestion to simplify the use of $2 (always use except for centuries).

MARC 046, Special Coded Dates (RDA 9.19.1.3, DCM Z1 046) Examples: 046 ## $f 1884-10-11$g 1962-11-07 $2 edtf 046 ## $f 1946-06 $2 edtf 046 ## $f 1960 $2 edtf 046 ## $s -0199~ $2 edtf 046 ## $f 1861? $2 edtf 046 ## $f [1666,1667] $2 edtf But: 046 ## $s 20  Cataloger’s Desktop 2015 Issue 3 release in Sept. 2015 included this update. -0199~ : RDA dates (Approximately 199 B.C. - Approximate date 200 B.C. 1816? : RDA dates (1861?) - Probable date [1666,1667] : RDA dates (1666 or 1667) - Known to be one of two years 19 : RDA dates (20th century) - Century 19: 20th century (RDA dates in ISO 8601 date scheme (no need to provide a source in $2)

MARC 046, Special Coded Dates (RDA 9.19.1.3, DCM Z1 046) 046 fields in existing NARs will be reformatted to conform to the new DCM Z1 guidelines during Phase 3B changes

MARC 046, Special Coded Dates (RDA 9.19.1.3, DCM Z1 046) Two new subfields not yet implemented by NACO: $q Establishment date $r Termination date Continue to use $s (Start period) for date of establishment and $t (End period) for date of termination Before these changes can be implemented, NACO will need to make a programmatic change to the subfield coding of many existing name authority records. There will be announcements made when the NACO nodes have implemented the new subfields and changes have been made to legacy records. We do not expect these changes to the 046 to be made until after the Phase 3B updates to the NACO authority file. Until further notice do not use subfields $q - Establishment date or $r - Termination date,  continue to use subfield $s and subfield $t for start and end periods for corporate bodies.

368 Other Attributes of Person or Corporate Body (9.19.1.8) $a - Type of corporate body 368 $a Conference $b Type of jurisdiction 368 $b County $c Other designation 368 $c Spirit 368 $c Saint $d Title of person DCM Z1: Prefer controlled vocabulary for terms in subfield $a, $b, and $c, recording the source in $2. For consistency, capitalize the first term in each subfield $a, $b, and $c. You may code these new subfields in NACO records where appropriate, exercising your cataloger’s judgment on whether to add them. They are not required. 27

368 Other Attributes of Person or Corporate Body (9.19.1.8) 368 $a, $b and $c: Prefer controlled vocabulary for terms, recording the source in subfield $2. For consistency, capitalize the first term in each subfield $a, $b and $c 368 $d (R) Title of person : Designation indicative of royalty, nobility, or ecclesiastical rank or office, or a term of address for a person of religious vocation. Best practice: Record titles of royalty, nobility or religious rank in the form used in the authorized or variant access points DCM Z1: Prefer controlled vocabulary for terms in subfield $a, $b, and $c, recording the source in $2. For consistency, capitalize the first term in each subfield $a, $b, and $c.

368 Other Attributes of Person or Corporate Body Examples (9.19.1.8) 100 0# Akiko, $c Princess, daughter of Tomohito, Prince of Mikasa, $d 1981- 368 ## $d Princess, daughter of Tomohito, Prince of Mikasa 100 0# Huike,$c da shi, $d 487-573 368 ## $d da shi 100 1# Chu, Tony $c (Fictitious character) 368 ## $c Fictitious characters $2 lcsh 374 Detectives $a Psychics $a Chinese Americans $2 lcsh 100 0# Kiritsubo, $c Emperor of Japan (Fictitious character) 368 ## $d Emperor of Japan 374 ## Emperors $2 lcsh $a - Type of corporate body $b Type of jurisdiction $c Other designation $d Title of person

370 Associated Place (9.8-11) Use the authorized access point form as found. The form may differ from the form of place name added to a preferred name of place or an access point. If no NAR exists in the LC/NACO Authority File for the jurisdiction, it is not necessary to create a NAR in order to code the 370 field Form of name in NAF: 151 ## $a Jiangsu Sheng (China) Form of name in 370: 370 ## $a Jiangsu Sheng (China) $2 naf Form of name as an addition in an access point: 110 2# $a Zhong gong Taizhou Shi wei (Jiangsu Sheng, China) Form of name as part of preferred name of a local place: 151 ## $a Changzhou (Jiangsu Sheng, China) DCM Z1: For jurisdictions or other place names with authority records in the LC/NAF, use the authorized access point form as found. The form of place name in 370 may differ from the form of place name added to a preferred name of place or an access point per RDA and LC-PCC PS instructions. 30

370 Associated Place (9.8-11) For non-jurisdictions prefer names from an authorized vocabulary such as LCSH; if not found in an authorized vocabulary, record it in 370 without giving $2 Geographic name in LCSH: 151 ## $a Hisaka Island (Japan) Form of name in 370: 370 ## $a Hisaka Island (Japan) $2 lcsh 370 use place name during the time the person was associated 370 $f for “XX 人,” “原/祖籍 …” 370 ## $a Singapore $f Chaozhou Shi (China) $2 naf 670 ## $a … p. 4 of cover (b. 1942 in Singapore, native of Chaozhou … ) 370 $f for “XX 人,” “原/祖籍 …” Use $f other associated place. Also, $c associated country is encouraged to use. 31

371 Address (9.12) Do not record physical addresses for living people If recorded, at the minimum subfield $m (Electronic mail address) or subfield $b (City) for OCLC program validation purpose Justify at end of 371 field or in 670 field DCM Z1 -Best practice: Supply based on cataloger's judgment, if the information is readily available and not already being recorded in field 370 subfield $e (Place of residence/headquarters).• In cases where subfield $a is not recorded, include at a minimum subfield $m (Electronic mail address) or subfield $b (City).• Do not record physical addresses for living people.• Catalogers are not required to maintain address information when updating a record that contains an address. 32

372 Field of Activity (9.15) Prefer controlled vocabulary, such as LCSH or MeSH, record the source in subfield $2 Capitalize the first term in each subfield $a Overall best practice: Repeat the MARC field when needed for clarity Geographic name in LCSH: 151 ## $a Southeast Asia $x Foreign relations $z China Form in 372: 372 ## $a Southeast Asia--Foreign relations--China $2 lcsh Topical term in LCSH: 150 Korean language $x Foreign words and phrases 372 ## $a Korean language--Foreign words and phrases $2 lcsh For personal names, prefer a controlled vocabulary, such as the LC/NACO Authority File.  For corporate/conference names, follow the instructions in RDA 11.5. 33

374 Profession or Occupation (9.16.1.3, 9.19.1.6) Prefer controlled vocabulary, capitalize first word of the term in each subfield $a, and record the source in subfield $2 When terms do not come from a controlled vocabulary, use a singular form When recording a profession or occupation term in 100 subfield $c, use a singular form Overall best practice: Repeat the MARC field when needed for clarity

What’s More in 374 Occupation? (9.16.1.3) August 2016 release: Use terms without indication of the person’s gender, nationality, religion, etc., unless such characteristics are part of the definition of the term itself Prefer gender-neutral terms to gender-specific terms when possible Information not included as part of the profession or occupation term may be appropriate for other elements, such as Other designation associated with the person (9.6.1.9) 374 ## $a Novelists $2 lcsh Not 374 ## $a Novelists, Japanese $2 lcsh Not 374 ## $a Women novelists $2 lcsh LC-PCC PS

373 Associated Group (9.13) Prefer a controlled vocabulary, such as the LC/NACO Authority File Overall best practice: Repeat the MARC field when needed for clarity 110 2# $a National University of Singapore 373 ## $a National University of Singapore $2 naf 110 2# $a Waseda Daigaku. $b Kokusai Gengo Bunka Kenkyūjo 373 ## $a Waseda Daigaku. Kokusai Gengo Bunka Kenkyūjo $2 naf 110 2# $a Yurŏp Munhwa Chŏngbo Sent’ŏ (Yŏnse Taehakkyo) 373 ## $a Yurŏp Munhwa Chŏngbo Sent’ŏ (Yŏnse Taehakkyo) $2 naf 36

375 Gender (9.7) Prefer controlled vocabulary, such as LCSH, record subfield $2 for the source Capitalize the first term in each subfield $a When terms do not come from a controlled vocabulary, use a singular form Overall best practice: Repeat the MARC field when needed for clarity 375         Females $2 lcsh 375         Males $2 lcsh

377 Associated Language (9.14) Prefer language codes over language terms, using codes from the MARC Code List for Languages Encode multiple languages for a person or corporate body if more than one language is used for publication, etc. Note: it is not necessarily a person’s “native language,” and, a non-textual work will not have associated language. 110 2# $a Canadian Standards Association 377 ## $a eng $a fre 100 1# $a Phua, K. K. 377 ## $a eng $a chi

385 Audience Characteristics 386 Creator/Contributor Characteristics 385 and 386 fields are used for Works and Expressions. Do not use them in NARs for persons Instruction sheets have been developed by PCC SCT Final document will be included in DCM after additional questions are resolved 385 ## $n age $a Teenagers $2 lcdgt 386 ## $a Japanese Americans $2 lcsh

Order of Subfield $2 Best practice: put subfield $2 after the last element to which it applies   372 ## $a Biotechnology $a Genetic engineering $2 lcsh $s 2008     not: 372 ## $a Biotechnology $a Genetic engineering $s 2008 $2 lcsh Subfield $2, if coded, should precede subfield $v or a combination of subfield $v + $u  ...  Aside from that, there is no guidance on placement.  I always put the subfield $2 after the last element to which it applies, and before any subfield $s or $t. 40

Subfield $v : Structure and Usage Follow the basic citation principles apply to 670 subfield $a (Source citation) Used to justify 046, 3XX No need to cite usage information if it is the same on the source Subfield $v precedes $u if $u is used 41

Subfield $v : Example $u and $v are repeatable. 42 42

Undifferentiated Personal Name (DCM Z1) 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 RDA 9.19.1 to create a unique authorized access point for the person http://www.loc.gov/aba/pcc/rda/PCC%20RDA%20guidelines/Z01%20008%2032%202014rapril.pdf Now let’s take a look at the undifferentiated personal names in the current NACO file and what is the current guidelines in light of this RDA update. As of November 2013, LC and the PCC have agreed to the following guidelines for persons whose preferred names are identical: •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: • date of birth (9.3.2) • date of death (9.3.3) • fuller form of name (9.5) • period of activity (9.3.4) • profession or occupation (9.16) • title of the person, including terms of rank, honor, or office (9.4) • other designation associated with the person (9.6)

Undifferentiated Personal Name (DCM Z1) 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 to the new NAR If more than one identity remains in the undifferentiated NAR, and there is not sufficient info. in the NAR to create new NARs for each name, leave the NAR coded AACR2

Undifferentiated Personal Name (DCM Z1) In order to facilitate machine processing of authority records (e.g., matching, linking), when only one identity is left on an undifferentiated personal name authority record, take the following steps:

Undifferentiated Personal Name (DCM Z1) 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

Undifferentiated Personal Name (DCM Z1) If a differentiated NAR has been created for the last identity: Add that information in the 667 note on the undifferentiated 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

Undifferentiated NAR Example #1 The record 008/32 is coded “b” Cataloger has info. about the author circled in the paired 670.

Undifferentiated NAR Example #1 New NAR for this identity This is a differentiated new NAR cataloger created. Note 670s and the $c in the 100.

Undifferentiated NAR Example #1 This NAR remains coded as AACR2 “c” The earlier undifferentiated NAR was left still coded “b” 008/32 since there is more than one author still left. It remains as an AACR2 NAR.

Undifferentiated NAR Example #2 This example involves evaluating the non-Latin script references in the course of updating the undifferentiated NAR.

Undifferentiated NAR Example #2 New NAR for this identity

Undifferentiated NAR Example #2 Differentiated NAR created for the last entity Note subfield $z of the undifferentiated NAR will also be added to the NAR for the new identity in 010 field.

Undifferentiated NAR Example #2 Undifferentiated NAR, to be deleted

Undifferentiated NAR Example #3 Original undifferentiated NAR Note the non-Latin variants includes data mined from OCLC bibliographic records and represents more than two identities as shown in the 670 fields in this record.

Undifferentiated NAR Example #3 New NAR for identity #1

Undifferentiated NAR Example #3 New NAR for identity #2

Undifferentiated NAR Example #3 Undifferentiated NAR reported for deletion Note in this example, there were only two identities in the undifferentiated NAR, which both have been established in separate unique NARs. 667 note clarified that no identity remained in the existing undifferentiated NAR. No need to create a new NAR for this existing NAR. Also note subfield $z of this undifferentiated NAR will be added to the NARs for the two new identities in 010 field by the time this NAR is deleted.

Variant Access Point (8.3, 9.19.2) Not core Cataloger’s judgment Give variant access points where it’s useful Make additions to the name, if considered important for identification 100 1# $a Lee, Chau Min 400 1# $a Li, Zhaomin $c (Actress) 100 0# $a Rushuaizheshi 400 1# $a Pan, Yang, $d 1980- 8.3 Core elements did not mention variant access points in the list. This means it is optional to provide variant access points to an authorized access point. 59

Describing Families (RDA 10) Family NAR is for a specific family in a specific place and for a specific period of time, unlike subject family name Families as Creators Families as Contributors Families as Subjects 667 SUBJECT USAGE: This name is not valid for use as a subject; use a family name heading from LCSH Families as creators: create records/archives, newsletters, family cookbook, or family website or blogs As contributors: performers, publishers, or owners As subjects: subjects of works. LC policy: only use LCSH family name forms in 600 fields. This policy may change in the future. Until the policy change, family name authority records should be coded as not valid for use as subjects and should include 667 SUBJECT USAGE: This name is not valid for use as a subject; use family name heading from LCSH.

RDA Core Elements for Families (10.2-6) Always core if the information is known Preferred name for the family (MARC field 100 #3) Type of family (MARC field 376 $a) Date associated with the family (MARC field 046 $s) Core if necessary to distinguish Place associated with the family (MARC field 370 $f) prominent member of the family (MARC field 376 $b)

376 Family Information (RDA 10) Type of family (subfield $a) Name of Prominent Member (subfield $b) Give the form for the person as found in the 100 field of the NAR for the family Do not include any internal subfield coding in $b Hereditary title (subfield $c) Start period (subfield $s) End period (subfield $t)

Family NAR Example Reciprocity is not required - but if you want to add this reciprocal information OK. Must use authorized form of the name for progenitor. $g usually is the name of the prominent member of the family. Possibility on multiple NARs for same family name (because of how $g is defined currently) 63

Relationships Between Persons, Families, and Corporate Bodies (RDA 24-32, Appendix I, J, K) PCC Guidelines on Using Relationship Designators in NACO Authority Records: http://www.loc.gov/aba/pcc/rda/PCC%20RDA%20guidelines/Post-RDA-Implementation-Guidelines.html

Record Relationships to Persons and Families AAP Relationship designators should only be used to relate authority records in the LC/NACO Authority File Do not use relationship designators in 4XX fields Do not use a RD if a specific relationship cannot be determined. Instead use simple see-also from tracings (5XX). Consider adding a 667 field to indicated that researched has been done

Related Persons (RDA 30) 100 1# $a Endō, Rintarō 100 1# $a Endō, Rōgairō, $d 1881-1925 500 1# $i Real identity: $a Endō, Rintarō $ w r 100 1# $a Endō, Rintarō 500 1# $i Alternate identity: $a Endō, Rōgairō, $d 1881-1925 $w r When creating name authority records for a person with different identities, follow the guidelines in the Descriptive Cataloging Manual Z1 sections for MARC fields 663 and 667. More information is available in the FAQ – LC/PCC RDA and AACR2 practice for creating NARs for persons who use pseudonyms: http://www.loc.gov/catdir/cpso/pseud.pdf The “$w r + $i [Relationship designator]” is used only in case of 2 identities when only 2 access points and NARs are created for a person.

Related Families (RDA 31) 100 1# $a Shijō, Takatoshi, $d 1841-1911 500 3# $i Descendants: $a Shijō (Family : $d 1894- ) $w r

Related Corporate Bodies (RDA 32) 100 1# $a Chen, Tong, $d 1962- 510 2# $i Founded corporate body of person: $a Cantonbon (Project) $w r 100 1# $a Cho, Minsuk, $d 1966- 510 2# $i Founded corporate body of person: $a Mass Studies (Firm) $w r $w r displays at the end of the field in OCLC. Otherwise, it is the first subfield, preceding subfield $i.