RDA 101: an introduction to RDA (2012)

RDA 101: an introduction
to RDA
Presented by Alison Hitchens (University of
Waterloo Library)
To Ontario Association of Library Technicians /
Association des bibliotechniciens de l'Ontario
(OALT/ABO) Conference, May 5, 2012
OALT/ABO-Hitchens-2012
1

Many thanks!
• To all of those cataloguers and presenters who
are letting us re-use their presentations in
preparation for RDA!
• Special thanks to Chris Oliver for use of many
slides from the following presentations:
• “What is RDA and why do I need to know?” Presented
at CLA Montreal Chapter March 9, 2011.
• “RDA: the framework : structure, principles,
concepts.”Presented at CASLIS RDA Workshop,
October, 2010.
• “RDA: a quick introduction.” Presented at OLA
Superconference, February 2, 2011.
2

Agenda
• What is RDA?
• FRBR/FRAD in RDA
• Objectives & Principles
• Data Elements & Extensible Framework
• Implementation & Training
3

WHAT IS RDA? 4

Road to RDA
• more resources– in numbers and in type
• more record sharing internationally
• more bulk loading of large files
• more demand for record enrichment
• metadata is everywhere and encoded in
many ways
• more and more data sharing
• Semantic Web and linked data on the
horizon 5

Road to RDA
• International Conference on the Principles &
Future Development of AACR, Toronto
(1997)
• principles of record creation
• basis for description: content vs. carrier
• is there a logical structure to AACR2?
• how do the rules deal with seriality?
• internationalization of cataloguing rules
6

Road to RDA
IME ICC Statement of International Cataloguing
Principles
• 5 regional meetings between 2003 and 2007 (one per
continent)
From the introduction:
• replaces and broadens the scope of the Paris Principles
• from just textual works to all types of materials
• from just the choice and form of entry to all aspects of
bibliographic and authority data
• Includes guiding rules that should be included in
cataloguing codes internationally
• includes guidance on search and retrieval capabilities
7

What is RDA?
• RDA = Resource Description and Access
• a content standard to replace AACR2*
• not based on the catalogue card format
• not based on MARC21 practices
• based on conceptual models created by IFLA*
• Functional Requirements for Bibliographic
Records (FRBR)
• Functional Requirements of Authority Data
(FRAD)
*Anglo-American Cataloguing Rules, Second edition
*International Federation of Library Associations and Institutions 8

What is RDA?
• designed for working online
• designed to describe all types of resources,
including those accessed online
• aims to be flexible and extensible
• going to help us create well-formed
metadata that will improve our systems and
therefore the user experience in the future
9
Modified from: Grover (2011: slide 4)

AACR2 RDA
• continue to record the title
• continue to record the edition
• continue to record the date of publication
But …
• new vocabulary
• new way of thinking about how we do these steps
10
Source: Oliver (Mar. 2011: slide 11)

Continuity with AACR2
• RDA includes instructions that originate from AACR2
• instructions derived from AACR2 are reworked:
• reworded
• organized differently
• within a new theoretical framework
every word has
changed
RDA instructions
show visible
continuity with
AACR2
11
Source: Oliver (Feb. 2011: slide 4)

Example
AACR2 1.5B1
Record the extent of the
item by giving the
number of physical units
in arabic numerals and
the specific material
designation as instructed
in subrule .5B in the
chapter dealing with the
type of material to which
the item belongs.
1 film reel
RDA 3.4.1.3
Record the extent of the
resource by giving the
number of units and an
appropriate term for the
type of carrier as listed
under 3.3.1.3
1 film reel
12

Broader scope than AACR2
RDA 0.0 Purpose and scope
RDA provides a set of guidelines and
instructions on formulating data to support
resource discovery.
versus AACR2 0.1
These rules are designed for use in the
construction of catalogues and other lists in
general libraries of all sizes.
13

Broader scope than AACR2
• bibliographic data
authority data
• more international
• beyond “Anglo-American”
• instructions made consistent and easy to use by many
cultural, religious, national communities
for example, options for the use of other languages,
scripts, calendars, numeric systems
14

