aall denver 2010

Getting from Here to There

And where is ‘There’ exactly, Anyway?

AALL 2010 Denver 2

What Does ‘There’ Look Like

Not like catalog cards

Not MARC records

Not necessarily ‘records’ at all

Not entirely our data

Data sharing, but probably not with a center point

More open, less constrained by old assumptions about functionality

Includes more collaborators outside the library silo 7/13/10

AALL 2010 Denver 3

Standards Upgrade!Type of Standard

Old Standard New Standard(s)?

Bibliographic Model

Catalog cards FRBR, FRBRoo

Metadata Content AACR2 RDA

Metadata Structure

MARC21 Bibliographic

RDVocab

Name Authority MARC21 Authority FRAD

Subject Authority MARC21 Authority FRASAR, SKOS

Encoding MARC21 XML, XML/RDF

7/13/10

AALL 2010 Denver 4

Why RDA?RDA is a FRBR-based approach to structuring

bibliographic data

It contains more explicitly machine-friendly linkages (preferably with URIs)

There’s more emphasis on relationships and roles …

… and less emphasis on cataloger-created notes and text strings (particularly for identification)

Less emphasis on transcription (important in an increasingly digital world) 7/13/10

AALL 2010 Denver 5

RDA & FRBR: Registered!RDA WEMI Elements:

http://metadataregistry.org/schema/show/id/1.html

RDA Roles: http://metadataregistry.org/schema/show/id/4.html

RDA Vocabulary: Base Material http://metadataregistry.org/vocabulary/show/id/35.

html

FRBRer Model http://metadataregistry.org/schemaprop/list/schem

a_id/5.html

7/13/10

AALL 2010 Denver 6

Who’s Doing This?DCMI/RDA Task Group

See: http://dublincore.org/dcmirdataskgroup/ Set up during the April 2007 London meeting

between JSC and DCMI Gordon Dunsire and Diane Hillmann, co-chairs Karen Coyle & Alistair Miles, consultants

IFLA Classification and Indexing Section Gordon Dunsire, Centre for Digital Library

Research, University of Strathclyde, registering FRBR entities and relationships, FRAD, ISBD, etc.

7/13/10

AALL 2010 Denver 7

Walking through a concrete example …

From the Cataloger Scenarios

7/13/10

7/13/10 8AALL 2010 Denver

A Cataloger Scenario

Jane Cataloger is assigned to work on a gift collection. Her first selection is a Latvian translation of Kurt Vonnegut's "Bluebeard: a novel." She searches the library database for the original work, and finds:

*Author: Kurt Vonnegut *Title of the work: Bluebeard: a novel *Form of work: Novel *Original language of the work: English

AALL 2010 Denver 97/13/10

<frbrWork ID="rda.basic/01”>

<rdarole:author>Kurt Vonnegut</rdarole:author><titleOfTheWork>Bluebeard: a novel</titleOfTheWork><formOfWork>Novel</formOfWork>

<originalLanguageOfTheWork>English<originalLanguageOfTheWork></frbrWork>

Translated to RDA/XML:

Upgraded to RDA/XML with Links:<frbrWork ID="rda.basic/01”>

<rdarole:author>http://lcnaf.info/79062641</rdarole:author><titleOfTheWork>Bluebeard: a novel</titleOfTheWork><formOfWork>http://RDVocab.info/genre/1008</formOfWork>

<originalLanguageOfTheWork>http://marclang.info/eng </></frbrWork>

AALL 2010 Denver 7/13/10 10

with links to the following expression information:

*Language of expression: English *Content type: Text

and one manifestation:

*Statement designating edition: 1st trade edition *Place of publication: New York *Publisher’s name: Delacorte Press *Date of publication: 1987 *Extent of text: 300 pages *Identifier for the manifestation: [ISBN]0385295901

AALL 2010 Denver 117/13/10

<frbrExpression ID="rda.basic/07”>

<contentType>Text</contentType><languageOfExpression>English<languageOfExpression></frbrExpression>

