Slide 1

FROM AACR2 to RDA

(and a few things in between)

The history and context of RDAdevelopment

Jenny Stephens, National Library ofAustralia, October 2010

Revised 2012

This work is licensed under the Creative Commons Attribution 3.0Australia License http://creativecommons.org/licenses/by/3.0/au/

Overview

•From AACR2 to RDA, Part I: History andContext

•FRBR/FRAD

•From AACR2 to RDA, Part II: Structure

Overview

TODAY -

•History of RDA Development

•International context

History of RDA

Why replace AACR2?

•International Conference 1997

–Analysis of underlying structure of AACR2

–Intellectual Content vs. Physical format

•Too much to just “amend” AACR2

History of RDA

AACR3?

2004 proposal for AACR3:

–Extensive revision of Part I of AACR2

–Alignment with FRBR

–Addition of a third section for authority control

•Constraints of working within existing AACRstructure

History of RDA

2005 – new standard

•Built on the foundations of AACR2

BUT

•New structure and new emphasis

•Designed for the digital world

•Adaptable and flexible for the future

History of RDA

•Three parts:

–Resource description

–Provision of Access points

–Formulation of data used for authority control

•Focused on user tasks

•Independent of presentation/encoding standards

•More user-friendly wording, layout andformatting

FRBR/FRAD/FRSAD

MARC

ISBD

RDA

InternationalCataloguingPrinciples

Metadatastandards

Advances in Web Development

InternationalContext

•Growth of shared cataloguing

•Lower level cataloguing

•Catalogues not meeting user needs

•1990- IFLA study to define the functionalrequirements of bibliographic records

Functional requirements forBibliographic and Authority Data

FRBR/FRAD/FRSAD

[Source: Adapted from Functional Requirements for Bibliographic records (FRBR), Functional requirements for Authority Data (FRAD), CatherineArgus, 2010]

•Functional Requirements for Bibliographic Records (1998)

•Functional Requirements for Authority Data (2009)

•Functional Requirements for Subject Authority Data (2010)

•Ongoing review, eventual consolidation.

FRBR/FRAD/FRSAD

Functional requirements forBibliographic and Authority Data

[Source: Adapted from Functional Requirements for Bibliographic records (FRBR), Functional requirements for Authority Data (FRAD), CatherineArgus, 2010]

Conceptual models

–Identify & define the things that are important - entities

–Identify & define the attributes that characterise the entities

–Identify & define significant relationships between entities

Functional requirements forBibliographic and Authority Data

FRBR/FRAD

[Source: RDA : Resource description and access, Deirdre Kiorgaard. RDA information session for QUT students, August 31, 2010]

•Define bibliographic entities

–resources, people, families, corporate bodies, and subjects

•List their attributes

•Identify the relationships between the entities

•Map to user tasks

FRBR/FRAD

Functional requirements forBibliographic and Authority Data

[Source: Adapted from: What you need to know about FRBR and FRAD when reading RDA, Pat Riva, May 2009]

•are not cataloguing rules

•are not system models

•do not prescribe how they might be implemented

FRBR/FRAD

Functional requirements forBibliographic and Authority Data

[Source: Adapted from Functional Requirements for Bibliographic records (FRBR), Functional requirements for Authority Data (FRAD),Catherine Argus, 2010]

•RDA uses FRBR and FRAD concepts, terms anduser tasks

•RDA content and organisation reflect FRBR andFRAD

–Attributes

–Relationships

FRBR and RDA

FRBR/FRAD

[Source: Functional Requirements for Bibliographic records (FRBR), Functional requirements for Authority Data (FRAD), Catherine Argus, 2010]

Paris Principles 1961

• Achieved international standardisation

• Used as the basis of most cataloguing standards

BUT

• Covered only textual works

• Focused on choice and form of entries

InternationalCataloguing Principles

•All types of materials

• All aspects of bibliographic and authority data

•Built on FRBR Model

•Underlying principles of RDA

InternationalCataloguing Principles

International CataloguingPrinciples 2009

International CataloguingPrinciples 2009

Principles:

• Convenience of users

• Common usage

• Representation

• Accuracy

• Sufficiency and necessity

•Significance

