Background and Overview of RDA

1. Background and Overview of RDA By Rodolfo Y. Tarlit

2. RDA • Stands for “Resource Description and Access” • Final draft • 17 November 2008 for comments and discussion • 2009 February deadline for submission of comments and recommendations • Library of Congress, National Library of Medicine, National Agricultural Library suggested further study before RDA is implemented • 2009 March JSC of RDA has responded to these comments and recommendations • 2010 for implementation

3. Why RDA? • Filipino Librarians community seemed to have: • Not heard about RDA • No interest • Thank PAARL for inviting me to present RDA even for backgrounder only to: • Steer Filipino librarians to take a look at RDA • I do not want us to be caught flatfooted when it is finally implemented

4. Historical Background on the Development of RDA • AACR 3 (Anglo-American Cataloging Rules, 3rd edition) • International Conference on the Principles and Future Development of AACR (1997 : Toronto) • As a respond to repeated calls for fundamental revisions of AACR 2 • address issues, taking into account present and future trends in information resources and information management

5. Historical Background on the Development of RDA • review the underlying principles of AACR, with a view to determining whether fundamental rule revision is appropriate and feasible and, if so, advising on the direction and nature of those revisions.

6. 9 Basic Papers Presented at the Conference • The Principles of AACR," by Michael Gorman and Pat Oddy address some fundamental questions. Are the present AACR principles still valid for all media? Do the rules need simplifying? Are the rules flexible and responsive to change? What risks are involved in change? In what way do rule interpretations undermine AACR principles?

7. Basic Papers Presented at the Conference • "Bibliographic Universe (Functional Requirements)" by Tom Delsey, describes some models of the bibliographic universe developed by various individuals and groups, and evaluate them in terms of accuracy, flexibility, efficiency, user-friendliness, and compatibility.

8. Basic Papers Presented at the Conference • "AACR2 and Catalogue Production Technology," Rahmatollah Fattahi of Iran examines to what extent the rules in AACR2 match or fail to match the capabilities of present systems and those of the near future or searching, retrieval, and presentation of bibliographic information.

9. Basic Papers Presented at the Conference • "The Work," by Martha Yee, discusses the question "What is a work?" by reviewing AACR2 rules by which a decision is made about whether an item is, or is not, to be considered a new work. Much of the paper is devoted to the problems that result from the lack of general rules for works of mixed responsibility.

10. Basic Papers Presented at the Conference • "Bibliographic Relationships," Sherry Vellucci discusses bibliographic relationships in terms of various linkages; their importance to users of bibliographic records and users of authority records; in the MARC environment; and in a relational database environment.

11. Basic Papers Presented at the Conference • Crystal Craham and Jean Hirons detail "Issues Related to Seriality: Defining On-going Publications." They believe that the definition of "serial" in AACR2 is no longer adequate, that a broader concept of "on-Going work" is needed. They also argue that the book-based chapter 1 and the paper-based chapter 12 do not accommodate the needs of all on-going library materials.

12. Basic Papers Presented at the Conference • "Principal Access Points," by Ronald Hagler deals with main entry and corporate body entry and their relationship to uniform titles and titles proper, the MARC format, and the need to restructure authority files to reflect the capabilities of computerization.

13. Basic Papers Presented at the Conference • "Content vs Carrier," by Lynne Howarth queries whether this fundamental rule should be retained, tinkered with, or reconstructed. Practical considerations, present realities, and international consequences are discussed.

14. Basic Papers Presented at the Conference • Mick Ridley presents "Beyond MARC." How effective is MARC? Is MARC simply an embodiment of AACR? Do we need a transfer standard for catalogue records? What is a good structure/format for catalogue records? Is the same structure/format needed for transfer, database storage, and presentation to users?

15. Results of the Conference • JSC identified a number of action items which constituted a major part of the working agenda for the Committee from 1997 to 2002 • document the basic principles that underlie the rules in AACR 2 • explore into content versus carrier and challenge the logical structure of AACR.

16. From AACR 2 to AACR 3 to RDA • By April 2005, the plan had changed. The reactions to the initial draft of AACR3 particularly raised concerns about the need to move closer to alignment with the FRBR model and to build an element set. So, a new structure and plan were developed and the name was changed to Resource Description and Access to emphasize the two important tasks of description and access and a break from the past. The Anglo-American emphasis was removed so RDA could take a more international view.

17. Composition of the JSC • Joint Steering Committee for Revision of AACR (JSC AACR) • Joint Steering Committee for Development of RDA (JSC RDA) • The American Library Association • The Australian Committee on Cataloguing • The British Library • The Canadian Committee on Cataloguing • CILIP: Chartered Institute of Library and Information Professionals • The Library of Congress • The current Chair of JSC is Alan Danskin, the British Library representative.