Translated to RDA/XML:

Upgraded to RDA/XML with Links:

<frbrExpression ID="rda.basic/07”>

<formOfWork>http://RDVocab.info/termList/RDAContentType/1020</><languageOfExpression>http://marclang.info/eng </>

</frbrExpression>

AALL 2010 Denver 127/13/10

<frbrManifestation ID="rda.basic/09”>

<statementDesignatingEdition>1st Trade Edition</><placeOfPublication>New York<placeOfPublication>

<publishersName>Delacorte Press</publishersName><dateOfPublication>1987</dateOfPublication><extentOfText>300 pages</extentOfText><identifierForTheManifestation>[ISBN]0385295901</>

</frbrManifestation>

Translated to RDA/XML (with links below):

<frbrManifestatiion ID="rda.basic/09”>

<statementDesignatingEdition>1st Trade Edition</><placeOfPublication>http://www.getty.edu/tgn/7007567</>

<publishersName>http://onixpub.info/2039987</><dateOfPublication>1987</dateOfPublication><extentOfText>300 pages</extentOfText><identifierForTheManifestation>urn:ISBN:0385295901</>

</frbrManifestation>

AALL 2010 Denver 137/13/10

Work

Exp: eng

Man: eng

FRBR Group 1

AALL 2010 Denver 7/13/10 14

Jane begins her description by linking to the existing Work entity. She then creates an expression description:

*Content type: text*Language of expression: Latvian*Translator: Grigulis, Arvīds

She creates an authority record for the translator since none yet existed. She continues by creating a fuller description for the new manifestation, linking to the authority record for the Latvian publisher (what luck, it already existed!).

*Title: [in Latvian]*Place of publication: Riga*Publisher’s name: Liesma*Date of publication: 1997*Extent of Text: 315 pages

AALL 2010 Denver 157/13/10

<frbrExpression ID="rda.basic/11”>

<contentType>text</contentType><languageOfExpression>Latvian<languageOfExpression>

<rdarole:translator>Grigulis, Arvīds</rdarole:translator></frbrExpression>

Translated to RDA/XML:

Upgraded to RDA/XML with Links:<frbrExpression ID="rda.basic/11”>

<formOfWork>http://RDVocab.info/termList/RDAContentType/1020</><languageOfExpression>http://marclang.info/lav </><rdarole:translator>http://lcnaf.info/83219993

</frbrExpression>

AALL 2010 Denver 167/13/10

<frbrManifestation ID="rda.basic/09”>

<title>[in Latvian]</><placeOfPublication>Riga<placeOfPublication><publishersName>Liesma</publishersName><dateOfPublication>1997</dateOfPublication><extentOfText>315 pages</extentOfText>

</frbrManifestation>

Translated to RDA/XML (with links below):

<frbrManifestatiion ID="rda.basic/09”>

<placeOfPublication>http://www.getty.edu/tgn/7006484</><publishersName>http://onixpub.info/6770094</><dateOfPublication>1997</dateOfPublication><extentOfText>315 pages</extentOfText>

</frbrManifestation>

AALL 2010 Denver 177/13/10

Work

Exp: eng

Man: eng

Exp: lav

Man: lav

FRBR Group 1

AALL 2010 Denver 187/13/10

Work

Exp: eng

Man: eng

Exp: lav

Man: lav

Author

Publisher

Translator

FRBR Group 1 FRBR Group 2

AALL 2010 Denver 197/13/10

Work

Exp: eng

Man: eng

Exp: lav

Man: lav

Author

Publisher

Translator

FRBR Group 1 FRBR Group 2

FRBR Group 3

Subjects

ConceptsObjectsEventsPlaces

AALL 2010 Denver 207/13/10

Work

Exp: eng

Man: eng

Exp: lav

Man: lav

Author

Publisher

Translator

FRBR Group 1 FRBR Group 2

FRBR Group 3

Subjects

ConceptsObjectsEventsPlaces

Content Vocabularies

Media Vocabularies

