1. LC Training for RDA: Resource Description & Access
Module 6: Authorities II
Part 2: Identifying Corporate Bodies
Cooperative and Instructional Programs Division
Library of Congress
2012

2. Vocabulary
Name: Word, character, or group of words and/or characters by which a corporate body is known
Preferred Name: Form to be used when constructing the authorized access point in bibliographic records and 1XX field of name authority records
Variant Name: Form used in variant access points (4XX fields in name authority records)
These were called headings in AACR2! We find these vocabulary terms in RDA 8.1.

3. Vocabulary
Access Point: Name, term, code, etc., representing a specific corporate body
Authorized Access Point: Standardized access point representing an entity; uses the preferred name for the corporate body
Variant Access Point: Alternative to the authorized access point representing an entity; constructed using a variant name for that corporate body
These were called headings in AACR2! We find these vocabulary terms in RDA 8.1.

4. Sources for Elements Preferred name (in order of preference):
Preferred sources of information (see RDA 2.2.2) in resources associated with the entity
Other formal statements appearing in resources associated with the entity
Other sources (including reference sources)
We will take one more stop in RDA– at RDA 2.2.2– to find out the order of preference for the preferred name. These are in priority order. This should sound familiar to you– it is similar to AACR2, but the instructions in RDA are given in an earlier chapter, chapter 2, Identifying Manifestations and Items, because we are talking about the preferred name that will be used in a bibliographic record– we will then use that preferred form in constructing the authorized access point (the NAR!) for the name.

5. General Guidelines Language and Script
“Record names in the language and script in which they appear on the sources from which they are taken.”
Alternative: Record a transliterated form of the name either as a substitute for, or in addition to, the form that appears on the source.
Record other identifying attributes of a person, family, or corporate body in the language and script prescribed in the applicable instructions in chapters 9-11.
We’re still in RDA Chapter 8 (RDA 8.4 to be specific)– but not for long….
RDA gives you choices for language and script for the Group 2 entities. PCC libraries will continue to give names of those entities in the Latin script in the authorized access points in authority records and in bibliographic records. PCC libraries may also continue the current policy for some languages to give variant access points (MARC 4XX fields) in the original language/script in authority records– those non-Latin references that you have seen in AACR2 authority records.
Then– for those “other identifying attributes”– if instructions in Chapter 9 do not specify language, give the elements in English.

6. Scope of “Corporate Body”
“An organization or group of persons and/or organizations that is identified by a particular name and that acts, or may act, as a unit.” (RDA 8.1.2)
A body is considered to be a corporate body only if it is identified by a particular name (i.e., if the words referring to it are a specific appellation rather than a general description) (RDA 11.0)

7. Scope of “Corporate Body”
Typical examples of corporate bodies are associations, institutions, business firms, nonprofit enterprises, governments, government agencies, projects and programs, religious bodies, local church groups identified by the name of the church, and conferences. (RDA 11.0)
Ad hoc events (such as athletic contests, exhibitions, expeditions, fairs, and festivals) and vessels (e.g., ships and spacecraft) are considered to be corporate bodies. (RDA 11.0)

8. Where is that Scope List from AACR2?
Corporate Bodies Considered to Be Creators (RDA )
Corporate bodies are considered to be creators when they are responsible for originating, issuing, or causing to be issued, works that fall into one or more of the following categories: … (RDA )
Also refer to the LCPS for this instruction
Remember that scope description of a corporate body from AACR2 Chapter 21? We always needed to refer to it before deciding whether a work should be entered under the corporate body– that is why it was in AACR2 Chapter 21, Choice of Access Points, and not in AACR2 Chapter 24, Corporate Bodies. The same principle is at work in RDA—to find more about the scope of a corporate body (and, no surprise, it is not that different from the one you know from AACR2), we need to look at RDA Chapter 19– Persons, Families, and Corporate Bodies Associated with a Work– and that is where we also find what used to be in AACR2 Chapter 21. It is also important to take a look at the related LCPS– that is where you will find more information on judging whether a corporate body should be considered the creator of a work.