18. RDA: Purpose and Scope • Data created using RDA to describe a resource are designed to assist users performing the following tasks: • find – i.e., to find resources that correspond to the user’s stated search criteria • identify – i.e., to confirm that the resource described corresponds to the resource sought, or to distinguish between two or more resources with similar characteristics

19. RDA: Purpose and Scope • Data created using RDA to describe a resource are designed to assist users performing the following tasks: • select – i.e., to select a resource that is appropriate to the user’s needs • obtain – i.e., to acquire or access the resource described

20. RDA: Purpose and Scope • Data created using RDA to describe an entity associated with a resource (a person, family, corporate body, concepts, etc.) are designed to assist users performing the following tasks: • find – i.e., to find information on that entity and on resources associated with the entity • identify – i.e., to confirm that the entity described corresponds to the entity sought, or to distinguish between two or more entities with similar names, etc.

21. RDA: Purpose and Scope • Data created using RDA to describe an entity associated with a resource (a person, family, corporate body, concepts, etc.) are designed to assist users performing the following tasks: • clarity – i.e., to clarify the relationship between two or more such entities, or to clarify the relationship between the entity described and a name by which that entity is known • understand – i.e., to understand why a particular name or title, or form of name or title, has been chosen as the preferred name or title for the entity.

22. RDA: Key Features • RDA provides a flexible and extensible framework for the description of resources produced and disseminated using state-of-the art technologies • Also serves the needs of agencies organizing resources produced in non-digital formats.

23. RDA: Key Features • RDA is designed to take advantage of the efficiencies and flexibility in data capture, storage, retrieval, and display made possible with newer database technologies, but to be compatible as well with the legacy technologies still used in many resource discovery applications

24. RDA: Key Features • In order to optimize flexibility in the storage and display of the data produced using RDA, a clear line of separation has been established between the guidelines and instructions on recording data and those on the presentation of data. Guidelines and instructions on recording data are covered in chapters 1 – 32; those on the presentation of data are covered in appendices D and E.

25. Relationship to Other Standards for Resource Description and Access • AACR and cataloging traditions on which it was based ((Rules for a Dictionary Catalog by Charles A. Cutter, Paris Principles 1961 (1963 Report), and Seymour Lubetzky’s Principles of Cataloging: Final Report. Phase I: Descriptive Cataloging).

26. Relationship to Other Standards for Resource Description and Access • ISBD • MARC 21 Format for Authority Data. • Dublin Core

27. Conceptual Models Underlying RDA • Alignment with FRBR. The data elements describing a resource that are covered in RDA generally reflect the attributes and relationships associated with the entities work, expression, manifestation, and item, that are defined in FRBR: • work – a distinct intellectual or artistic creation (i.e., the intellectual or artistic content)

28. Conceptual Models Underlying RDA • Alignment with FRBR • expression – the intellectual or artistic realization of a work in the form of alpha-numeric, musical or choreographic notation, sound, image, object, movement, etc., or any combination of such forms • manifestation – the physical embodiment of an expression of a work • item – a single exemplar or instance of a manifestation

29. Conceptual Models Underlying RDA • Alignment with FRAD. The data elements describing entities associated with a resource that are covered in RDA generally reflect the attributes and relationships associated with the entities person, family, corporate body, and place, that are defined in FRAD: • person – a human or non-human individual or to an identity established by an individual (either alone or in collaboration with one or more other individuals)

30. Conceptual Models Underlying RDA • Alignment with FRAD • family – two or more persons identified as a family unit • 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. • place – a location identified by a name.

31. Objectives and Principles Governing RDA • Objectives 1. Responsiveness to User Needs. The data should enable the user to: • find resources that correspond to the user’s stated search criteria; • find all resources associated that embody a particular work or a particular expression of that work • find all resources associated with a particular person, family, or corporate body;

32. Objectives and Principles Governing RDA • find all resources in a given subject; • find works, expressions, manifestations, and items that are related to those retrieved in response to the user’s search; • find persons, families, and corporate bodies that correspond to the user’s stated search criteria;

33. Objectives and Principles Governing RDA • find the resource described (i.e., confirm that the resource described corresponds to the resource to the resource sought, or distinguish between two or more resources with the same name or similar characteristics); • identify the person, family, or corporate body represented by the data (i.e., confirm that the entity described corresponds to the entity sought, or distinguish between two or more entities with the same or similar names, etc.);

34. Objectives and Principles Governing RDA • select a resource that is appropriate to the user’s requirements with respect to the physical characteristics of the carrier and the formatting and coding of information stored on the carrier; • select a resource appropriate to the user’s requirements with respect to form, intended audience, language, etc.;

35. Objectives and Principles Governing RDA • obtain a resource (i.e., acquire a resource through purchase, loan, etc., or access a resource electronically through an online connection to a remote computer); • understand therelationship between two or more entities;

36. Objectives and Principles Governing RDA • understand the relationship between the entity described and a name by which that entity is known (e.g., a different language form of the name); • understand why a particular name or title, or form of name or title, has been chosen as the preferred name or title for the entity.

37. Objectives and Principles Governing RDA 2. Cost Efficiency. The data should meet functional requirements for the support of user tasks in a cost-efficient manner. 3. Flexibility. The data should function independently of the format, medium, or system used to store or communicate the data. They should be amenable to use in a variety of environments. 4. Continuity. The data should be amenable to integration into existing databases particularly those developed using AACR and related standards) with a minimum of retrospective adjustment to those databases.