New terminology
headings
physical description
main entry
see reference
see also reference
access points
description of the carrier
preferred access point
representing a work or
expression
variant access point
authorized access point
for a related entity
15

Why is RDA important?
• designed to improve resource discovery for the user
• puts the user at the centre
• bibliographic data how it is used
• designed as a metadata standard
• data elements
• instructions on how to record values for those
elements
• controlled vocabularies
• overall structure governed by a formal model 16

Designed for now and the future
Now
• designed to work in
current catalogues
• compatible with AACR2
records
• co-exist with AACR2
records in the same
databases
Future
• ready to take advantage
of new database
structures
• function in the semantic
web, linked data
environment
• visible in the web
alongside other types of
metadata
17

What you need to know to understand
the changes
• user tasks
• entities, attributes, relationships
• organization and structure of RDA
• principles
• data elements
• core elements
• extensible framework
18
Source: Oliver (Oct. 2010: slide 10)
FRBR/FRAD
ICP
practical design

FRBR/FRAD IN RDA
User tasks
Entities, attributes, relationships
Organization and structure of RDA
19

Focus on the user
0.0
• RDA provides a set of guidelines and instructions on
formulating data to support resource discovery.
• The data created using RDA to describe a resource are
designed to assist users performing the following tasks:
Find
Identify
Select
Obtain
20

Consistent focus on the user
Throughout RDA:
why record this data?
to support the user in completing one
of the user tasks
• user tasks come from FRBR/FRAD models
• user tasks are an essential part of RDA
21

Functional objectives
• Each section of RDA begins with functional
objectives and principles specific to the
section
• relationship between the data and the user tasks
(recorded or formulated according to the instructions in that
section)
22

Example from Section 1
Section 1= Recording attributes of manifestations & items
1.2 Functional Objectives and Principles
The data describing a manifestation or item should enable the user
to:
a) find manifestations and items that correspond to the user’s
stated search criteria
b) identify the resource described …
c) select a resource that is appropriate to the user’s
requirements with respect to the physical characteristics of
the carrier and the formatting and encoding of information…
d) obtain a resource …
23

User tasks and cataloguer judgment
• user tasks provide scope that permits cataloguer
judgment
That is, the cataloguer determines if the data is
important for the successful completion of a user task
for example, from 3.7 Applied material
Record the applied material used in the resource if it
is considered important for identification or
selection …
24

Entities, attributes, relationships
• vocabulary of FRBR and FRAD
• entity = the object of a user’s interest
• That is, entities that are of interest to someone who uses
bibliographic and authority data
• RDA includes:
bibliographic entities
entities specific to authority control
25

Bibliographic entities
work
expression
manifestation
item
person
family
corporate body
concept
object
event
place
FRBR Group 1
products of intellectual or
artistic endeavor
FRBR Group 2
responsible for group 1
entities
FRBR Group 3
subjects (includes group
1 & 2)
26

As a user ...
• I need to read the novel for an English exam
I want access to the WORK
work = a distinct intellectual or artistic creation
• I want an audio version for commuting
I need to find a particular EXPRESSION
expression = 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
27

As a user ...
• I prefer a paperback copy when traveling
I want a particular MANIFESTATION
manifestation = physical embodiment of an expression
of a work
• I need to find the copy I borrowed, it is overdue
I need a particular ITEM
item= single exemplar or instance of a Manifestation
28

29
4 entities –
1 object
an item in Ryerson’s
collection
one example of the
Beach Holme
Publishing
manifestation
an embodiment of the
original English
expression
a realization of the work
by M. Crummey
Source: Grover (2011: slide 12)

As library staff ...
• we build our collections by selecting manifestations
that we want to buy
• we select manifestations
• for the expression that the manifestation embodies
• for a manifestation attribute such as the type of
carrier (e.g. print volume or online resource)
• our bibliographic records are records for
manifestations
• we buy, receive, label, barcode and loan items that
are exemplars of the manifestation
30
Modified from: Oliver (Mar. 2011: slide 30)