Other InformationIn the “Cloud”

RelationshipVocabularie

s

AALL 2010 Denver 21

Can Standards Help?Not Necessarily Library Standards …

7/13/10

AALL 2010 Denver 22

Semantic Web Standards

RDF: Resource Description Framework Statements about Web resources in the form of subject-

predicate-object expressions, called triples E.g. “This presentation” –“has creator” –“Diane Hillmann”

RDF Schema Vocabulary description language of RDF

SKOS: Simple Knowledge Organisation System Expresses the basic structure and content of concept

schemes such as thesauri and other types of controlled vocabularies

An RDF application OWL (Web Ontology Language)

Explicitly represents the meaning of terms in vocabularies and the relationships between them

7/13/10

AALL 2010 Denver 23

Semantic Web Building Blocks

Each component of an RDF statement (triple) is a “resource”

RDF is about making machine-processable statements, requiring A machine-processable language for representing

RDF statementsExtensible Markup Language (XML)

A system of machine-processable identifiers for resources (subjects, predicates, objects)Uniform Resource Identifier (URI) For full machine-processing potential, an RDF

statement is a set of three URIs7/13/10

AALL 2010 Denver 24

Things Requiring Identification

Object “This presentation” e.g. its electronic location (URL)

Predicate “has creator” e.g. http://purl.org/dc/terms/creator

Object “Diane Hillmann” One option: URI of entry in Library of Congress

Name Authority File (real soon now?) NAF: nr2001015786

Declaring vocabularies/values in SKOS and OWL provides URIs—essential for the Semantic Web

7/13/10

AALL 2010 Denver 25

Examining RDA GeneticsRDA’s model is primarily FRBR and FRAD, but

also takes some of its DNA from Dublin Core

DC’s Abstract Model de-composes traditional metadata “records” and re-composes them with additional levels above and below what we’ve traditionally thought of as our “atomic level”

The DCAM also talks about “statements” in ways that help connect RDA to the Semantic Web

7/13/10

AALL 2010 Denver 7/13/10 26

A Dublin Core View of the World

DCMI Abstract Model: http://dublincore.org/documents/abstract-model/

AALL 2010 Denver 7/13/10 27

A Dublin Core View of the World

DCMI Abstract Model: http://dublincore.org/documents/abstract-model/

AALL 2010 Denver 7/13/10 28

Anatomy of a Statement

Place of Production: New York

Property Value

ValueString

AALL 2010 Denver 7/13/10 29

Anatomy of a Statement

Place of Production: http://www.getty.edu/tgn/7007567

Property Value

RelatedDescription

AALL 2010 Denver 7/13/10 30

Description Sets a Key Concept!

AALL 2010 Denver

Description Set=“A set of one or more descriptions, each of which describes a single

resource.”*

31

*DCAM Definition

7/13/10

AALL 2010 Denver 32

A Different StrategyWhat Happens When We Give Up the Record as Our Basic Unit?

7/13/10

AALL 2010 Denver 33

Our View of the Internet, 1995

“The turning point for the World Wide Web was the

introduction[4] of the Mosaic web browser[5] in 1993, a

graphical browser developed by a team at the National Center for Supercomputing Applications

(NCSA) at the University of Illinois at Urbana-Champaign

(UIUC), led by Marc Andreessen.” --

Wikipedia

7/13/10

AALL 2010 Denver 34

What Would Happen If …We stopped thinking about our data as

‘records’

Instead, we started thinking of our data as ‘statements’

We started thinking of these statements as able to be aggregated in a variety of ways, for a variety of purposes Including sharing with others, both within the

library and beyond

What would that look like?

7/13/10

AALL 2010 Denver 357/13/10

ID=23456 hasAuthor “Kurt Vonnegut”

ID=23456 hasPreferredTitle “Bluebeard,

a novel”

ID=23456 isFormOfWork “Novel”

ID=23456 hasOriginalLanguage

“English”

ID=23456

hasPlaceOfPublication “New

Yorkl”

ID=23456