9. Identifying Corporate Bodies
RDA Chapter 11 “Identifying Corporate Bodies”
11.0 Purpose and Scope
11.1 General Guidelines
11.2 Name of the Corporate Body
11.4 Date Associated With the Corporate Body
11.5 Associated Institution
11.6 Number of a Conference, etc.
On this slide and the three that follow, you will see how RDA Chapter 11 is arranged. These slides go in chapter order. For Module 6.a, Recording the Information Found, we will be looking at more detail for each of these parts of Chapter 11. But for now, we are just looking at an overview. More detail to come.
In RDA Chapter 11 the elements identifying a corporate body are given separately at the beginning of the chapter. Then, at the end of the chapter, there is an instruction that says which of those elements to use in constructing an authorized access point.
For corporate bodies, the preferred name is the basis for the authorized access point. Then there are possible additions to the preferred name.

10. Identifying Corporate Bodies
RDA Chapter 11 “Identifying Corporate Bodies”
11.7 Other Designation Associated with the Corporate Body
11.8 Language of the Corporate Body
11.9 Address of the Corporate Body
Field of Activity of the Corporate Body

11. Identifying Corporate Bodies
RDA Chapter 11 “Identifying Corporate Bodies”
Corporate History
Identifier for the Corporate Body
Constructing Access Points to Represent Corporate Bodies
This is the last slide for the overview of RDA Chapter 11. But there is a very important thing to note here– at the very end of RDA Chapter 11 is the section on Constructing Access Points to Represent Corporate Bodies. This is no different from the arrangement in Chapters 9 and 10. All the preceding sections in Chapter 11 discuss data elements that can be used to identify corporate bodies. But from all of those data elements, only certain ones can actually be added to the preferred name to create an authorized access point.
But the construction of the access point is only a small part of identifying a corporate body. Of course, the access point is extremely important, perhaps the most important part of the authority record for a corporate body, but unlike AACR2, in which Chapter 24 only addressed construction of headings for corporate bodies, RDA takes a much more holistic approach, addressing the construction of the access point itself, the actual 1xx part of the authority record, last.
Now let’s start with the preferred name for a corporate body, then we’ll look at all the identifying characteristics RDA allows up to record for the body– those characteristics that are covered in the bulk of RDA Chapter 11– you just saw them all listed on the slides– from RDA all the way through RDA then, in the next module, we will look at which of those identifying characteristics may be used in the authorized access point itself. But we’ll start with the preferred name, and remember, we are not thinking of the 1xx quite yet– this is just in anticipation of that.

12. Preferred Name (RDA 11.2.2) Choose the form most commonly known
Variant spellings: choose the form found in the first resource received (RDA )
LC policy: change to the later spelling in cases of orthographic reform
Not abbreviating “Department” (should not have abbreviated in AACR2 headings)
These will be changed in the LC/NACO Authority File recodings
Just as for personal and family preferred names, determine the most commonly-known form of the name of the corporate body. If there are variations, choose the form found on the first resource received unless a later spelling is the result of orthographic reform.
Remember not to abbreviate the word “department.” Well, unless it is represented in abbreviated form– following the Principle of Representation– transcribe what you see.

13. Preferred Name (RDA )
Names containing initials, terms of honor, terms of incorporation, etc. (RDA RDA )
Various categories of corporate bodies (e.g., subordinate bodies both government and non-government, courts, religious officials, etc.) (RDA RDA )