Entities have Attributes
• characteristics of the entity
• data to be recorded about the entity
Examples:
work: title, genre, coordinates (map)
manifestation: publisher, date of publication, extent of the
carrier
item: identifier (e.g. barcode), provenance, condition
person: dates, gender, a title of rank or office
corporate body: place, dates, address
object: term
31

Entities have Relationships
• link between one entity and another
• basis for navigation and support collocation
• Types of relationships:
• between work, expression, manifestation and
item
• between a person, family or corporate body and
a resource
• between one resource and another resource
• between a person, family or corporate body and
another person, family or corporate body 32
Modified from: Oliver (Feb. 2011: slide 26)

Examples of relationships
expression translation of work
item exemplar of manifestation
work created by person
item owned by family
manifestation produced by corporate body
work based on work
manifestation electronic reprod. manifestation
person member of family
family founded corporate body
33

Relationship designators
afterimage / by Robert Chafe ;
adapted from the short story by
Michael Crummey.
Chafe, Robert, author.
adaptation of (work) :
Crummey, Michael. After image 34
Source: Grover (2011: slide 21)

Search the current online
catalog:
35

FRBR: leads to better grouping
36
• texts
• translations of text
• audio-books
• dramatizations
• adaptations as a
motion picture
• criticisms

work – Sunshine sketches
of a little town
Person – Stephen Leacock
author
work – Afternoons in Utopia
Lahontan’s voyages
editor
date of birth -- 1869
date of death -- 1944
country – Canada
profession – author, professor
affiliation – McGill University
Text
English
Text
French
spoken word
realized
author
manifestation – Sunshine
sketches of a little town
Toronto : McClelland &
Stewart, 1931
manifested
item – signed
copy
exemplar
autographer
37
Source: Oliver (2012: slide 18)

FRAD in RDA
• scope of RDA:
bibliographic data authority data
• attributes of person, family, corporate body,
place
• role of identifiers
• relationship between name + entity
38

Authority entities
bibliographic entities
name
identifier
controlled access
point
(in RDA = authorized access
point)
rules
agency
entities on which
authority data is
focused
entities for authority
control
entities that
determine the
content and form of
access points 39

Example FRAD Attributes
Person
• dates
• place of birth
• field of activity
• affiliation
• language
• gender
Name
• name string
• scope of usage
• dates of usage
• language
• script
40

Example RDA authority record
046 $f 1931 date of birth
100 $a Munro, Alice
370 $a Wingham, Ont. $c Canada $e Clinton, Ont.
374 $a short-story writer occupation
375 $a female gender
377 $a eng language that she writes in
378 $q Alice Ann fuller form of name
400 $a Laidlaw, Alice Ann variant name
678 $a Alice Ann Munro (née Laidlaw) is a Canadian
short-story writer and three-time winner of Canada’s
Governor General Award for English-language
fiction...
41
Place of birth; associated
country; place of residence

Can you imagine the
possibilities for display?
• Alice Munro (short-story writer)
• Alice Munro
• Canadian short story-writer born in 1931
• Alice Munro
• Also known as Alice Ann Munro and Alice Laidlaw
• Alice Munro
• Who is this?
• Alice Munro
42

We are family!
• RDA recognizes families as entities that can
be responsible for or related to a resource
• Definition: “two or more persons related by
birth, marriage, adoption, civil union, or similar
legal status, or who otherwise present
themselves as a family” (RDA 8.1.2)
• Role: creators, contributors etc.
• Important for archives, museums, special
collections, genealogy newsletters, family
reunion publications etc. 43
Modified from: Library of Congress (2011: slide 36)

