This is intended to be a two day workshop on RDA. This workshop will explore RDA with a specific focus on theories, practicalities, authority work and hands on cataloging. The workshop will take the student through understanding the theories behind RDA and then cataloging by RDA standards.

1. RDA from Scratch for Catalogers
Shana L. McDanold
Head, Metadata Services

2. Introductions and Acknowledgments
 Who am I and why am I teaching this?
 Attendees intro
 Slide content credits:
 Adam Schiff (University of Washington)
 Library of Congress
 Barbara Tillett, Judy Kuhagen, the staff of the Cataloging &
Acquisitions Cooperative and Instructional Programs Division
 Jacquie Samples (Duke U.)
 Joint Steering Committee for the Development of RDA
 And many more who have contributed bits and pieces

3. Course outline
 Day 1
 RDA – where did it come from?
 FRBR – the core concepts
 Authorities  Authorized Access Points
 Bibliographic records
 Day 2
 Bibliographic records (continued)
 Game: is it RDA or AACR2?
 Step by step as a group
 Step by step as individuals
 What’s next? Relationships!
 Wrap-up

4. Cataloging brief history
 Early cataloging codes
 No “one” set for US libraries
 1940s: ALA cataloging rules
 1961 IFLA’s Paris Principles
 Cutter’s Rules for a Printed Dictionary Catalog
 1967: Anglo-American Cataloging Rules (AACR)
 2 versions!: North American text and a British text
 1969: ISBDs (consolidated in 2007)
 1978: Anglo-American Cataloging Rules Revised (AACR2)
 Revisions: 1988, 1998, 2002
 1960s: MARC developed (Henriette Avram)
 Work completed 1969
 US standard by 1971; international standard 1973
 Several “flavors” of MARC

5. So why RDA? And why now?
 AACR2 is based on a card environment, thus it is
limited by that 3x5 inch boundary
 RDA is designed for the web and online
communication, making use of how intertwined the
web is to share information
 From RDA 0.0 Purpose and Scope:
 “RDA provides a set of guidelines and instructions on
formulating data to support resource discovery.”
 “RDA provides a comprehensive set of guidelines and
instructions covering all types of content and media.”

6. So why RDA? And why now?
 RDA Objectives (RDA 0.4.2):
 Responsiveness to user needs
 Cost efficiency
 Flexibility
 Continuity
 RDA Principles (RDA 0.4.3)
 Differentiation
 Sufficiency
 Relationships
 Representation
 Accuracy
 Attribution
 Common usage or practice
 Uniformity

7. So why RDA? And why now?
 Specific RDA Goals
 Easy to use and interpret
 Applicable to an online, networked environment
 Provide effective bibliographic control for all types of
media
 Encourage use beyond library community
 Compatible with other similar standards
 Have a logical structure based on internationally
agreed-upon principles
 Separate content and carrier data, and separate
content from display
 Examples – numerous and appropriate

8. RDA – the birth story
 2005: Final update of AACR2 2002 ed.
 1997: International Conference on the Principles & Future
Development of AACR
 2002: AACR3 development begins
 2003-2007: meetings of the International Cataloguing Principles
(ICP)
 2005: AACR3 renamed RDA: Resource Description and Access
 2006, 2007: drafts of RDA chapters and appendices
 2008: first full draft of RDA
 2009: delivered to the publishers
 2010: first published in the RDA Toolkit
 2010/2011: testing, testing
 2012: re-writing by an editor, other tasks designated by U.S. Test
Coordinating Committee
 March 31, 2013: RDA implementation!

9. RDA – testing, testing
 Goal: assure the operational, technical, and
economic feasibility of RDA
 Who: U.S. RDA Test Coordinating Committee
 Test participants: Library of Congress, National
Agricultural Library, National Library of Medicine, 23
partner institutions
 Timeline:
 June-Sept. 2010: training
 Oct.-Dec. 2010: record creation
 Jan.-Mar. 2011: analyze results
 Apr.-June 2011: report and decision

10. RDA – testing, testing
 Questions answered by the test and the reports
 Does RDA meet the stated goals?
 What is user reaction to the records?
 What is the economic impact?
 How was the data being assessed and collected?
 Review and analysis of records
 Surveys
 Statistics on time
 Record use and impact in shared environment (OCLC,
SkyRiver) to ensure RDA/AACR2 compatibility

11. RDA – testing, testing
 CONCLUSION! Finally.
 Decision published June 13, 2011
 Overarching conclusion:
 “Contingent on the satisfactory progress/completion of the