14. Preferred Name for Conferences, Exhibitions, etc. (RDA 11.2.2)
A merged instruction for the preferred name of a conference, congress, meeting, exhibition, fair, festival, etc.:
Retain frequency in the name of a conference, congress, or meeting
Omit year of convocation from the name of an exhibition, fair, or festival (will be included in the authorized access point in subfield $d) if publication cataloged as a monograph
In RDA two different AACR2 rules are merged when determining the preferred name for a conference, exhibition, etc. The result is that there are some differences from AACR2 in what appears as part of the preferred name: retaining the frequency but omitting the year.
The year does appear in the authorized access point (in subfield $d, not in subfield $a) for the conference, etc., if the resource is not cataloged as a serial.
Lots to look forward to here in the work of the PCC task group working on PCC NACO policies and best practices. Because of the merged instruction in RDA, authority records will be created for every instance of a conference, when needed for an access point for a monographic publication. This is a big change from current practice, where for an ongoing conference, no qualification was added to the authority record, but was added to the bibliographic record. In RDA, and the resultant PCC best practice or policy decision, we will add the qualification to the authority record– and treat serial publications slightly differently. Let’s look at the next slide as well…

15. Conference Access Points Additions (RDA 11.6)
If for a single conference, etc., include additions in bibliographic record X11
Interim PCC policy for NARs:
Add the number, place, and date to a new NAR for a conference if it is being established for the first time under RDA
If an AACR2 NAR for an ongoing conference already exists without the additions for number, place, and date, do not create a new NAR
The LC policy for including additions for a conference, etc., authorized access point has been simplified for November If the access point is for a single event, always include the appropriate additions in the NAR as well as in the bibliographic record; you no longer will determine if the conference is a one-time conference or part of an ongoing series of conferences.

16. Addition if not “Corporate” Enough (RDA 11.7)
Part of “Other designation associated with the corporate body”
Cataloger judgment on choice of term (generally in English in the U.S.):
Levantine Entertainment (Firm)
Remember: if subordinate body, establish subordinately to higher body
Some names don’t convey the idea that the name is a corporate body. For those preferred names, add a term to convey this information.
Remember that this action applies only when the corporate body is not subordinate to another body; when there is a higher body, the subordinate body is established subordinately and no term is added in parentheses. The addition of the higher body is enough to indicate “corporateness.”

17. Associated Place (RDA 11.3)
Two categories:
Location of conference, etc.
Location of headquarters
Form of place:
Form prescribed in Chapter 16
Abbreviate name of countries, states, etc., as instructed in Appendix B
NAR not required
The attribute Place associated with a corporate body is used for two types of corporate bodies: conferences (we’ll look at place for those access points in a later slide) and all other corporate bodies.
The form of the place is based on the instructions in chapter 16 (the counterpart to AACR2’s chapter 23); some abbreviations are used.
Associated Place is a core element in certain situations:
RDA :
Place associated with the corporate body is a core element for conferences, etc. (see ). For other corporate bodies, place associated with the corporate body is a core element when needed to distinguish a corporate body from another corporate body with the same name.

18. Associated Institution (RDA 11.5)
In the form and language recorded as the preferred name for the institution (not the authorized access point for the institution)
Associated institution is a core element if needed to break a conflict.
Use the preferred name, not the authorized access point, when giving this element.
This is no different than AACR2.

19. Date of Establishment or Termination (RDA 11.4.3-11.4.4)
Year in which a corporate body was established or terminated
Give if needed to differentiate the name of one corporate body from another
MARC X10: add with hyphen, if both dates, in parentheses, to the preferred name – no change
Date of establishment or Date of termination is included in an authorized access point if needed to break a conflict. Again, no different from AACR2!

20. Type of Jurisdiction (RDA 11.7.1.5)
Part of “Other designation associated with the corporate body”
Term designating the type of jurisdiction added if necessary, to distinguish between access points for two or more governments that have the same or a similar name
e.g., Cork (Ireland)
Cork (Ireland : County)
Type of jurisdiction may be needed in an authorized access point to distinguish two or more governments that have the same or similar names.
Remember: New York (State) to distinguish from New York (N.Y.)!