hasStatementOfEdition “1 st

trade edition”

ID=23456 hasL

anguageOfExp

ress

ion

“Englis

h”

ID=23456 hasPublisher “Delacorte

Press”ID=23456 hasPublicationDate

“1987”

Statements on the Floor?

AALL 2010 Denver 367/13/10

ID=23456 hasAuthor “Kurt Vonnegut”

ID=23456 hasPreferredTitle “Bluebeard,

a novel”

ID=23456 isFormOfWork “Novel”

ID=23456 hasOriginalLanguage

“English”

ID=23456

hasPlaceOfPublication “New

Yorkl”

ID=23456

hasStatementOfEdition “1 st

trade edition”

ID=23456 hasLanguageOfExpression

“English”

ID=23456 hasPublisher “Delacorte

Press”

ID=23456 hasPublicationDate

“1987”

Is This Really Chaos?

AALL 2010 Denver 377/13/10

ID=23456 hasAuthor “Kurt Vonnegut”

ID=23456 hasPreferredTitle “Bluebeard,

a novel”

ID=23456 isFormOfWork “Novel”

ID=23456 hasOriginalLanguage

“English”

ID=23456

hasPlaceOfPublication “New

Yorkl”

ID=23456

hasStatementOfEdition “1 st

trade edition”

ID=23456 hasLanguageOfExpression

“English”

ID=23456 hasPublisher “Delacorte

Press”

ID=23456 hasPublicationDate

“1987”

Or Just an AggregationIn the Making?

AALL 2010 Denver 387/13/10

ID=23456 hasAuthor “Kurt Vonnegut”

ID=23456 hasPreferredTitle “Bluebeard, a novel”

ID=23456 isFormOfWork “Novel”

ID=23456 hasOriginalLanguage

“English”

ID=23456

hasPlaceOfPublication “New

Yorkl”

ID=23456

hasStatementOfEdition “1 st

trade edition”

ID=23456 hasLanguageOfExpression

“English”

ID=23456 hasPublisher “Delacorte

Press”

ID=23456 hasPublicationDate

“1987”

AALL 2010 Denver 397/13/10

ID=23456 hasAuthor “Kurt Vonnegut”

ID=23456 hasPreferredTitle “Bluebeard, a novel”

ID=23456 isFormOfWork “Novel”

ID=23456 hasOriginalLanguage “English”

ID=23456

hasPlaceOfPublication “New

Yorkl”

ID=23456

hasStatementOfEdition “1 st

trade edition”

ID=23456 hasLanguageOfExpression

“English”

ID=23456 hasPublisher “Delacorte

Press”

ID=23456 hasPublicationDate

“1987”

AALL 2010 Denver 407/13/10

ID=23456 hasAuthor “Kurt Vonnegut”

ID=23456 hasPreferredTitle “Bluebeard, a novel”

ID=23456 isFormOfWork “Novel”

ID=23456 hasOriginalLanguage “English”

ID=23456

hasPlaceOfPublication “New

Yorkl”

ID=23456

hasStatementOfEdition “1 st

trade edition”ID=23456 hasLanguageOfExpression

“English”

ID=23456 hasPublisher “Delacorte

Press”

ID=23456 hasPublicationDate

“1987”

AALL 2010 Denver 417/13/10

ID=23456 hasAuthor “Kurt Vonnegut”

ID=23456 hasPreferredTitle “Bluebeard, a novel”

ID=23456 isFormOfWork “Novel”

ID=23456 hasOriginalLanguage “English”

ID=23456

hasPlaceOfPublication “New

Yorkl”

ID=23456

hasStatementOfEdition “1 st

trade edition”ID=23456 hasLanguageOfExpression

“English”

ID=23456 hasPublisher “Delacorte

Press”

ID=23456 hasPublicationDate

“1987”

Work

AALL 2010 Denver 427/13/10

ID=23456

hasPlaceOfPublication “New

Yorkl”

ID=23456

hasStatementOfEdition “1 st

trade edition”