Family example
046 $s 1869 $t 1999 associated dates
100 3# $a Eaton (Family : $d 1869-1999 : $c Toronto, Ont.)
370 $e Toronto, Ont. Place of residence
376 $a Family $b Eaton, Timothy, $d 1834-1907
type of family; prominent member
678 0# $a Timothy Eaton was born in March 1834 in
Ballymena, Northern Ireland. At the age of 20 he moved to
Ontario. He married Margaret Beattie in 1862 and had 5
children. He opened a dry goods store in 1869 in Toronto
which was the cornerstone for the large Canadian retail chain
Eaton's. John Craig Eaton inherited the business in 1907...
The business finally went bankrupt in 1999
family history
44

Organization & Structure of RDA
• 2 main parts
Recording attributes sections 1-4
of works, expressions, manifestations, items
of persons, families, corporate bodies
Recording relationships sections 5-10
primary relationships
relationships between works, expressions,
manifestations, items
relationships to persons, families, corporate bodies
• Divided into 10 sections
sections are organized according to the bibliographic entities
45

Organization & Structure of RDA
• each chapter associated with a user task
Chapter 1: General guidelines on recording
attributes of manifestations and items
Chapter 2: Identifying manifestations and items
User task = Identify
Chapter 3: Describing carriers
User task = Select
Chapter 4: Providing acquisition & access
information
User task = Obtain
46

Comparing AACR2 and RDA
Ch.1: General rules for description
Ch. 2: Books, pamphlets, printed
sheets
Ch. 3: Cartographic materials
Ch. 4: Manuscripts
Ch. 5: Music
Ch. 6: Sound recordings
Ch.: Motion pictures &
videorecordings
Ch. 8: Graphic materials
Ch. 9: Electronic resources
Ch. 10: 3D artefacts and realia
Ch. 11: Microforms
Ch. 12: Continuing resources
Ch. 13: Analysis
Section 1: Recording attributes
of manifestation and item
1: General guidelines on recording
attributes…
2: Identifying manifestations &
items
3: Describing carriers
4: Providing acquisition & access
information
Section 2: Recording attributes
of work and expression
5: General guidelines on recording
attributes of works & expressions
6: Identifying works & expressions
7: Describing content
47

Lost in RDA? There’s a tool for that!
48
Screen image from the RDA Toolkit (www.rdatoolkit.org) used by permission of the Co-Publishers for RDA (American Library Association,
Canadian Library Association, and CILIP: Chartered Institute of Library and Information Professionals)

RDA OBJECTIVES & PRINCIPLES 49

RDA Objectives & Principles
RDA and ICP both released final text in 2009
• ICP and RDA developed in sync
• ICP “informs” RDA principles
no. 1 for ICP and RDA
• Responsiveness to User Needs (RDA)
• Convenience of the User (ICP)
50
Modified from : Oliver (Oct. 2010: slide 40)

RDA Objectives & Principles
Objectives
• responsiveness to
user needs
• cost efficiency
• flexibility
• continuity
Principles
• differentiation
• sufficiency
• relationships
• representation
• accuracy
• attribution
• common usage or
practice
• uniformity
51

Role of Objectives & Principles
• instructions must be defensible + not arbitrary
• real impact on the content of RDA
for example: 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.
52

Result: RDA as a Content Standard
“what data should I record?”
RDA can be encoded using different
encoding schema
e.g. MARC 21, MODS, Dublin Core, etc.
RDA data can be displayed using different
display conventions
e.g. ISBD, label display, etc.
53

Impact on Examples in RDA
examples show what the data should be
RDA 2.4.1.4 Recording Statements of Responsibility
Transcribe a statement of responsibility in the form in which
it appears on the source of information. Apply the general
guidelines on transcription given under 1.7.
EXAMPLE
by Walter de la Mare
Fats Waller
by Dr. Johnson
by Sir Richard Acland
by Alfred, Lord Tennyson
by a Lady of Quality
par Charles M. Schultz
directed and produced by the Beatles
54