21. “Other Designation ... ” (RDA 11.7.1.6)
If other elements in “list” not appropriate or not sufficient to differentiate between two different non-conference bodies, add:
A word, phrase, or abbreviation indicating incorporation or legal status
Any term serving to differentiate the body from other corporate bodies, persons, etc.
World Cup (Cricket) Congo (Brazzaville)
World Cup (Soccer) Congo (Democratic Republic)
We’re back for a second look at the element Other designation associated with the corporate body. We looked at it first when the element is needed as an addition to a preferred name if that name doesn’t convey the idea that it belongs to a corporate body– an example is Red Hot Chili Peppers (Musical group) or Johann Traeg (Firm) – really no different from AACR2. That “list” on this slide means: (place nor date associated with the body, nor an associated institution, nor a type of jurisdiction, is sufficient or appropriate for distinguishing between two or more bodies, record an appropriate designation in the language preferred by the agency creating the data)– it is in RDA

22. Number of a Conference (RDA 11.6)
“Designation of the sequencing of a conference, etc., within a series of conferences, etc.”
Use English ordinal numerals 1st, 2nd, 3rd, etc.
LC policy: not given in access point if publications of a conference, etc., cataloged as a serial
There are three additions related to authorized access points for conferences. The first is Number of a conference, etc., if the conference is numbered, and if the resource is not cataloged as a serial. The number is recorded as an English ordinal numeral in the form shown on the slide.

23. Date of Conference, etc. (RDA 11.4.2)
Date or range of dates, given as year or years, in which a conference, etc., was held
LC policy: not given in access point if publications of a conference, etc., cataloged as a serial
The Date of a conference, etc., is a date or range of dates, usually years, given in subfield $d of the authorized access point if the resource isn’t being cataloged as a serial.

24. Location of Conference (RDA 11.3.2)
In form as authorized access point
No “rule of three” when sessions held in three or more locations (separated by semicolons in access point -- RDA Appendix E – give all)
If conference held online, location is “Online”
Omit in access point if publications of a conference, etc., cataloged as a serial
Now we’re back to Place associated with the corporate body in its use as location of a conference.
Listed here are two changes from AACR2 for location of a conference:
1) there is no restriction on the number of places to give;
2) when the conference is held online, “online” is given as the place.
What about establishing the location of a conference? If the location is added to the 370 field, and there is no authority record for the place, it does not need to be established. You make the necessary modifications to the preferred name in order to record the data in the 370 9Cf. DCM Z1 370 section).
If you use a place name as part of an access point in the qualifier, it does need to be established, if it does not already have an authority record.

25. Institution as “Place” for Conference (RDA 11.3.2)
If the institution’s name provides better identification than the local place name or if the local place name is unknown or cannot be readily determined
Use the preferred name of the institution (not the authorized access point) – an authority record is not needed, if one does not exist
Remember that earlier we were talking about Associated institution and said it could be used in an authorized access point for a conference if that information is more helpful for the user or if you don’t know the local place. Give the preferred name of the institution, not the authorized access point for the institution.

26. New Fields in the MARC 21 Authority Format for Corporate Bodies
046: Special coded dates (RDA 11.4)
368: Other corporate body attributes (RDA 11.7) -- not yet implemented
370: Associated place (RDA 11.3)
371: Address (RDA 11.9) (not in 1xx)
372: Field of activity (RDA 11.10) (not in 1xx)
377: Associated language (RDA 11.8) (not in 1xx)
This slide shows the new fields for corporate bodies in the MARC 21 Authority Format. Such characteristics can be very helpful when identifying corporate bodies even if the preferred names are slightly different. The 368 field, approved in June 2011, won’t be implemented until next year. Where you see (not in 1xx) on the slide, that means that the element may not be added to the authorized access point. But it still is very helpful to have it in the authority record itself! See the next slide …
We’ll look at examples of authority records using these fields in a few minutes.

