Describing archives: A Content Standard. Chicago: Society of American Archivists, 2004
Attached is a draft of RDA Part B – Access point control.
The base text of instructions included in the draft is derived from the current version of AACR2, incorporating the 2005 amendments. The number in square brackets at the end of the first paragraph under each caption indicates the AACR2 rule from which the base text was derived.
Note: There are a number of special characters used in AACR2 chapters 22-26 (particularly in examples of romanized names and titles) that are not supported in the standard fonts available in MS Word. For the purposes of this draft, those special characters have been replaced with the corresponding roman alphabet character (without the required diacritic) highlighted in yellow.
The organization of the draft chapters follows the outline accompanying the revised RDA Prospectus. The base text has been reformatted using the RDA template, and minor editorial changes have been made.
Changes related to instructions covered by Part B put forward in the following proposals have been deferred pending discussion of the proposals and responses by JSC at its upcoming meeting:
Key issues that need to be addressed by JSC in reviewing the draft are highlighted below.
The elements included in the draft reflect the attributes defined in Functional Requirements for Authority Data (FRAD) for the following entities: person, family, corporate body, place, work, and expression.
The inclusion of elements to reflect the attributes of manifestation and item defined in FRAD has been deferred pending discussion with JSC on the need for those elements.
Attributes defined in FRAD for the entities concept, object, and event have been excluded pending further discussion on the coverage of “subject” elements in RDA.
The FRAD entities name, identifier, and controlled access point are covered to the extent that they pertain to the entities person, family, corporatebody, place, work, and expression. Certain attributes of name, identifier, and controlledaccesspoint—e.g., scope of usage, dates of usage, source of controlled access point—are encompassed by the elements defined under sections 14.8 (citing sources consulted) and 14.9 (cataloguer’s notes). Attributes of name, identifier, and controlledaccesspoint that would normally be reflected only through content designation—e.g., type of name, language of name, script of name, status of controlled access point—have been excluded.
Attributes defined in FRAD for the entities rules and agency have been excluded pending discussion on the desirability of extending the scope of RDA to include elements identifying the agency responsible for creating the data and the standards used to formulate the data. If such an extension is considered desirable, the additional elements should probably be covered in a separate section (Part C) that would be applicable to both descriptive data and access control data.
The relationships defined in FRAD that operate between instances of the entities person, family, corporatebody, and work as well as those between instances of the entities name and title and the persons, families, corporate bodies, and works known by those names and titles are encompassed by the “references” elements in Part B. The relationships between instances of the entity controlled access point defined in FRAD (e.g., parallel language relationship, alternate script relationship) have been excluded pending discussion on the desirability of extending the scope of RDA to include elements to reflect those relationships.
2. Relationship to other standards for access point control
The inclusion of citations for other standards for access point control in section 0.2.1 of the Introduction to Part B has been deferred pending discussion of 5JSC/ALA/3 and the ALA follow-up.
3. Functional objectives and principles of access point control
The section on functional objectives and principles of access point control in the Introduction to Part B (0.2.2) parallels the revised text for the RDA Objectives and Principles document, incorporating changes discussed at the April 2006 JSC meeting.
An attempt has been made to bring the text in the Objectives and Principles document and in section 0.2.2 of the Introduction to Part B into line with the April 3, 2006 draft of the IME-ICC Statement of International Cataloguing Principles.
JSC now needs to assess whether the degree of alignment with the IME-ICC Statement is adequate, and whether the guidelines and instructions in Part B are consistent with the principles as stated. Specific RDA guidelines and instructions that should be reviewed in the context of the IME-ICC Statement include the following:
18.104.22.168 (re names of persons in more than one language)
22.214.171.124 (re names of persons written in a nonroman script)
126.96.36.199 (re romanization of names of corporate bodies)
188.8.131.52 (re names of corporate bodies in more than one language)
184.108.40.206 (re names of international bodies)
220.127.116.11 (re conventional names for corporate bodies)
12.1.1 (re the English form of name for a place)
12.1.2 (re the vernacular form of name for a place)
18.104.22.168 (re romanization of titles)
13.2.1 (re titles of works created after 1500)
13.2.2 (re titles of works created before 1501)
13.4.1 (re choosing the preferred title for a musical work)
13.5.1 (re titles for laws)
13.5.2 (re titles for treaties)
13.6.0 (re titles for sacred scriptures)
13.7.0 (re titles for liturgical works, theological creeds, confessions of faith, etc.)
13.8.1 (re titles for official communications of the pope)
13.8.2 (re titles for official communications of the Roman Curia)
13.9.0 (re titles for manuscripts and manuscript groups)