tasks and action items below, the Coordinating
Committee recommends that RDA should be
implemented by LC,NAL, and NLM no sooner than
January 2013. The three national libraries should commit
resources to ensure progress is made on these activities
that will require significant effort from many in and beyond
the library community.”

12. FRBR family?
 Family:
 FRBR: Functional Requirements for Bibliographic
Records
 FRAD: Functional Requirements for Authority Data
 FRSAD: Functional Requirements for Subject Authority
Data
 Conceptual model used as the foundation for RDA
 FRBR: WEMI attributes/elements (resource)
 FRAD/FRSAD: entitles (persons, corporate bodies) and
subjects (concepts) associated with the resource
 Focus: user tasks and relationships

13. FRBR User Tasks
 Find
 to locate either a single entity or a set of entities as the result of
a search using an attribute or relationship of the entity
 Identify
 to confirm that the entity described corresponds to the entity
sought, or to distinguish between two or more entities with
similar characteristics
 Select
 to choose an entity that meets the user's requirements with
respect to content, physical format, etc., or to reject an entity as
being inappropriate to the user's needs
 Obtain
 to acquire an entity through purchase, loan, etc., or to
access an entity electronically through an online connection

14. FRBR Structure
 Group 1 (WEMI): products of intellectual of artistic
endeavor
 Work
 Expression
 Manifestation
 Item
 Group 2: entitles responsible for Group 1
production/creation
 Person
 Corporate Body
 Family
 Group 3: subjects for works (Group1)
 Concept
 Object
 Event
 Place

15. 15
Work
Expression
Manifestation
Item
is realized through
is embodied in
is exemplified by
Inherent Group 1
Relationships
FRBR Structure – Group 1

16. Original
Work - Same
Expression
Same Work –
New Expression
New WorkCataloging Rules
Cut-Off Point
DerivativeEquivalent Descriptive
Facsimile
Reprint
Exact
Reproduction
Copy
Microform
Reproduction
Variations
or Versions
Translation
Simultaneous
“Publication”
Edition
Revision
Slight
Modification
Expurgated
Edition
Illustrated
Edition
Abridged
Edition
Arrangement
Summary
Abstract
Digest
Change of Genre
Adaptation
Dramatization
Novelization
Screenplay
Libretto
Free
Translation
Same Style or
Thematic Content
Parody
Imitation
Review
Criticism
Annotated
Edition
Casebook
Evaluation
Commentary
Family of Works

17. FRBR Structure - Relationships
17
Work
Expression
Manifestation
Item
is owned by
is produced by
is realized by
is created by
Person
Corporate Body
Family
Relationships
Between Groups 1 and 2

18. FRBR exercise
 What are the identifying elements of the:
 Work
 Expression
 Manifestation
 Item
 Relationship(s)
 Other Group 1 entities?
 Group 2 (person, family, corporate body)?

19. An important distinction
 FRBR
 conceptual model
 RDA/AACR2:
 content standard
 ISBD
 display format/standard
 MARC/MARC21
 communication format
 other communication formats: ONIX, Dublin Core

20. RDA Toolkit
 Tabs
 RDA – text of RDA
 Tools
 RDA element set
 RDA mappings (MARC-RDA; MODS-RDA)
 RDA record examples
 Workflows – can be global (public) or local
 Maps – Metadata Application Profiles
 Entity Relationship Diagrams (FRBR, FRAD, etc.)
 Schemas – element sets
 Resources
 AACR2
 LC-PCC PS (policy statements)
 Other (various links)

21. RDA Toolkit
 Updates
 “When there is a new release for RDA Toolkit, it is made
on the second Tuesday of the month. Releases typically
contain updates to content and metadata, enhancements
to RDA Toolkit functionality, and fixes to existing bugs.”
(RDA Toolkit blog)
 May 14, 2013
 Next: July 9, 2013
 Training
 RDA Toolkit Essentials - FREE

22. Authorities
 Based on attributes and relationships identified in
FRAD
 Person
 Family
 Corporate body
 Place
 Authorized/variant access points and elements will
for now continue to be documented in authority
records

23. Authority records - vocabulary changes
AACR2 RDA
Heading Authorized access point
See reference Variant access point
See also reference Authorized access point for related
entity

24. Authority records – new MARC fields
 046 : associated dates (Work, Expression, Person,
Family, Corporate Body)
 336 : content type (Work, Expression, Person, Family,
Corporate Body)
 370 : associated place (Work, Expression, Person,
Family, Corporate Body)
 371 : address (Person, Family, Corporate Body)
 372 : field of activity (Person, Family, Corporate Body)
 373 : affiliation (Person, Family, Corporate Body)
 374 : occupation (Person, Family, Corporate Body)
 375 : gender (Person)
 376 : family information (Family)
 377 : associated language (Person, Family, Corporate
Body entities)