27. Elements not Eligible for Inclusion in Authorized Access Points
May be helpful for identification:
Associated place for non-conference corporate bodies (RDA 11.3)
Address (RDA 11.9)
Field of activity (RDA 11.10)
Language of the corporate body (RDA 11.8)
Corporate history (RDA 11.11)
Listed here are the attributes for corporate bodies in RDA Chapter 11 that are not used to assemble authorized access points; they can be helpful when distinguishing one corporate body from another when looking at name authority records.

28. Associated Place (RDA 11.3)
“Significant location associated with the corporate body”
e.g., Headquarters of an organization
Place given in form it would be as an addition to an access point
NAR not required
If not a jurisdiction, in separate 370 with vocabulary (e.g., LCSH) in subfield $2
If you give a place connected to a corporate body in field 370 of the name authority record, it should be in the RDA form it would have as an addition to an access point. The LC policy change for November is that there does not need to be an NAR for that jurisdiction. Also, you can give a non-jurisdiction place (e.g., a region) but it must be in a separate 370 field with the source of the term in subfield $2.

29. Address (RDA 11.9)
“Address of corporate body’s headquarters ..., or Internet address”
MARC field 371 (separate subfields)
This information would be given only if it is publicly available.
For a corporate body, an address or internet address is very helpful!

30. Field of Activity (RDA 11.10)
“Field of business ..., its area of competence, responsibility, jurisdiction, etc.”
No controlled vocabulary in RDA
MARC field 372; if use a thesaurus, cite it in subfield $2
MARC 372 field can contain the field of activity for a corporate body. Remember that there isn’t a controlled vocabulary in RDA for this element. We have noticed that a lot of PCC NACO participants prefer to use LCSH as a controlled vocabulary– that is a good idea, since most catalogers have a close familiarity with that controlled vocabulary.

31. Language of the Corporate Body (RDA 11.8)
“Language a corporate body uses in its communications”
“Select terms from a standard list of names of languages, if available.”
In MARC 377 field, form is three-character code from MARC code list of languages
If giving this element in field 377, remember that it is a language used by the body in its publications. It is not just the language of the body’s headquarters or branch offices. Use the three-character codes specified by MARC; do not use the names of the languages as illustrated in RDA In the instruction at RDA 11.8, spelled-out forms are illustrated– Russian, English, for example– but there is a note as well: Select terms from a standard list of names of languages, if available. We will do that and use the three-character MARC code for the language. There is no prescribed order if giving multiple languages.

32. Corporate History (RDA 11.11)
“Information pertaining to the history of a corporate body”
Can incorporate information from separate fields into a “public note”
MARC field 678
You can use MARC field 678 to give the corporate body’s history in a public note; this note needs to be written in complete sentences without any cataloger jargon. The information in the note needs to be justified elsewhere in the NAR, either in separate specific fields or in one or more 670 fields.

33. Wrap-Up
Here is an example of an RDA NAR in OCLC. You can see some of the attributes we have just described illustrated in the NAR. Think about how much more dynamic this RDA NAR can be in an online environment– it is a living thing.
In the next module, we will look at how to create the authorized access point for a corporate body– that is just one part of the overall RDA authority record.

34. More Information the New MARC 21 Authority Format Fields

35. Identifying Corporate Bodies Constructing Authorized Access Points
In the previous module we looked at identifying characteristics of a corporate body, all of which may be recorded in an authority record for the body. The authorized access point is only a part of the authority record, though. In this module, we will look at the authorized access point itself, and we will look at what identifying characteristics may be added to the authorized access point. 35 35

36. Constructing Authorized Access Points
It is not until RDA 11.13, at the end of the chapter, that we finally arrive at the instructions for creating the authorized access point, the 1xx. We will rely on all the previous sections of Chapter 11 to assist us in the construction of the access point, however. 36 36

