CJK NACO Webinar Series – Supplement to the PCC NACO Training Describing Corporate Bodies and Conferences (Chapters 8 and 11)

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 for 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 Preferred names for corporate bodies Change of names Preferred names for subordinate and related bodies Direct and indirect subdivision Conference names Attributes of corporate bodies Variant names Relationships between persons, families and corporate bodies

Definition of Corporate Body (8.1.2) Meetings, events, festivals, athletic contests, exhibition, and vessels are considered corporate bodies Corporate bodies as creators, contributors, and as subjects Example: 111 2# $a Dang dai yu yan xue li lun he Han yu yan jiu guo ji xue shu bao gao hui $d (2006 : $c Beijing, China) 411 2# $a 当代语言学理论和汉语研究国际学术报告会 $d (2006 : $c Beijing, China)  Corporate bodies as creators (company websites, reports or catalogs), contributors (publishers, owners), and as subjects (610 Society for Conservation Biology, 611 Olympic Games)

Preferred Name (11.2.2) Choosing preferred name Different forms of the same name Different language forms of the name International bodies

Choosing and Recording the Preferred Name Choose the name by which the corporate body is commonly identified Record it as it appears in resources associated with the body. If the name does not appear in resources associated with the body, or in case of doubt, record it in the form most commonly found in reference sources

Change of Name, Minor Differences (11.2.2.5) Guidelines on identifying minor changes of name. Consider minor differences in the absence of explicit evidence that a true name change has taken place, such as: Representation of words Change in preposition, article, or conjunction Change in punctuation Addition, omission, or fluctuation of a frequency word in a conference name

Different Forms of the Same Name (11.2.2.5) Choose the name that appears in the preferred sources of information Choose the form that is presented formally Choose the most commonly found form of the name Choose a brief form

Name appeared in the preferred sources of information

Different Language Forms (11.2.2.5.2) Choose as the preferred name the form in the official language of the body LC-PCC PS: If there is more than one official language and one of these is English, choose the form in English as the preferred name

Special Rules for Corporate Bodies in Hong Kong Government body Establish in English if both English and Chinese available, and in Chinese if only Chinese available Code “provisional” Non-government body Establish in English if both English and Chinese available Code “full level”

Government Body: Provisional Level

Non-Government Body: Full Level

International Bodies (11.2.2.5.3) If the name of an international body appears in resources associated with it in a language preferred by the agency creating the data, choose that form as the preferred name LC-PCC PS: If the name of an international body appears in English on resources associated with it, choose that form as the preferred name

International Bodies

Referencing a Related Corporate Body (11.2.2.6, 32.1.1.3) Earlier/later relationships: Use MARC field 5XX to connect related bodies. All 5XX must be separately established. Use subfield $i and r in subfield $w Simple 5XX relationships: When the relationship is not directly sequential, or information about the exact relationship is unknown Earlier Name Resumed Earlier Names not likely to be needed as relationships

Earlier/later Relationships (11.2.2.6, 32.1.1.3) Use MARC 5XX to connect related bodies. Separate NAR must be established for all related bodies (subfields $w and $i w/RD)

Earlier/later Relationships

Earlier/later Relationships

Earlier/Later Relationships Middle body

Earlier/Later Relationships Latest body

Earlier/Later Relationships Earliest body

Relationship is Not Known (LC-PCC PS 32.1.1.3) Use simple 5XX without subfields $w and $i when the relationship is not directly sequential, or unknown, or when it has been decided not to record the relationship

Simple 5XX Relationships

Simple 5XX Relationships

Earlier Name Resumed (LC-PCC PS 32.1.1.3) Treat each instance of the name as a separate body when a corporate body resumes an earlier form of name. Distinguish between AAPs by following the instructions at 11.13.1.1 NAR 1: 110 2# $a Body A (1937-1949) 510 2# $wr $i Successor: $a Body B NAR 2: 110 2# $a Body C (2001- ) 510 2# $wr $i Predecessor: $a Body B Note: Body A and Body C share the same name.

Earlier Name Resumed (LC-PCC PS 32.1.1.3) Update: use one authorized access point to represent all instances of the same name when a corporate body belongs to one of the following categories, and include a 667 field in the NAR about the decision made. Add other clarifying info. in the 667 note if useful Note: If a body has already had separate AAPs created for the earlier and resumed names, it is not required to retrospectively collapse the separate AAPs into one AAP

