Introducing RDA
-
Upload
alatechsource -
Category
Documents
-
view
7.522 -
download
5
description
Transcript of Introducing RDA
What is RDA?
RDA = Resource Description and Access
• new metadata standard replaces AACR2
• set of practical instructions built on the foundation of a theoretical framework/data model
• record better metadata to support better resource discovery
• designed for the web environment
2
Plan
1. moving towards RDA and its implementation
2. key concepts in RDA
• theoretical framework
• objectives and principles
• focus on the user
• content standard
• bibliographic information as data
• internationalization
and their visible impact on RDA
3
1. Moving towards RDA
4
AACR2 successful standard adopted by many countries in use for many years
but
problems with AACR2
for example:• written for card catalogues• inadequate rules to describe new types of
resources• inconsistencies• library specific
5
Roots of RDA
1997 problems identified:
International Conference on the Principles & Future Development of AACR, Toronto,
Ontario
1998-2004 revisions to AACR2; revise within the existing structure
2004 AACR3
2005 decision to develop a new standard: Resource Description and Access
2005-2009 development of content for the new standard
6
Moving towards RDA2009 text of RDA completed
software designed ... but
>>> still a set of static documents that need to be transformed into a web tool
2010 first release of the RDA Toolkit (RDA plus)
2010 US testing (US RDA Test Coordinating Committee)
2011 US national libraries and the Program for Cooperative Cataloging: intention to implement if certain conditions are met
implementation not before 2013
7
Moving towards RDA
2011 some of the libraries who tested RDA decide to continue producing RDA records
2011-2012 preparations for implementation
- work on recommendations
- community involvement
2012 announcement from the Library of Congress: target date for implementation: March 31, 2013
Long-Range RDA Training Plan
http://www.loc.gov/aba/rda/pdf/RDA_Long-Range_Training_Plan.pdf
8
Moving towards RDA
2012 other national libraries are also planning to target the 1st quarter of 2013 as their RDA implementation date:
National Agricultural Library
National Library of Medicine
British Library
Library and Archives Canada
National Library of Australia
Deutsche Nationalbibliothek (mid 2013)
9
Is there a day 1?
Yes and No1) day 1 is important for a sharing data environment:
PCC: declares day 1 for contributing to NACO authorities
LC: declares day 1 for its own cataloguing operations
2) some institutions never switched back after the test
3) each institution decides on day 1 for bibliographic data
10
March 31, 2013• all new authority records contributed to LC/NACO
authority file = RDA
• all records coded pcc = all RDA access points
all records coded pcc whether:• RDA description
or• AACR2 description
• LC will have completed training all its cataloging staff
and all LC records will be RDA records
11
by March 31, 2013• rapid rise in number of RDA bibliographic records
• changes in LC/NACO authority file • distinction between RDA acceptable and not acceptable
• global changes in individual databases
implications for authority work
implications for copy cataloging
12
Implementation arriving quickly ...
13
Phase 1 of implementation
emphasis on continuity
● RDA data in MARC 21
● in current catalogues
● still creating bibliographic and authority records
● some new fields
● some changed instructions
● some new instructions
BUT
>>> thinking about bibliographic information differently
14
Phase 1 = starting down new track
RDA• continuity and change
• moves us to a new track
• starts us on a promising track for the future use of our metadata
• useful to understand some of the key RDA concepts and see the long view
15
2. Key concepts in RDA
16
AACR2 RDA• continue to record the title
• continue to record the statement of responsibility
• continue to record the date of publication
But …
• new vocabulary
• new way of thinking about how we do these steps
17
Similar, but ...
AACR2
1.2B1. Transcribe the edition statement as found on the item. Use abbreviations as instructed in appendix B and numerals as instructed in appendix C.
RDA
2.5.1.4. Transcribe an edition statement as it appears on the source of information.
No instruction to abbreviate or to convert to arabic numerals.
18
Similar, but ...• serious adherence to the principle of representation
“take what you see”
t.p. data recorded
3rd ed. 3rd ed.
Second edition Second edition
19
On the surface …
similar instructions
but different framework
new vocabulary
but also new concepts
20
2. Key concepts in RDA
Theoretical framework
21
RDA’s theoretical framework• explicit conceptual framework
• aligned with the FRBR and FRAD conceptual models
FRBR Functional Requirements for Bibliographic Records
1998
FRAD Functional Requirements for Authority Data
2009
FRAD is an extension of the FRBR model
• both models developed under the auspices of IFLA• broad base of international consensus and support
22
The two models• widely used data modeling technique:
entity relationship model• entities• attributes• relationships
• analyze bibliographic and authority data from the point of view of how that data is used
23
RDA vocabulary from FRBR + FRAD
• user tasks
• meaning and scope of the 11 bibliographic entities
work person concept
expression family object
manifestationcorporate body event
item place
• entities – attributes – relationships
24
Organization and Structure of RDA
RDA table of contents reflects alignment with FRBR
Section 1-4 = Recording attributes
Section 1. Recording attributes of manifestation and item
Section 2. Recording attributes of work and expression
Section 3. Recording attributes of person, family, and corporate body
Section 4. Recording attributes of concept, object, event, and place [placeholder]
25
Organization and Structure of RDASections 5-10 = Recording Relationships
Section 5. Recording primary relationships between work, expression, manifestation, and item
Section 6. Recording relationships to persons, families, and corporate bodies associated with a resource
Section 7. Recording subject relationships [placeholder]
Section 8. Recording relationships between works, expressions, manifestations, and items
Section 9. Recording relationships between persons, families, and corporate bodies
Section 10. Recording relationships between concepts, objects, events, and places
[placeholder]
26
User tasks from FRBR + FRAD
Bibliographic data
• find• identify• select• obtain
Authority data
• find• identify• contextualize (clarify)• justify (understand)
27
Attributes• how to record the attributes of entities (characteristics)
for example, entity = a manifestation
attributes we record: title proper
statement of responsibility
edition statement
place of publication
etc.
28
Relationships: links between entities
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
29
Relationships in RDA1. record relationship
2. specify exact nature of the relationship
for example
AACR2 name of a person ------- title of book
• type of relationship may be embedded in text of description• bibliographic record contains name of person and title
RDA name of a person --- type of relationship --- work
• make the relationship explicit and clear• relationship designators = controlled vocabulary
30
Relationship designators• specify roles
for example cartographer
performer
broadcaster
former owner
issuing body
• specify the nature of the relationship
for example adaptation of
paraphrased as
electronic reproduction of
31
Relationships in RDA
examples with MARC 21 coding:
245 10 $a British Atlantic, American frontier : $b spaces of power in early modern British America / $c Stephen J. Hornsby ; with cartography by Michael J. Hermann.
700 1# $a Herman, Michael J., $e cartographer
245 00 $a Alice in Wonderland, or, What's a nice kid like you doing in a place like this? /$c Hanna-Barbera Productions.
700 1# $i parody of (work) $a Carroll, Lewis, $d 1832-1898. $t Alice's adventures in Wonderland.
authority record
500 3# $w r $i Descendant family: $a Adams (Family)
32
Theoretical framework• alignment with the FRBR and FRAD conceptual models
• bibliographic and authority data
>>> in terms of entities, attributes + relationships
• identify what is important --- how is data used
• systematic and coherent framework
>>> conceptual clarity
>>> logical consistency
>>> reference point for further development
33
Underlying data model
>>> practical set of cataloguing instructions
● built on a theoretical framework
● built on a robust data model
• widely used data modeling technique
• understood by other metadata and data modeling communities
e.g. software engineers, information systems and database designers
34
2. Key concepts in RDA
Objectives and principles
35
RDA Objectives & Principles• important part of RDA
• shaped many of the instructions that are different from AACR2
• concur with the International Cataloguing Principles (ICP)
36
RDA Objectives & Principles
Objectives RDA 0.4.2
• responsiveness to user needs
• cost efficiency
• flexibility
• continuity
Principles RDA 0.4.3
• differentiation
• sufficiency
• relationships
• representation
• accuracy
• attribution
• common usage or practice
• uniformity
37
Principle of representation
for example RDA 0.4.3.4
principle = representation
The data describing a resource should reflect
the resource’s representation of itself.
result = simplify transcription
“Take what you see”
38
RDA = Take what you see
source= Kemptville, Ontario
AACR2 = Kemptville, Ont.
RDA = Kemptville, Ontario
264 1 $a Kemptville, Ontario ____________________________________________________________________________________________________________________
source = Band LXXXVIII (series numbering)
AACR2 = Bd. 88
RDA = Band LXXXVIII
490 $a ... ; $v Band LXXXVIII
39
RDA = Take what you see
source = Third revised edition
AACR2 = 3rd rev. ed.
RDA = Third revised edition
_____________________________________________
source = 2nd enlarged ed., revised
AACR2 = 2nd enl. ed., rev.
RDA = 2nd enlarged ed., revised
40
Different instructions
AACR2 1.0F. Inaccuracies
In an area where transcription from the item is required, transcribe an inaccuracy or a misspelled word as it appears in the item. Follow such an inaccuracy either by [sic] or by i.e. and the correction within square brackets. Supply a missing letter or letters in square brackets.
RDA 1.7.9 Inaccuracies
When instructed to transcribe an element as it appears on the source of information, transcribe an inaccuracy or a misspelled word as it appears on the source, except where instructed otherwise.
41
Inaccuracy in RDA 1.7.9 continued
Make a note correcting the inaccuracy if it is considered to be important for identification or access (see 2.20 ).
If the inaccuracy appears in a title, record a corrected form of the title as a variant title (see 2.3.6 ) if it is considered to be important for identification or access.
Exception:
2.3.1.4 Inaccuracies. When transcribing the title proper of a serial or integrating resource, correct obvious typographic errors, and make a note giving the title as it appears on the source of information (see 2.20.2.4 ) ...
42
RDA = Take what you see
title page = Melallization of polymers
AACR2 = Melallization [sic] of polymers
or Melallization [i.e. Metallization] of polymers
RDA = Melallization of polymers
245 14 $a Melallization of polymers 246 1 $i Corrected title: $a Metallization
of polymers
43
2. Key concepts in RDA
Focus on the user
44
RDA Objectives & Principles
Objectives RDA 0.4.2
• responsiveness to user needs
• cost efficiency
• flexibility
• continuity
Principles RDA 0.4.3
• differentiation
• sufficiency
• relationships
• representation
• accuracy
• attribution
• common usage or practice
• uniformity
45
Focus on the user• record data that is important to the user
why is it important?
helps the user to find
identify
select
obtain
46
Resource discovery = user tasks
Bibliographic data
• find• identify• select• obtain
Why record the data?
Authority data
• find• identify• clarify• understand
To help user achieve these tasks.
47
Consistent focus on the user • RDA divided into 10 sections
• each section begins with general guidelines
• functional objectives and principles specific to the section
Functional objectives = relationship between data and user tasks
the data (recorded or formulated according to the instructions in that section)
the user tasks
48
Example from Section 1Section 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 stored on the carrier
d) obtain a resource …
49
Basis for Cataloguer Judgment• instructions encourage cataloguer judgment --- based on
relationship to user tasks
for example, from 3.7 Applied material
Record the applied material used in the resource if it is considered important for identification or selection …
50
Easier for user to identify• no abbreviations
300 $a 398 pages :$b illustrations ; $c 25 cmAACR2: 300 $a 398 p. :$b ill. ; $c 25 cm.
• no square brackets 300 $a 48 unnumbered pages, 256 pages
AACR2: 300 $a [48], 256 p.
• replace Latin abbreviations 300 $a 48, that is, 96 pages
AACR2: 300 $a 48 [i.e. 96] p.
• avoid cryptic information 300 $a xiv, 179 pages (incomplete)
AACR2: 300 $a xiv, 179 + p.
51
Easier for user to find, identify
RDA: no more: rule of three
no more … [et al.] in description
if statement of responsibility names more than one person >>> record all RDA
2.4.1.5
optional omission: record first named and summarize the omission
[and six others]
access points for first named or principal core
or all
or cataloger judgment
or institutional policy
52
Easier for user to find, identifyRDA: record all authors; access points for all authors;
define relationships with designators
100 1 $a Berry, John W., $e author.
245 10 $a Cross-cultural psychology : $b research and applications / $c John W. Berry, Ype H. Poortinga, Seger M. Breugelmans, Athanasios Chasiotis, David L. Sam.
250 $a Third edition.
260 $a Cambridge : $b Cambridge University Press, $c 2011.
300 $a xxii, 626 pages ; $c 25 cm
700 1 $a Poortinga, Ype H., $d 1939- $e author.
700 1 $a Breugelmans, Seger M., $e author.
700 1 $a Chasiotis, Athanasios, $e author.
700 1 $a Sam, David L., $e author.
53
Easier for user to understand
RDAoptional omission (2.4.1.5):
more than three, omit and summarize
core relationship = access point for first-named
100 1 $a Berry, John W.
245 10 $a Cross-cultural psychology : $b research and applications / $c John W. Berry [and four others].
250 $a Third edition.
260 $a Cambridge : $b Cambridge University Press, $c 2011.
300 $a xxii, 626 pages ; $c 25 cm
54
Easier for user to find
AACR2 Aesop’s fables. Polyglot.
RDA Aesop’s fables. Greek
Aesop’s fables. Latin
Aesop’s fables. English
Aesop’s fables. German
AACR2 Aesop’s fables. English & German
RDA Aesop’s fables. English
Aesop’s fables. German
55
2. Key concepts in RDA
Content standard
56
RDA as a content standard
AACR2: MARC encoding + ISBD display
RDA = what data should the cataloguer record?
• possible to encode using many encoding systems• can be encoded using MARC
• does not have to be encoded using MARC encoding
• can be used with web friendly XML based encoding schema, such as Dublin Core, MODS
• possible to display the data in many ways
57
RDA as a content standard
not an encoding standard
not a display standard
• for example, take the data and create displays that suit your user group:
RDA says: record person’s date of death = 2003
Display? died 2003
d. 2003
- 2003
date of death: 2003
58
Possible displayIssuing body: Whitney Museum of American Art
710 2# $a Whitney Museum of American Art, $e issuing body.
Photographer: Burger, Hillel
700 1# $a Burger, Hillel, $e photographer.
Author: Gaines, Isabel
100 1# $a Gaines, Isabel, $e author.
Alice in Wonderland, or, What's a nice kid like you doing in a place like this? / Hanna-Barbera Productions.
Parody of: Carroll, Lewis, 1832-1898. Alice's adventures in Wonderland.
700 1# $i parody of (work) $a Carroll, Lewis, $d 1832-1898. $t Alice's adventures in Wonderland
59
Identifying the entity
either
eye-readable data: name
date of birth and death
Shields, Carol, 1953-2003
and/or
machine actionable data: identifier
0101A6635
http://viaf.org/viaf/4944537/#Shields,_Carol
60
RDA as a content standard• not locked into library encoding practices
• not locked into library display practices
• get out of the library silo
>>> data visible on the web
>>> data interacting with the data of other metadata
communities
61
2. Key concepts in RDA
Bibliographic information as data
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 “forming part of an area”
effect is quite different from AACR2
each element is ≈ discrete
≈ precisely defined
≈ single attribute / single relationship
63
AACR2for example
AACR2: information embedded in non-specific places
notes digital file characteristicsphysical description file typeMARC 538 encoding format
516 file size500 resolution300 regional encoding
transmission speed
64
RDARDA: precise elements and element sub-types
digital file characteristics RDA 3.19
file type
encoding format
file size
resolution
regional encoding
transmission speed
65
347 Digital File Characteristics
new MARC field 347
subfield codes
$a - File type (R)
$b - Encoding format (R)
$c - File size (R)
$d - Resolution (R)
$e - Regional encoding (R)
$f - Transmission speed (R)
66
AACR2 InformationAACR2: ambiguity --- assume human will decipher
AACR2: date of publication, distribution, etc.date of copyrightdate of manufacture
MARC 21: 260 $c260 $g
67
RDA Data ElementsRDA: precise elements – only one kind of data in an
element
RDA: 5 different elements: RDA 2.7-2.11date of productiondate of publicationdate of distributiondate of manufacturedate of copyright
MARC 21: 264 $c 5 different indicators
68
Controlled vocabulary• controlled vocabulary recommended for many elements
encoding format DAISY, MP3, Access, XML, JPEG, TIFF, CAD, PDF, Blu-ray, VCD
production method blueline, blueprint, engraving, etching, lithograph,
photocopy, photoengraving, woodcut
base material Bristol board, canvas, cardboard, ceramic, glass, leather, paper, parchment, vellum
69
RDA data = precise + usable data
RDA• each element is distinct and precisely defined• each element contains only one kind of data• controlled vocabulary in many elements
each element has the potential to be usable:
to indexto search
to build meaningful displays of data
data in any element can be used: by humans
by computers
70
Many new elements
many new elements but do not 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
• inclusion of other elements --- cataloguer judgment
71
2. Key concepts in RDA
Internationalization
72
Beyond “Anglo-American”
RDA 0.11.1:
RDA is designed for use in an international context.
options for use of • other languages
• other scripts
• other calendars
• other numeric systems
• other units of measurement
73
RDA • when not transcribing:
some instructions say –
... record in the language preferred by the agency creating the data
... record in the preferred script of the agency creating the data
6.4.1.3 Recording Date of Work
Record the date of the work in terms of the calendar preferred by the agency creating the data.
74
RDA April 2012 update• change at 6.2.1.7 for the international cataloguing
community (proposed by the German National Library and approved by all constituencies)
Basic instructions on recording titles of works
RDA 6.2.1.7 Initial articles
When recording the title, include an initial article, if present.
Alternative
Omit an initial article …
original text at RDA 6.2.1.7 was: Omit an initial article …
75
FRBR + FRAD as point of reference
broad international support for the explanatory power of the models
common international language and conceptual understanding of the bibliographic universe
as the foundation for a standard:
• easier to apply in international context
• easier for our data to interoperate with other data generated on the basis of a FRBR/FRAD understanding of the bibliographic universe
76
On the international scene
2005-2009 comments on RDA drafts:
from libraries beyond Australia, Canada, Great Britain and the United States
2011 formal launch of European RDA Interest (began in 2009) Group (EURIG)
members from: Austria, Croatia, Denmark, Finland, France, Germany, Great Britain, Italy, Latvia, Netherlands, Norway, Poland, Portugal, Slovakia, Slovenia, Spain, Sweden, the Vatican
>>> interest of countries who use AACR2
>>> interest of countries that have never used AACR
77
On the international scene
Translation projects:
German Germany, Austria
French Canada, France, Belgium
Spanish licensing for: Argentina, Bolivia, Chile, Colombia, Costa Rica, Dominican Republic, Ecuador, El Salvador, Equatorial Guinea, Guatemala, Honduras, Mexico, Nicaragua, Panama, Paraguay, Peru, Spain, Uruguay, Venezuela
Chinese (Mandarin)
and expressions of interest from others
78
Key concepts
Key concepts shape RDA:
• theoretical framework
• objectives and principles
• focus on the user
• content standard
• bibliographic information as data
• internationalization
>>> visible impact on RDA and the content of instructions
>>> many changes in RDA trace back to concepts
79
Familiarity with key RDA concepts• a useful way to grab hold of RDA
• a useful way to approach RDA implementation
80
Flickr credits: creative commons attribution
Tour de Toona by Team Traveller
http://www.flickr.com/photos/teamtraveller/5928422950/
Cross track – iPhone wall paper by CJ Schmit
http://www.flickr.com/photos/cjschmit/4623783487/
The roof continues by Martin Pettitthttp://www.flickr.com/photos/mdpettitt/2521374167/
Oregon silo by TooFarNorth
http://www.flickr.com/photos/toofarnorth/4597980984/
Rock climbing is fun by mariachilyhttp://www.flickr.com/photos/mariachily/3382799213/
81