38. Objectives and Principles Governing RDA • Principles • 1. Differentiation. The data describing a resource should differentiate that resource from other resources. The data describing an entity associated with a resource should differentiate that entity from other entities, and from other identities used by the same entity.

39. Objectives and Principles Governing RDA • 2. Sufficiency. The data describing a resource should be sufficient to meet the needs of the user with respect to selection of an appropriate resource.

40. Objectives and Principles Governing RDA • 2. Sufficiency. The data describing a resource should be sufficient to meet the needs of the user with respect to selection of an appropriate resource. • 3. Relationships. The data describing a resource should indicate significant relationships between the resource described and other resources. The data describing an entity associated with a resource should reflect all significant bibliographic relationships between that entity and other such entities.

41. Objectives and Principles Governing RDA • 4.Representation. The data describing a resource should reflect the resource’s representation of itself. • 5.Accuracy. The data describing a resource should provide supplementary information to correct or clarify ambiguous, unintelligible, or misleading representations made on sources of information forming part of the resource itself.

42. Objectives and Principles Governing RDA • 6. Attribution. The data recording relationships between a resource and a person, family, or corporate body within that resource should reflect attributions or responsibility made either in the resource itself or in reference sources, irrespective of whether the attribution of responsibility is accurate.

43. Objectives and Principles Governing RDA • 7.Language Preference. The name or form of name designated as the preferred name for a person, family, or corporate body should be name or form of name found in resources associated with that person, family, or corporate body in the original language and script of the content.

45. Objectives and Principles Governing RDA • 8.Common Usage or Pratice. Data that is not transcribed from the resource itself should reflect common usage. The part of the name of a person or family used as the first element in recording the preferred name for that person or family should reflect conventions used in the country and language most closely associated with the person or family.

46. Objectives and Principles Governing RDA • 9.Uniformity. The appendices on capitalization, abbreviations, order of elements, punctuation, etc., should serve to promote uniformity in the presentation of data describing a resource or an associated with a resource.

47. Structure of RDA • Section 1: Recording Attributes of Manifestation and Item • Chapter 1: General Guidelines On Recording Attributes of Manifestations and Items • Chapter 2: Identifying Manifestations and Items [that are most commonly used to identify a resource] • Chapter 3: Describing Carriers [to select a resource appropriate to the user’s requirements with respect to format and encoding] • Chapter 4: Providing Acquisition and Access Information [to obtain a resource]

48. Structure of RDA • Section 2: Recording Attributes of Work and Expression • Chapter 5: General Guidelines on Recording Attributes of Works and Expressions • Chapter 6: Identifying Works and Expressions [that are most commonly used to identify a work or expression] • Chapter 7: Describing Content [to select a work or expression appropriate to the user’s requirements with respect to content]

49. Structure of RDA • Section 3: Recording Attributes of Person, Family, and Corporate Body • Chapter 8: General Guidelines on Recording Attributes of Persons, Families, and Corporate Bodies • Chapter 9: Identifying Persons • Chapter 10: Identifying Families • Chapter 11: Identifying Corporate Bodies

50. Structure of RDA • Section 4: Recording Attributes of Concept, Object, Event, and Place • Chapter 12 [Placeholder]: General Guidelines on Recording Attributes of Concept, Object, Event, and Place • Chapter 13 [Placeholder]: Identifying Concept • Chapter 14 [Placeholder]: Identifying Object • Chapter 15 [Placeholder]: Identifying Event • Chapter 16: Identifying Place