Compared to AACR2/MARC
RDA examples show what the data should be
not how it should be displayed
not how it should be encoded
AACR2: 2.1F1. Transcribe statements of responsibility
relating to persons or bodies as instructed in 1.1F
Shut up in Paris / by Nathan Sheppard
Great Britain : handbook for travellers / by Karl Baedecker
Vas-y, Charlie Brown / par Charles M. Schulz
MARC 21 manual: 245 $c statement of responsibility, etc.
245 04$aThe plays of Oscar Wilde /$cAlan Bird.
245 10$aHow to play chess /$cKevin Wicker ; with a
foreword by David Pritchard ; illustrated by Karel Feuerstein.
55

Role of Objectives & Principles
For example: representation
The data describing a resource should reflect
the resource’s representation of itself.
result = impact on instructions about transcription
2.5.1.4 Recording Edition Statements
Transcribe an edition statement as it appears on the
source of information.
 no instruction to use abbreviations
 transcribe what is on the source of information 56

Fewer abbreviations
• Don’t introduce abbreviations – accurate
representation
57
On title page:
3rd ed.
Second edition
Data recorded:
3rd ed.
Second edition
• Don’t use abbreviations - responsiveness to user
need
Publisher: [place of publication not identified] : Fishy Press, 2011
Extent: x, 143 pages : illustrations, portraits ; 22 cm

What does fewer
abbreviations mean?
• Accurate data – expressing what is actually
on the resource
• Clarity – users do not have to translate
things like ill., port., v., s.l., et al.
• Display – displays will be a little wordier
• Typing – cataloguers will be thankful for
macros!
58

For example: Accuracy
59
AACR2
Title: The wolrd [sic] of
television.
Variant title: The world
of television.
RDA
Title: The wolrd of
television.
Variant title: Title should
read: The world
of television.
• Not second guessing the marketing decisions
• Accurate for citations
• Predictable for search
• Important for bulk-loading of records and for re-use of
metadata

Not Arbitrary: Goodbye rule of 3!
5 by five: five poems by five poets/ Danielle
Bizzaro, Jeff Carroll, Andrea Denny-Brown,
Sarah Hannah, Roberta Pestka.
• AACR2 - just give an access point for
Danielle Bizzaro
• What if a user wanted everything we had by
Sarah Hannah?
• RDA – option to give access points for all
• Policy decision
60

Not Arbitrary: Goodbye rule of 3!
Title: Antigo Testamento Poliglota : Hebraico, Grego,
Português, Inglês.
In AACR2 if something contains expressions in more
than 3 languages you have one access point with
language “polyglot”
Bible. O.T. Polyglot
In RDA you can give access point to all of the
expressions:
Bible. Old Testament. Hebrew
Bible. Old Testament. Greek
Bible. Old Testament. Portuguese
Bible. Old Testament. English
61

DATA ELEMENTS IN RDA & THE
EXTENSIBLE FRAMEWORK
Including elements
62

Data Elements
element = A word, character, or group of words
and/or characters representing a distinct
unit of bibliographic information.
appears similar to AACR2 definition, minus the
reference to “areas”
actually quite different from AACR2
elements are in line with metadata conventions
elements, element sub-types, sub-elements
63

Data Elements
each element is discrete and precisely defined
64

Data Elements
data is not embedded in long character strings
65

Elements in AACR2
66
• data embedded in areas or paragraphs
• different kinds of data embedded together
in long character strings
• assumption is that a human will read and
interpret information in record
• cannot be used reliably to search or to limit a
search
• cannot be used for automated processing
• cannot be used to generate a meaningful
display

RDA data elements
• RDA element contains data either about:
a single attribute of an entity
OR a single relationship between entities
• each element is discrete and precisely defined
• independent, separate units of data
• increased use of controlled vocabulary
67

Data elements: dates
• only one kind of data in an element
AACR2: date of publication, distribution, etc.
MARC 21: 260 $c
RDA: 4 different elements:
date of production
date of publication
date of distribution
date of copyright
day 1 implementation in MARC 21 environment – data will still be
ambiguous 68

Data elements: dissertations
AACR2: 1.7B13. Dissertations
information embedded in a note about academic degree,
granting institution or faculty and year degree granted
RDA: 7.9.1 Recording Dissertation or Thesis
Information
• separate elements for
academic degree
granting institution or faculty
year degree granted
day 1 implementation in MARC 21 environment – subfields for
502 already implemented
69