ID=23456 hasLanguageOfExpression “English”

ID=23456 hasPublisher “Delacorte

Press”

ID=23456 hasPublicationDate

“1987”

AALL 2010 Denver 437/13/10

ID=23456

hasPlaceOfPublication “New

Yorkl”

ID=23456 hasStatementOfEdition “1st

trade edition”

ID=23456 hasLanguageOfExpression “English”

ID=23456 hasPublisher “Delacorte

Press”

ID=23456 hasPublicationDate

“1987”

AALL 2010 Denver 447/13/10

ID=23456

hasPlaceOfPublication “New

Yorkl”

ID=23456 hasStatementOfEdition “1st

trade edition”

ID=23456 hasLanguageOfExpression “English”

ID=23456 hasPublisher “Delacorte

Press”

ID=23456 hasPublicationDate

“1987”

Expression

AALL 2010 Denver 457/13/10

ID=23456 hasPlaceOfPublication “New

Yorkl”

ID=23456 hasPublisher “Delacorte

Press”

ID=23456 hasPublicationDate

“1987”

AALL 2010 Denver 467/13/10

ID=23456 hasPlaceOfPublication “New

Yorkl”

ID=23456 hasPublisher “Delacorte Press”

ID=23456 hasPublicationDate

“1987”

AALL 2010 Denver 477/13/10

ID=23456 hasPlaceOfPublication “New

Yorkl”

ID=23456 hasPublisher “Delacorte Press”

ID=23456 hasPublicationDate “1987”

AALL 2010 Denver 487/13/10

ID=23456 hasPlaceOfPublication “New

Yorkl”

ID=23456 hasPublisher “Delacorte Press”

ID=23456 hasPublicationDate “1987”

Manifestation

AALL 2010 Denver 49

Extensible PotentialBecause of the way the RDA Vocabularies are

built, specialized communities can extend them in ways that support (not break) interoperability

The aggregation of statements into FRBR ‘packages’ could be done in a completely different way to suit a particular community's needs without losing interoperability

This is an entirely different way of thinking about data: It doesn’t require up-front consensus It doesn’t imply losers and winners when needs

conflict It sets communities free to build interoperable

data on their own terms

7/13/10

AALL 2010 Denver 50

Yet More Challenges We need application profiles that express more than

one notion of “Work” and more than one community point of view JSC still seeing the process through the lens of a text

cataloger The law library community (and others) have many

unmet needs with the current RDA

Moving the MARC legacy data into RDA OCLC has yet to reveal any details about their planning The eXtensible Catalog Project has a running start on this

Multi-lingual and specialized extensions Non-Anglo-American communities eager to participate

7/13/10

AALL 2010 Denver 51

Multi-lingual RDAThe Registry approach:

Translations of labels, definitions and comments reside within the save vocabulary, with separate language attributes

URIs stay the same, as do relationships Responsibility for updating translations rests with

translation “owner”—who is enabled as a maintainer in the main vocabulary

Requires a “web of trust” and organizational commitment

So far, seems to have support from JSC and ALA Publishing

7/13/10

AALL 2010 Denver 52

Some Questions (not answers)

If we base our notions of aggregation on FRBR, does that imply that we exchange data as FRBR WEMI packages? Do those packages include all four levels, or one

level only?

How will we manage the identity of these packages? Identity is key to making sharing work well

Will we need to manage these statements as aggregates?

How will we continually upgrade and add data to these aggregations?

7/13/10

AALL 2010 Denver 53

The BIG Questions Remaining

What do we anticipate will be different about our changed working environment?

How will workflow change?

How will the data look?

What will the library vendor systems do with it?

How will we integrate user data? What kinds of user data?

What do we need to know to operate in this new environment?

7/13/10

AALL 2010 Denver 54

Thanks & Acknowledgements

Thanks for your attention!

Slides will be available on Slideshare: http://slideshare.net/smartbroad/

Contact for Diane: Email: metadata.maven@gmail.com Website: http://managemetadata.com/

7/13/10