37. Authorized Access Points for Corporate Bodies (RDA 11.13)
RDA : How to put together the elements to construct an authorized point
Preferred name is the basis
Includes the concept of subordinate body entry– the same types as in AACR2
Additions to the name as instructed under – , in that order, as applicable
Chapter 11 has the same organization as chapters 9 and 10: the elements identifying a corporate body given first and then, at the end of the chapter, an instruction that says which of those elements to use in constructing an authorized access point.
RDA is the instruction for authorized access points for corporate bodies. As for persons and families, the preferred name is the basis for the authorized access point for a corporate body. There are seven possible additions to the preferred name with a prescribed order as applicable to the type of corporate body. In the instruction for each of those elements, there is a link back to the element itself for guidance on how to construct the element. 37 37

38. Additions to the Preferred Name
( ): Addition if name not “corporate” enough:
Health of the Public (Program)
Required for certain names
(11.3): Place associated with the body:
Republican Party (Mont.)
If needed to distinguish
May be added if it assists with identification
Let’s look at some examples right out of RDA: This slide and the next three: Here are the additions we can make to the authorized access point for the corporate body. The instruction in RDA under Constructing Authorized Access Points is given, and in parentheses, the instruction that addresses the elements themselves. 38 38

39. Additions to the Preferred Name
(11.5): Associated institution
Annual Computer Law Institute (Practising Law Institute)
If needed to distinguish
(11.4): Date associated with the body
South Dakota. Department of Public Safety (2003– ) 39 39

40. Additions to the Preferred Name
( ): Type of jurisdiction
Darmstadt (Germany : Landkreis)
If needed to distinguish
(11.7): Other designation
Indiana (Battleship : BB-50) 40 40

41. Additions to the Preferred Name
(11.6, 11.4, 11.3): number, date, & location of a conference
Governor’s Conference on Aging (Fla.) (3rd : 1992 : Tallahassee, Fla.)
Australian Bioethics Association. National Conference (6th : 1998 : Hobart, Tas.)
Required for certain names 41 41

42. Putting the Authorized Access Point into MARC 21
No big surprises here!
Follow:
Punctuation as in AACR2 (RDA Chapter 8 & LCPS 1.7.1)
Capitalization as in AACR2 (RDA Appendix A & LCPS 1.7.1)
MARC 21 tagging and coding as in AACR2
Initial articles as in AACR2 (RDA Appendix C)
Even though RDA is very close to AACR2 in terms of constructing an authorized access point for a person, still you cannot apply the instructions in RDA without reading and understanding them first. The purpose of this module is to show you how to construct an RDA authorized access point for a person, and in order to do that, we are using comparisons between AACR2 and RDA to assist you. Remember, though, there is no substitute for a thorough reading of RDA! And we are not encouraging you to apply RDA based on these slides alone. It is your responsibility to use these slides as an entry to the RDA instructions. 42 42

43. Identifying Corporate Bodies Constructing Variant Access Points
Now we’ll look at variant access points– here is where AACR2 and RDA diverge! 43 43

44. Constructing Variant Access Points
RDA gives us instructions on variant access points for a corporate body in – right after section on Constructing Authorized Access Points– in fact, is a sub-section of 11.13—Constructing Access Points to Represent Corporate Bodies. So, whereas in AACR2 you would have gone to Chapter 26 to find out about variants, in RDA, you stay in the same chapter. This is just the beginning of the differences …
What is the same between AACR2 and RDA is this: you construct a variant access point as if it were an authorized access point– treat the variant as if it were an authorized access point, meaning that any or all additions that would be allowed in the authorized access point are appropriate in the variant access point. 44 44

45. Variant Access Points
Which variants do you include in an authority record as 4XX fields?
RDA 11.2: CORE ELEMENT:
Preferred name for the corporate body is a core element. Variant names for the corporate body are optional.
LC policy: cataloger judgment
Consider what users (remember FRAD User Tasks!) would need or find helpful
RDA does not require any categories of variant access points. Cataloger judgment is the LC policy; consider what users would need to find the authorized access point form.
This may be a hard concept to get your head around, especially if you have been doing AACR2 authority work for a long time. Those inverted references … gone; those spelled out forms of ampersands and those mixed-language variants that favor English usage … gone. This is all now cataloger’s judgment, not rule-determined.
The PCC is currently recommending certain categories of variants that may be considered either policy to add or “best practice.” A lot of this is yet to be determined, and for that reason, this module is extremely short! 45 45