Elements in AACR2
AACR2: information embedded in “other physical
details” (or a non-specific note)
illustrative content
encoding format
other physical production method
details sound content
applied material
MARC 300 $b base material
reduction ratio
70

RDA data elements
• separated according to whether it is data about
content or carrier
illustrative content encoding format
sound content production method
applied material
base material …
• controlled vocabulary recommended for many elements
aspect ratio: full screen, wide screen, mixed
base material: Bristol board, canvas, cardboard, ceramic,
glass, leather, paper, parchment, vellum … 71

Extensible Framework
many data elements – each precisely defined
data elements can be used in any combination
clear distinction between content and carrier
work content
expression content
manifestation carrier
item carrier
framework to describe all known resources
framework that can be extended to describe
resources yet to be developed 72
Source: Oliver (Oct. 2010: slide 63-64)

Extensible Framework
 room for growth with framework of attributes
and relationships
RDA framework can describe
any content any carrier
in addition, framework for categorizing
resources
73

Categorization of Content & Carrier
RDA/ONIX framework
 support needs of libraries and publishing industry
 help user to select appropriate resource
What is the categorization framework?
 replaces the general material designation (GMD), e.g.
[electronic resource]
 consists of 3 elements that can be used in multiple
combinations
 each element has controlled vocabulary
74

consists of three elements:
content type
media type
carrier type
• can use as many of each type as needed
• not a display standard -- consistent values in the
elements that can be mapped in various ways
map to icons
map to terms preferred by the user group
map to terms in different languages
map to newly developed terms
75
Modified from: Oliver (Oct. 2010: slide 67, 71)

content type expression notated music
performed music
still image
spoken word
text
media type manifestation audio
microform
unmediated
carrier type manifestation audio cartridge
audio disc
audiocassette
76

e-books vs. print books
E-book:
content type: text
media type: computer
carrier type: online
resource
Print book:
content type: text
media type: unmediated
carrier type: volume
audio book vs. audio book online
Audio book:
content type: spoken word
media type: audio
carrier type: audio disc
Online Audio book:
content type: spoken word
media type: computer
carrier type: online resource
77

web page
Content type = text
Content type = still image
Content type = performed music
Media type = computer
Carrier type = online resource
online video
Content type = two dimensional moving image
Media type = computer
Carrier type = online resource
78

New MARC fields
336 ## $a performed music $2 rdacontent
337 ## $a audio $2 rdamedia
338 ## $a audiodisc $2 rdacarrier
79

Core Elements
300+ elements but you don’t have to use them all
core elements
• not a level of description
• core elements are a minimum “a floor, not a ceiling”
• must include any additional elements required to
differentiate the resource or entity from a similar one
• may include additional elements – as required to
complete user tasks
80

Core Elements
• core elements support the key user tasks
• identify and select a manifestation
• identify works and expressions embodied in a
manifestation
• identify the creator or creators of a work
• find a person, family, or corporate body associated
with a resource
• identify a person, family, or corporate body
• certain elements are flagged as “core”
• certain elements are flagged as “core if”
81
Modified from: Oliver (Feb. 2011: slide 58-59)

So, what is RDA?
RDA = a set of practical instructions
based on a theoretical framework
• Broad scope
• Theoretical framework based on the FRBR and FRAD
conceptual models
• Guided by objectives and principles
• Data elements: an aspect of RDA’s design
• Flexible and extensible framework
82

RDA - standard for now and the future
• day 1 of implementation:
“shoe-horn” RDA into
MARC 21
• RDA: not simply RDA in
MARC 21
• day 1 of implementation
allows us to begin
travelling along the new
track
• Keep an eye on the LC
Bibliographic Framework
Transition Initiative 83