InternationalCataloguing Principles

Principles (continued):

• Economy

• Consistency and standardisation

• Integration

http://www.ifla.org/publications/statement-of-international-cataloguing-principles

InternationalCataloguing Principles

International CataloguingPrinciples 2009

International StandardBibliographic Description (1971)

•Aims

•Promotion of uniform bibliographic description

•Facilitates shared cataloguing

•Determined

•Required data elements

•Sequence of elements

•Prescribed punctuation

•Multiple ISBDs for different formats

•AACR2 framework based on ISBD

ISBD

International StandardBibliographic Description (2007)

•Aims unchanged

•Single consolidated ISBD that is format neutral

•Conformed to FRBR data elements

•Influenced RDA development, but do not dictate structure.

http://www.ifla.org/publications/ifla-series-on-bibliographic-control-44

ISBD

•Machine Readable Code for cataloguedata

•Based on layout of card catalogue

•Still the most widely used encoding standard inlibrary systems.

•Developed beyond boundaries of AACR2

MARC

Bibliographic Framework TransitionInitiative

MARC

Working Group on the Future of Bibliographic Control (2008)

US RDA Test (2010)

MARC Standard insufficient for current and future needs

Bibliographic Framework Transition Initiative

Progress to date:

•Consultation with Libraries, MARC users, MARBI andother standards groups

•Defined requirements for the new bibliographicframework.

•Contracted Zepheira to develop model(s) fordiscussion within community

http://www.loc.gov/marc/transition/

MARC

World wide web ofinformation

Metadatastandards

RDF

Semanticweb

LinkedData

Developed and maintained by cultural and computer science sectors

Metadata standards

Developed for the National Science Digital Library (NSDL), now open to allmetadata communities.

Registry forApplication profiles

Defined a set of coremetadata elements.

RDA on OMR

http://metadataregistry.org/schema/list/page/3.html

ONIX

Set of standardsdeveloped byPublishing industry

Metadata standards

•Books

•Serials

•Licensing terms and rights information

http://www.editeur.org/8/ONIX/

Semantic Web

Source: Video still from Intro to the Semantic Web by Manu Spornyhttp://www.youtube.com/watch?v=OGg8A2zfWKg

Linked Data

1.Use URIs as names for things

2.Use HTTP URIs so that people can look up thosenames.

3.When someone looks up a URI, provide usefulinformation, using the standards (RDF*, SPARQL)

4.Include links to other URIs. so that they candiscover more things.

http://www.w3.org/DesignIssues/LinkedData.html

RDF

•Resource Description Framework (RDF)

•Model for labelling and linking informationusing URIs

http://www.w3.org/TR/2004/REC-rdf-primer-20040210/#statements

RDA Today

2010

–Published June 2010

–Free public trial of Toolkit

–Subscriptions available

–US National Testing, 2nd half 2010

2011

Full Report: Report and Recommendations of the U.S. RDA Test Coordinating Committee

–Recommended implementation not before 2013,pending

•Rewording of text

•Changes to the content of RDA

•Significant progress towards replacing MARC

–US National Libraries accepted recommendations

–LC, Canada, Britain and Australia agreed to a jointimplementation.

RDA Today

Where are we at now?

•LC has announced a firm implementation dateof March 1, 2013.

•National Library of Australia - rollingimplementation beginning January 2013

•Training documentation being developed

•Rewording of RDA text nearing completion

•Progress towards replacement of MARCcontinues.

RDA Today

At the National Library of Australia

•Develop and provide training

•Policies

•System changes

•Update documentation

RDA Today

Sources

International Federation of Library Associations

www.ifla.org

Joint Steering Committee for the Development of RDA

www.rda-jsc.org

Dublin Core Metadata Initiative

http://dublincore.org/

Editeur

http://www.editeur.org/

Sources

Oliver, Chris, Introducing RDA : a guide to the basics (London,Facet Publishing, 2010)

Argus, Catherine, Functional Requirements for Bibliographicrecords (FRBR), Functional requirements for Authority Data(FRAD). [Powerpoint presentation, 2010]

Kiorgaard, Deirdre, RDA : Resource description and access, [RDAinformation session for QUT students, August 31, 2010]