Earlier Name Resumed (LC-PCC PS 32.1.1.3) Category A - Bodies of a Type Likely to Be Subject to Frequent Name Changes Use one authorized access point to represent both the earlier and resumed name, if a body is likely to have frequent name changes because of its nature (e.g., firms named after individual members, legislative committees, conferences)

Earlier Name Resumed Category A Example 111 2# $a IEEE Workshop on Advanced Robotics and its Social Impacts 511 2# $a IEEE International Conference on Advanced Robotics and its Social Impacts $d (2008 : $c Taipei, Taiwan) 667 ## $a This conference resumed its earlier name; the name IEEE Workshop on Advanced Robotics and its Social Impacts was used 2005-2007 and 2009- present. The name IEEE International Conference on Advanced Robotics and its Social Impacts was used in 2008

Earlier Name Resumed (LC-PCC PS 32.1.1.3) Category B - Place Names Use the same authorized access point for both the earlier and resumed name provided the additions to the AAP are appropriate for each instance, when a place resumes its earlier name

Earlier Name Resumed Category B Example 151 ## $a Saint Petersburg (Russia) 551 ## $a Leningrad (R.S.F.S.R.) 667 ## $a This place resumed its earlier name; Leningrad resumed the name Saint Petersburg in 1991. 151 ## $a Leningrad (R.S.F.S.R.) 551 ## $a Saint Petersburg (Russia) Note: also reflects change of name of the larger place

Earlier Name Resumed (LC-PCC PS 32.1.1.3) Category C - Bodies with Complex and Uncertain Histories If a body has had a complex or uncertain history, and creating and applying separate authorized access points for each use of the same name is not feasible, use the same authorized access point for both the earlier and resumed name

Earlier Name Resumed Category C Example 110 2# $a Republican National Committee (U.S.) 511 2# $a National Union Executive Committee (U.S.) 667 ## $a This corporate body resumed its earlier name; the Republican National Committee began in 1856.  It used the name National Union Executive Committee beginning in 1864 until sometime around 1868.

Earlier Names Not Likely to be Needed as Relationships (32.1.1.3) If the earlier names of a corporate body that are not likely ever to be needed as access points in bibliographic records, and the decision is made not to create NARs for the earlier names, record them in the 670 along with an indication such as [no publications in database] or [no access point found in OCLC] 110 2# $a Body A 670 ## $a Title cataloged, date :$b cover (Body A) pref. (Body B [no access point found in OCLC])

