Chris Oliver
May 4th, 2009
for MLA
RDA and AACR2
Outline
RDA: relationship to AACR2
continuity with AACR2
differences from AACR2
examples to illustrate comparisons
Challenges of online environment
changing cataloguing environment new types of resourceswork in an online, networked environment
Problems with AACR2
written in the context of card catalogues e.g. space-saving limitations (rule of 3,
abbreviations)
inadequate rules for the description of new types of resources
lack of theoretical framework to act as reference point when dealing with new situations
Problems identifiedConference in 1997:
International Conference on the Principles & Future Development of AACR, Toronto
Experts identified key issues: PrinciplesContent vs. carrierLogical structure of AACR2Seriality Internationalization
International developmentsFRBR + FRAD
IME-ICC and the groundwork for revised internationally accepted cataloguing principles (2003-2009)
strong foundation of international consensus
Revisions are not enough
revisions only give partial solutionse.g. revision of rule 0.24 e.g. new chapter 12
issues not resolvede.g. logical inconsistency
remains difficult to adapt rules for new media and publication types
AACR2 AACR3 in 2004, plans for a new edition:
AACR3: resource description and access
change the structure of Part 1add theoretical frameworkmaintain content of AACR2 rules
AACR3 RDAin 2005: go further!
RDA replaces AACR2
RDA is different from AACR2new standard
designed for the online environment
built on a theoretical framework
developed in dialogue with other metadata communities
flexible for use beyond the traditional library application
intended for world-wide use
RDA replaces AACR2RDA replaces AACR2
last amendments to AACR2 released in 2005
RDA compatible with AACR2 data
From the Strategic Plan for RDA:
“Be compatible with those descriptions and access points devised using AACR2, and present in existing catalogues and databases”
RDA replaces AACR2
RDA builds on the foundation of AACR2
RDA Statement of purpose:
“Built on foundations established by the Anglo-American Cataloguing Rules (AACR), RDA will provide a comprehensive set of guidelines and instructions on resource description and access covering all types of content and media”
RDA builds on AACR2
RDA builds on the strengths of AACR2
AACR2 is used around the world
translated into 24 languages
constantly evolving
based on common usage, common citation practices and real publication practices
enables the sharing of records
RDA goes beyond AACR2
aligned with the FRBR and FRAD conceptual models:
FRBRFunctional Requirementsfor Bibliographic Records
FRAD Functional Requirements for Authority Data
AACR2 RDA RDA new logical organization
alignment with FRBR/FRAD conceptual models
AACR2 deconstructed
+
some changes
+
new vocabulary
+
new organization
Reconstruction into RDA
every word has changed
many instructions show visible continuity with AACR2
Changes from AACR2strong theoretical basis
new way of thinking about cataloguing and new structure to support it
“designed for the digital world” take advantage of new database structures better description of digital resources support for use in the semantic web re-use metadata to be used as a web tool
Changes from AACR2new extensible framework for the description of all types of content and media
support for better navigation and better data display
not just for libraries
world-wide use
FRBR + FRAD in RDA
structure of RDA
user tasks
FRBR and FRAD vocabulary and concepts
explicit explanation of the relation between the instructions and the user tasks (functional objectives)
emphasis on relationships and on clarifying the nature of the relationships
FRBR perspective: bibliographic record in the context of a large catalogue or database
RDA StructureIntroduction
10 sections:Sections 1-4 = Recording attributes
Sections 5-10 = Recording relationships
Appendicescapitalization, abbreviations, initial articles, data
presentation, relationship designators, examples
Glossary
RDA vs AACR2Organization of the guidelines
RDA AACR2
Recording attributes Description Recording relationships Headings, uniform
titles and references
FRBR/FRAD entities class of materialtypes of headings
data for authority control references
1 chapter = 1 user task user is in the shadows
FRBR relationshipsrelationships within the family of one work:
work-expression-manifestation-item
relationships between works, between expressions, between manifestations, between items
relationships between a person (or corporate body or family) and a work, or expression, or manifestation, or item
relationships between persons, corporate bodies and families
subject relationships
relationships between subjects
Relationships in RDAaccess points no limit to the number of access points
controlled vocabulary for relationship designators Appendices I, J, K and L
e.g. transformation
Hamlet by William Shakespeare
Hamlet : opéra en cinq actes musique de Ambroise Thomas; paroles de Michel Carré et Jules Barbier
Relationship designators
J.2 Relationship designators for related works
based on (work) libretto based on (work)
A work used as the basis for the text of an opera or other work for the musical stage
derivative workbasis for libretto (work)
A work that comprises the text of an opera or other work for the musical stage based on the source work
Relationship designators
I.2 Relationship designators for works
I.2.1 Relationship designators for creators
work level author
work level librettist1.3 Relationship designators for expressions
expression level narrator
expression level translator
(added to preferred access point for the creator)
Access point for expression6.27.3 Preferred Access Point Representing an
Expression
Add to the preferred access point for the work, as applicable:
a) a term indicating content type
b) the date of the expression
c) language of the expression
d) a term indicating another distinguishing characteristic of the expression
Shakespeare, William, 1564-1616. Hamlet. Spoken word
“Designed for the digital world”
work with existing catalogues and database structures
take advantage of newly emerging database structures
re-use of metadata
metadata for the semantic web
describe and give access to all types of resources, analog, digital, etc.
RDA vs AACR2RDA: “to take advantage of the digital environment” stop fussing about abbreviations more “take as is” – principle of representation transcribe inaccuracies; add note if necessary enable re-use of metadata
AACR2: rules from the card catalogue erawhen to abbreviate, when not to abbreviate“transcription” but also required to omit and
sometimes to supply datause of [sic] or correction of inaccuracies
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.
Appendix B Abbreviations
B.4. Transcribed Elements
For transcribed elements, use only those abbreviations found in the sources of information for the element.
AACR2
1.1F7. [4 conditions when you do record titles of nobility, address, etc.]
… Otherwise, omit all such data from statements of responsibility.
RDA
2.4.1.4. 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.
no instructions to omit data in 1.7
2.4.1.4 Optional Omission
Abridge a statement of responsibility only if it can be abridged without loss of essential information.
RDAnew standard, new format1st release will be as an online tool
written as an online tool
online tool also delivers additional functionality
e.g., includes mapping between AACR2 rules and RDA guidelines
easier to use, easier to teach
individual or collaborative use
efficiency and customization
New RDA vocabularyheading access point
area element
uniform title preferred title
name of the work
see reference variant access point
main entry preferred access point
physical describing carriersdescription
choosing recording relationships added entries
Reconstruction into RDA
every word has changed
many instructions show visible continuity with AACR2
AACR221 Choice of Access Points
21.30J2 Variant title. If considered necessary for access, make an added entry for any version of the title (e.g., cover title …) that is significantly different from the title proper.
RDA2.3 Title
2.3.6.3 Recording Variant Titles
Record variant titles that are considered to be important for identification or access applying the basic instructions on recording titles given under 2.3.1
AACR225 Uniform Titles
25.3 Works created after 150025.3A Use the title or form of title in the original language by which a work created after 1500 has become known through use in manifestations of the work or in reference sources.
RDA6.2.2 Preferred Title for the Work
6.2.2.4 Works Created After 1500
For works created after 1500, choose as the preferred title the title in the original language by which the work has become known through use in resources embodying the work or in reference sources.
RDA, a content standardnew standard = content standard“what data should I record?”
use with different encoding schema
e.g. MARC21, Dublin Core, LOM, etc.
use with different display conventions
e.g. ISBD, label display, etc.
RDA vs AACR2RDA: content standard not a display standard use with many encoding schema data elements use by non-library metadata communities
AACR2: content and display many display conventions already ignored“areas” with string of data tied together: not
friendly for use in a web environment the library’s standard
RDA vs AACR2
RDA: “to describe all types of resources” three separate elements to record:
Content typeMedia typeCarrier type
AACR2: problems with new types of resourceslimitations of rule 0.24rules organized according to “class of material” limited list of GMDs
RDA vs AACR2using RDA’s new framework:
book Content type = text Media type = unmediated Carrier type = volume
music CD Content type = performed music Media type = audio Media type = computer Carrier type = audio disc Carrier type = computer disc
RDA vs AACR2
using RDA’s new framework:
streaming video Content type = moving image Media type = video Carrier type = online resource
web page Content type = text Media type = computer Carrier type = online resource
RDA vs AACR2RDA: more information for users no more restrictions such as “rule of three” make the relationships between entities clear to
the user:
appendices I, J and K = lists of relationship designators
no more Latin abbreviations
AACR2: limitations of the 3 x 5 card “rule of three” more focus on single record, less on relationships “et al.”, “S.l.”, “s.n.”
AACR2
21.6B and 21.6C
distinctions are made when two, three or four or more persons or bodies share responsibility
21.6B1. If, in a work of shared responsibility, principal responsibility is attributed … to one person or corporate body, enter under the heading for that person or body … Make added entries under the headings for other persons or bodies involved if there are not more than two.
RDA
no instructions to limit the number of access points
RDAno instructions to limit the number of access points
6.27.1.3. Alternative
Include in the preferred access point representing the work the preferred access points for all creators named in resources embodying the work or in reference sources (in the order in which they are named in those sources), formulated according to the guidelines and instructions given under 9.1.1 , 10.10.1 , or 11.12.1 , as applicable.
Example:Gumbley, Warren, 1962– ; Johns, Dilys; Law, Garry. Management of wetland archaeological sites in New Zealand
Latin abbreviations gone
instead of [et al.] [and six others]
instead of [S.l.] Place of publication not identified
instead of [s.n.] publisher not identified
More for digital resourcesnew data elements: record carrier type for online resource; record extent:
1 online resource (1 image file)
1 online resource (75 pages) file type
data file
streaming video file encoding format
DAISY GIF HTML
audio DVD audio image JPEG text PDF
MP3 TIFF MS Word
uniform resource locator
RDA, a new standardstandard for recording metadata
easier to apply: consistency, principles
works for both traditional and digital resources
record sufficient metadata to support better navigation and better data display
record data in separate data elements to support improved searching
extensible framework for technical and content description of new types of resources
focus on creating data to fulfill user tasks