25. Authority records – new MARC fields
 380 : form of work (Work)
 381 : other distinguishing characteristic of work or
expression (Work, Expression)
 368 : additional corporate body attributes
 378 : fuller form of personal name
 382 : medium of performance (Work)
 383 : numeric designation of a musical work (Work)
 384 : key (Work)

26. Key changes for Authorities
 Authorized access point is based on *usage* or
preferred name
 Date of birth/death are required (if known)
 Spell out born, died, approximately, use – (hyphen) for
open dates
 Include titles or terms associated with surnames
 Such as Junior (Jr.), Senior, etc.
 Separate guidelines for royalty, nobility, religious persons

27. Key changes for Authorities
 Families
 Fictitious persons and real non-human entities can
now be authors
 Treatment of pseudonyms – separate identities
 If pseudonym is preferred and real name is not used,
establish under pseudonym; otherwise establish each
identity separately

28. Key changes for Authorities
 Undifferentiated names – avoid creating
 Options:
 Dates
 Qualifiers
 Titles/designations
 Profession/field of activity
 And more!
 Conferences, Congresses, other events with dates
 Include frequency in the name
 Include number, date, and location

29. Key changes for Authorities
 Uniform titles
 Language: Polyglot no longer used
 Separate authorized access points for each language of
translation
 Works always present
 Selections.  Works. Selections.
 Bible: removal of O.T. and N.T.
 Bible. O.T. Genesis  Bible. Genesis. AND Bible. Old
Testament. (for the whole)
 Koran  Qur’an

30. RDA authority record example(s)
 Identification:
 040 |e rda
 008/10 (Rules) = z (other)

31. Bibliographic records
 RDA is fundamentally different in it's approach to
describing materials/resources/things
 Focus on content *first* and carrier/format second
 RDA cultivates relationships
 “Guidelines and instructions” rather than rules
 Cataloger’s judgment
 MARC record contains a mix of Group 1 WEMI
attributes as well as Group 2 and Group 3 entities.

32. Bib records – vocabulary changes
AACR2 RDA
Heading Authorized access point
Author, composer, artist, etc. Creator
Main entry Preferred title, and, if appropriate, authorized
access point for the creator
Uniform title Two RDA counterparts:
1. Preferred title + differentiating information
2. Conventional collective title like “works”
Physical description Carrier description
General material designator
(GMD)
Three elements:
1. Content type
2. Media type
3. Carrier type
Chief source Preferred source(s)

33. Bib records – new MARC fields
 336 – content type
 337 – media type
 338 – carrier type
 344 – sound characteristics
 345 – projection characteristics of moving image
 346 – video characteristics
 347 – digital file characteristics
 264 – production, publication, distribution,
manufacture, and copyright notice
 New subfields for relationships
 New subfields to parse 502 Dissertation information

34. Bib records - vocabularies
 Registered and controlled

35. Key changes for Bibs
 Transcription – record what’s there!
 Source(s)
 Relationships for authorized access points
 *Required* for the creator
 Rule of three – gone!
 Be liberal in recording alternate titles
 Related works are no longer in a general note field,
but rather traced so they can be linked
 GMD replaced by 336 (content type), 337 (media
type), 338 (carrier type)

36. Key changes for Bibs
 Spelling out of abbreviations
 p.  pages
 ill.  illustrations
 cm is not an abbreviation, it is a symbol, like ©
 Latin terms no longer used
 [S.l. : s.n.]  [Place of publication not identified] :
[publisher not identified]
 [et al.]  [and # others]
 [sic]  245 has title as appears on piece; 246 contains
corrected form of title
 Adjacent bracketed elements are bracketed
separately

37. RDA bib record example(s)
 Identification:
 040 |e rda
 LDR/18 (Desc) = i (ISBD), c (ISBD not included), blank
(non-ISBD)

38. RDA or AACR2?

39. RDA or AACR2?

40. RDA or AACR2?

41. RDA or AACR2?

42. RDA or AACR2?
 Hybrid records

43. Hands on practice!
 Group record creation
 Individual record creation

44. Image created by:
Jennifer Young
Northwestern University

45. What’s next?
 BIBFRAME
 Linked Data and the Semantic Web
 Tools
 Bibframe.org
 RIMMF – RDA in Many Metadata Formats
 VTLS Sandbox (subscription) – “FRBRize” records
 Linkeddata.org

46. Wrap-up
??

47. Image created by:
Jennifer Young
Northwestern University