Preferred Names for Subordinate and Related Bodies (11.2.2.13-14) Record the name of a subordinate body or a related body under 11.2.2.4 unless its name belongs to one or more of the types listed at 11.2.2.14 11.2.2.4 – Record the name chosen as the preferred name (either as it appears in resources associated with the body, or under the form most commonly found in reference sources

Subordinate and Related Bodies Recorded subordinately (11. 2. 2. 14 Record the name of the subordinate body in the form of a subdivision of the authorized access point representing the higher body. Make it a direct or indirect subdivision under 11.2.2.15. Subordinate body entry: 11.2.2.14.1-6, 11.2.2.14.7-18

Body Whose Name Implies Administrative Subordination (11.2.2.14.2) Apply the instruction to a name containing a term that normally implies administrative subordination, only if the name of the higher body is required for the identification of the subordinate body

Direct or Indirect Subdivision (11.2.2.15) Record the name as a subdivision representing the lowest unit in the hierarchy that is recorded directly under its own name. Omit intervening units in the hierarchy, unless the name of the subordinate body has been or is likely to be used by another body. In that case, interpose the name of the lowest unit in the hierarchy that will distinguish between the bodies.

Indirect Subdivisions (11.2.2.15) Refer from the name of its immediately superior body for direct subheading entry

Indirect Subdivisions (11.2.2.15)

Conference Name Location Qualifier (11.13.1.8) Add the name of the associated institution instead of the local place name if: the institution name provides better identification, or the local place name is not known When adding the name of an institution as the location of a conference, record the preferred name for the institution, minus any additions used in the institution’s authorized access point

Conference Name Location Qualifier (11.13.1.8) Name authority record for the institution name:

Ongoing Conferences (11.13.1.8) Separate NARs may be created for the collective conference (typically made when cataloging serial), an individual instance of an ongoing conference (typically made for a monograph), or both. These records may coexist in the NACO file. A record for the collective conference should always be made to connect the earlier and later names of the collective conference. Once an official name of a conference is chosen, the names for all NAR should have the same name.

Access Point for a Series of Conferences, Etc. (11.13.1.8.2) If the access point represents a series of conferences, etc., do not add the number, date, or location of the conferences, etc. Be careful not to confuse a “Place associated with a corporate body” added to distinguish different conferences with the same name with a location of a conference.

Access Point for a Series of Conferences, Etc. (11.13.1.8.2) Connect authority records for earlier and later names of the collective conference using 5XX field Include a 667 field when there are authority records for both collective and individual instances of an ongoing conference 667 ## $a See also related access points for individual instances of this conference which include specific information about the number, date, or place of the individual conference.

Collective Treatment of an Ongoing Conference

Collective Treatment of an Ongoing Conference

Access Point for a Single Instance of a Conference (11.13.1.8.1) Add the following elements to the name of a one-time conference, or a single instance of a series of conferences (number, date, location). 111 2# $a Olympic Winter Games $n (21st : $d 2010 : $c Vancouver, B.C.) Generally do not connect an individual instance of an ongoing conference to the earlier or later instance of the conference using a 5XX field, or to an NAR for the collective conference

Single Instance of an Ongoing Conference

Single Instance of an Ongoing Conference

Conference Name and Its Associated Bodies Often, establishing a corporate body name or a conference name authorized access point involves updating and modifying the associated authority records. Research often is needed in order to decide the relationship among the different names.

Establish Single Instance Conference Name

Update AACR2 NAR to a Collective Conference

Update Sponsoring Body Name NAR

Update Parent Body Name NAR of the Sponsoring Body

Update Parent Body Name NAR of the Sponsoring Body

Attributes of Corporate Bodies (11.3-5) Date: Core when needed to distinguish between bodies with same name; core for Conference, record it when known 046 ## $s 2011-11-18 $t 2011-11-19 $2 edtf 111 2# $a Kokusai Shinpojūmu "Translating/Comparing Poetry" $d (2011 : $c Ōtemae Daigaku) Places: Core when needed to distinguish between bodies with same name 370 ## $e Anxi Xian (Fujian Sheng, China) $2 naf 110 1# $a Anxi Xian (Fujian Sheng, China). $b Jiao tong ju Institutions: Core when needed to distinguish and provide better identification than place name 373 ## $a Koryŏ Taehakkyo. Chungang Tosŏgwan $2 naf 110 2# $a Chʻiam Munʼgo (Koryŏ Taehakkyo. Chungang Tosŏgwan)

Other Elements (11.7) Type of corporate body, jurisdiction, or other designation 368 Congresses and conventions $2 lcsh 368 $b Cities and towns $2 lcsh 368 $c South e.g., for Korea (South)

Other Elements (11.8-10) Language of the body – MARC field 377 Address of the body – MARC field 371 Field of activity of the body – MARC field 372 Corporate history – MARC field 678 #1

Variant Names (11.2.2.13) Record as a variant name the name of the body in the form of a subdivision of the authorized access point representing the higher body

Variant Name Example

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

Module 4. Describing Corporate Bodies Related Persons (RDA 30) Related persons are recorded in 500 fields, and may include a relationship indicator in subfield $i (from RDA Appendix K), with $w r 110 2# $a Dannō Hōrinji (Kyoto, Japan) 410 2# $a 檀王法林寺 (Kyoto, Japan) 500 0# $i Founder: $a Taichū, $d 1552?-1639 $w r no2012072927 Module 4. Describing Corporate Bodies

Related Families (RDA 31) 64 Related Families (RDA 31) Related families are also recorded in 500 fields. You may include a relationship indicator in subfield $i (from RDA Appendix K), with $w r 110 2# $a Berith Salom (Organization) 500 3# $i Founding family : $a Spanjaard (Family) $w r 100 3# $a Spanjaard (Family) 5102# $i Founded corporate body of family: $a Berith Salom (Organization) $w r Module 4. Describing Corporate Bodies

Related Corporate Bodies (RDA 32) 65 Related Corporate Bodies (RDA 32) Related corporate bodies are recorded in 510 fields. You may include a relationship indicator in subfield $i (from RDA Appendix K), with $w r, or may use MARC $w coding. 110 2# $a Beijing da xue. $b Ya Fei La shi jiao yan shi 410 2# $a 北京大学.ǂb亚非拉史教研室 510 2# $i Hierarchical superior: $a Beijing da xue. $b Li shi xi $ w r Module 4. Describing Corporate Bodies

Use of $i in Relationship Links Between Corporate Entities and the Name of Other Persons or Families – Use judgment about whether to make reciprocal 5XX Explicit recording of certain reciprocal relationships is highly encouraged to facilitate search and retrieval