Navigating beyond the library
Author
• out to biographical information (e.g. in Virtual
International Authority File (VIAF) or Wikipedia or a
dynamic mash-up)
• out to resources by the author available in other places
(websites, blogs, articles, etc.)
Work
• out to descriptive information about the content of the
work (e.g. in Wikipedia, in a national bibliography,
publisher’s catalogue, etc.)
• out to resources that are based on the work (e.g.
adaptations, movies, plays etc.)
84

85
Image from: WorldCat. Copyright OCLC. WorldCat
Identities is a project of OCLC Research

IMPLEMENTATION AND TRAINING 86

Implementation in North
America
• Library of Congress
• Information available on their RDA site
http://www.loc.gov/aba/rda/
• Target date for implementation is March 31, 2013
• Revising LCRIs and making decisions on options
• These will appear in the RDA Toolkit as LC Policy Statements
(LCPS)
• Monitoring status of U.S. RDA Test Coordinating Committee
recommendations
• Created training plan
87

Implementation in North
America
• Library and Archives Canada
• See their RDA FAQs
http://www.collectionscanada.gc.ca/cataloguing-
standards/040006-1107-e.html
• Target date between January 2 and March 31, 2013
• Coordinating with LC, British Library, National Library of
Australia
• Trying to align LAC policies with other national libraries
• In YOUR library
• Decide if you need any local policies or if you will follow
LC/LAC
• Communicate with your public services staff (e.g. how you are
handling the elimination of the Rule of 3)
• Communicate with systems staff (e.g. can your system handle
the new MARC fields) 88