46. Government Bodies
Record as a variant name the name in the form of a subdivision of the authorized access point representing its immediately superior body when the access point does not include the name of that superior body (RDA ) -- What to do? 46 46

47. RDA Chapter 9: Identifying Corporate Bodies
AACR2 Similarities and Differences 47

48. RDA and AACR2 Conceptually different codes
Authority work under each code has many similarities, though
But there are some major differences
What is the same and at what is different?
Nothing can beat a thorough reading and understanding of RDA! 48 48

49. RDA and AACR2: Similarities
MARC 21 coding and field order
Punctuation and Spacing (RDA Chapter 8, LCPS 1.7.1)
Additions to names (RDA )
But a couple of exceptions!
Data added to the authority record
But in different locations!
NACO Normalization (NACO) 49 49

50. RDA and AACR2: Similarities
Ambiguous entities (RDA 11.0 & SHM H 405)
New NAR for a name change (RDA )
Three Basic Principles (NACO)
Government body or not a government body?
Direct entry or subordinate entry?
Any additions or omissions?
Direct entry is “default” choice (NACO)
Preferred sources for determining the preferred name (RDA )
Some examples from SHM H 405:
Cemeteries are Group 1 (NACO) and Gardens are Group 2 (SACO). 50 50

51. RDA and AACR2: Similarities
Official language of the body (RDA )
Provisional coding (RDA )
Minor name changes (RDA )
Subordinate entry instructions
RDA (6 Types) = AACR
RDA (11 Types) = AACR
Direct or indirect subdivision
RDA = AACR A
More on Provisional coding: Code the 008/33 byte as in AACR2. Refer to DCM Z1 667 section on when to record information on why the provisional coding was assigned. RDA does not address this. 51 51

52. RDA and AACR2: Similarities
Types of qualifiers (RDA )
Omission of Inc., Ltd., etc. (RDA )
Unless needed to identify “corporateness”
Omission of initial articles (RDA )
Unnamed vs. Named conferences
Those inverted references– still exist but are not required any longer 52 52

53. RDA and AACR2: Similarities
Qualifiers and the order in which they are added (if more than one) are the same (RDA )
Need to establish place names used as additions to authorized access points, or at least make sure they have been established already (RDA )
Do not need to establish institutions used as additions to authorized access points for conferences (RDA ) 53 53

54. RDA and AACR2: Differences
May choose brief form over full form (RDA )
Inclusion of periodicity in preferred names for conferences:
Biennial Symposium on Active Control of Vibration and Noise
Create a new NAR for every instance of an ongoing conference cataloged as a monograph (RDA ) 54 54

55. RDA and AACR2: Differences
No “treat as non-government body” rule as in LCRI 24.2.C
More cataloger’s judgment on adding qualifiers – no more LCRI 24.4B
Still required for churches, radio, and TV stations
No limit on addition of location to authorized access points for conferences
New use of subfield $w r $i in place of see-also earlier/later references
PCC is developing recommendations on the use of subfield $r w $i in place of see-also earlier/later references. These recommendations were submitted to the PCC Policy Committee on April 15, Please watch for further developments on policies. 55 55

56. Summary
Do not fear!
If you are a good AACR2 authorities cataloger, you will be a good RDA authorities cataloger
We stressed the similarities here, and you can see there are a lot more similarities than differences, at least for RDA corporate bodies
Most of RDA Chapter 11 is lifted from AACR2 Chapter 24 with little change– but some nice new examples! 56 56

57. Acknowledgments
These presentation slides have been adapted from RDA training materials prepared by the Library of Congress Policy and Standards Division for RDA Refresher Training at the Library of Congress, October 2011