Prepare yourself for training
• Familiarize yourself with FRBR terminology and RDA
• There are a lot of presentations available on the RDA in
Canada Wiki
(http://rdaincanada.wikispaces.com/presentations)
• If you have access, familiarize yourself with the RDA
Toolkit. Try cataloguing something using RDA!
• If you don’t have access yet, view the a Toolkit webinar
(http://www.rdatoolkit.org/webinar/2011Feb)
• Watch for the training modules being developed by the
Pan-Canadian Working Group on Cataloguing with RDA
• Watch for workshops & webinars from EI Institute,
ALCTS, sessions at OLA
89

Look at sample RDA records
• Look at RDA records on LC website: http://catalog.loc.gov
90

If you are the trainer…
• Don’t reinvent the wheel! Go online for training materials
• Start with the background: RDA principles, FRBR concepts
and terminology
• Highlight changes from AACR2 to RDA for common
cataloguing tasks
• Identify changes in the structure of the tool so that cataloguers
can navigate the RDA Toolkit
• Give practical examples and exercises
• Allow time for follow-up sessions 91

Questions?
Alison Hitchens
Cataloguing & Metadata Librarian
University of Waterloo Library
ahitchen@uwaterloo.ca
To subscribe to the new cataloguing list from OLA
(rda@accessola.com)
Send an e-mail request to Claire at OLA
cward@accessola.com
92

Flickr credits: creative commons attribution
Spongey balls by Seldom Scene Photography (was Old Dog Photo)
http://www.flickr.com/photos/old_dog_photo/3876259713/
Pastel ribbons by Sakurako Kitsa
http://www.flickr.com/photos/kitsa_sakurako/414007954/
Cross track – iPhone wall paper by CJ Schmit
http://www.flickr.com/photos/cjschmit/4623783487/
93

References & Resources
Association for Library Collections & Technical Services. "Online
Learning." Access at: http://www.ala.org/alcts/confevents
Education Institute. "EI Education Institute." Access at:
http://www.thepartnership.ca/partnership/bins/index_ei.asp
Grover, Trina. “Cataloguing on the edge: emerging standards for
bibliographic data,” PowerPoint prepared for Atlantic Provinces
Library Association, May 17, 2011. Access at
http://rdaincanada.wikispaces.com/file/view/apla2011b.ppt
IFLA Meeting of Experts on an International Cataloguing Code,
“Statement of International Cataloguing Principles,” (2009).
Access at: http://www.ifla.org/files/cataloguing/icp/icp_2009-
en.pdf
94

Resources and References
IFLA Working Group on Functional Requirements and Numbering of
Authority Records, Functional Requirements for Authority Data: a
Conceptual Model. IFLA Series on Bibliographic Control 34
(Munchen: Saur, 2009)
IFLA Study Group on the Functional Requirements for Bibliographic
Records, Functional Requirements for Bibliographic Records: Final
Report. UBCIM Publications, New series vol. 19 (Munchen: Saur,
1998). Access at: http://www.ifla.org/files/cataloguing/frbr/frbr.pdf
Joint Steering Committee for Development of RDA. "International
Conference on the Principles & Future Development of AACR."
Access at: http://www.rda-jsc.org/intlconf1.html
Joint Steering Committee for Development of RDA. "RDA: Resource
Description and Access." Access at: http://www.rda-jsc.org/rda.html
95

Resources and References
Library and Archives Canada. "RDA: Resource Description and Access
Frequently Asked Questions." Updated January 2012. Access at
http://www.collectionscanada.gc.ca/cataloguing-standards/040006-1107-e.html
Library of Congress. Bibliographic Framework Transition Initiative. "Bibliographic
Framework Transition Initiative." Last updated March 29, 2012. Access at:
http://www.loc.gov/marc/transition/
Library of Congress. Cataloguing and Acquisitions. "Resource Description and
Access (RDA): Information and Resources in Preparation for RDA." Updated
April 9, 2012. Access at: http://www.loc.gov/aba/rda/
Library of Congress. “Module 4: Persons, Families and Corporate Bodies:
Elements and authorized access points.” PowerPoint module prepared for the
Georgia Public Library Service Cataloging Summit, August 9-10, 2011. Access at
http://www.loc.gov/aba/rda/source/Georgia_module_4_17august2011.ppt
McCallum, Sally. “RDA in MARC: September 2011.” Access at
http://www.loc.gov/marc/RDAinMARC29-9-12-11.html
96

References and Resources
Oliver, Chris. Introducing RDA: A guide to the basics. Chicago: American Library
Association, 2010.
Oliver, Chris. “Module 8: cataloguing with RDA: recording relationships,”
PowerPoint module prepared for OLA Superconference, February 1, 2012.
Oliver, Chris. “RDA: a quick introduction,” PowerPoint prepared for OLA
Superconference, February 2, 2011. Access at
http://rdaincanada.wikispaces.com/file/view/ola_rda_oliver_2011feb.pptx
Oliver, Chris. “RDA: the framework: structure, principles, concepts,” PowerPoint
prepared for CASLIS RDA Workshop, October, 2010. Access at
http://tsig.wikispaces.com/file/view/Framework+for+workshop.ppsx
Oliver, Chris. “What is RDA and why do I need to know?” PowerPoint prepared for
CLA Montreal Chapter, March 9th, 2011. Access at
http://rdaincanada.wikispaces.com/file/view/What+is+RDA+March+9+2011+final
.pptx
97

References and Resources
Ontario Library Association. "Superconference 2013, January 30-
February 2." Access at:
http://www.accessola.org/ola_prod/OLAWEB/Super_Conference/Welco
me/OLAWEB/Super_Conference/Welcome.aspx
Pan-Canadian Working Group on Cataloguing with RDA. "Training."
Access at: http://rdaincanada.wikispaces.com/training
"RDA Canadian Knowledge Exchange." Access at
http://rdaincanada.wikispaces.com
RDA-L. To subscribe: LISTSERV@LISTSERV.LAC-BAC.GC.CA. See
the list of archives at http://www.mail-archive.com/rda-l@listserv.lac-
bac.gc.ca/
"RDA Toolkit." Access at: http://www.rdatoolkit.org/
98

RDA 101: an introduction to RDA (2012)

Recommended

Recommended

More Related Content

Similar to RDA 101: an introduction to RDA (2012)

Similar to RDA 101: an introduction to RDA (2012) (20)

More from Alison Hitchens

More from Alison Hitchens (15)

Recently uploaded

Recently uploaded (20)

RDA 101: an introduction to RDA (2012)