emerging cataloging future
DESCRIPTION
Presented at the Massachusetts Library Association meeting, May 7, 2008TRANSCRIPT
The Emerging Cataloging Future
The Emerging Cataloging FutureRDA, DCMI, and the Semantic WebRDA, DCMI, and the Semantic Web
Diane I. HillmannDiane I. HillmannMassachusetts Library AssociationMassachusetts Library Association
Wednesday, May 7, 2008Wednesday, May 7, 2008
2
The Starting Point: Here and Now
The Starting Point: Here and Now
RDA: Resource Description and Access in the last stages of development
Final full draft due in August; will be “published” in early 2009
Dublin Core Metadata Initiative in partnership with RDA to develop Resource Description Vocabularies
RDA: Resource Description and Access in the last stages of development
Final full draft due in August; will be “published” in early 2009
Dublin Core Metadata Initiative in partnership with RDA to develop Resource Description Vocabularies
3
The Destination: Where We’re Going
The Destination: Where We’re Going
RDA guidelines will be available
will be used to support the creation of FRBR-based records
RD Vocabularies will be available to support catalogers and applications
Specialized communities will be building Application Profiles
RDA guidelines will be available
will be used to support the creation of FRBR-based records
RD Vocabularies will be available to support catalogers and applications
Specialized communities will be building Application Profiles
4
The Journey: A Series of Maps
The Journey: A Series of Maps
Envisioning new descriptive structures
Supporting libraries and other communities of practice as they build and share data
“Building in” support for future development and extension
Envisioning new descriptive structures
Supporting libraries and other communities of practice as they build and share data
“Building in” support for future development and extension
5
RDA & RDVocabulariesRDA & RDVocabularies
RDA: Resource Description and Access
This is the part you’ve heard about--the successor to AACR2
Resource Description Vocabularies
This is the part you may not have heard about, but it’s essential to understanding how RDA will be used
RDA: Resource Description and Access
This is the part you’ve heard about--the successor to AACR2
Resource Description Vocabularies
This is the part you may not have heard about, but it’s essential to understanding how RDA will be used
6
RDA--What can you expect?
RDA--What can you expect?
7
RDA History in a Nutshell
Step 1: AACR3
Step 2: AACR3, reorganized as RDA (FRBR invisible, still looking backwards)
Step 3: RDA, explicitly FRBR/FRAR, no longer tied explicitly to MARC
RDA History in a Nutshell
Step 1: AACR3
Step 2: AACR3, reorganized as RDA (FRBR invisible, still looking backwards)
Step 3: RDA, explicitly FRBR/FRAR, no longer tied explicitly to MARC
8
A FRBR-based approach to structuring bibliographic data
More explicitly machine-friendly linkages (preferably with URIs)
More emphasis on relationships and roles
Less reliance on cataloger-created notes and text strings (particularly for identification)
A FRBR-based approach to structuring bibliographic data
More explicitly machine-friendly linkages (preferably with URIs)
More emphasis on relationships and roles
Less reliance on cataloger-created notes and text strings (particularly for identification)
The New RDAThe New RDA
9
What would this new approach look like?
Pt.1: RDA organization
What would this new approach look like?
Pt.1: RDA organization
10
JSC ScenariosJSC Scenarios
Scenario 1: separate records for all FRBR entities with linked identifiers
Scenario 2: composite bibliographic records (with authority records representing each entity)
Scenario 3: one flat record, with all Group 1 entities on a single record
Scenario 1: separate records for all FRBR entities with linked identifiers
Scenario 2: composite bibliographic records (with authority records representing each entity)
Scenario 3: one flat record, with all Group 1 entities on a single record
11
Sect. 1: Recording Attributes of manifestation Sect. 1: Recording Attributes of manifestation and itemand item
12
Sect. 2: Recording Attributes of Work and Sect. 2: Recording Attributes of Work and ExpressionExpression
13
Sect. 6: Recording primary relationships Sect. 6: Recording primary relationships between Group I and II entitiesbetween Group I and II entities
14
Sect. 8: Recording relationships between Group Sect. 8: Recording relationships between Group I entitiesI entities
15
A Cataloger ScenarioA 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 *Work Title: Bluebeard: a novel. *Form of Work: Novel *Original Language: English
16
with links to the following expression information:
*Language of Expression: English *Content Type: Text
and one manifestation:
*Edition: 1st trade edition *Place of Production: New York *Publisher: Delacorte Press *Date of Production: 1987 *Number of Units: 300 pages *Resource Identifier: [ISBN]0385295901
17
Jane begins her description by linking to the existing Work entity. She then creates an expression description:
*Language of Expression: Latvian *Translator: Arvida Grigulis
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 Production: Riga *Publisher: Liesma *Date of Production: 1997
18
A Cataloger Scenario: Updated
A Cataloger Scenario: Updated
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 *Work Title: Bluebeard: a novel. *Form of Work: Novel *Original Language: English
19
A Cataloger Scenario: Updated
A Cataloger Scenario: Updated
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: http://lcnaf.info/79062641 *Work Title: Bluebeard: a novel. *Form of Work: http://RDVocab.info/genre/1008 *Original Language: http://marclang.info/eng
20
with links to the following expression information:
*Language of Expression: English *Content Type: Text
and one manifestation:
*Edition: 1st trade edition *Place of Production: New York *Publisher: Delacorte Press *Date of Production: 1987 *Number of Units: 300 pages *Resource Identifier: [ISBN]0385295901
21
with links to the following expression information:
*Language of Expression: http://marclang.info/eng *Content Type: http://purl.org/dc/dcmitype/Text
and one manifestation:
*Edition: 1st trade edition *Place of Production: http://www.getty.edu/tgn/7007567 *Publisher: http://onixpub.info/2039987 *Date of Production: 1987 *Number of Units: 300 pages *Resource Identifier: [ISBN]0385295901
22
Jane begins her description by linking to the existing Work entity. She then creates an expression description:
*Language of Expression: Latvian *Translator: Arvida Grigulis
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 Production: Riga *Publisher: Liesma *Date of Production: 1997
23
Jane begins her description by linking to the existing Work entity. She then creates an expression description:
*Language of Expression: http://marclang.info/lat *Translator: http://lcnaf.info/88007685
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 Production: http://www.getty.edu/tgn/7006484 *Publisher: http://onixpub.info/6770094 *Date of Production: 1997
24
Is FRBR the only model relevant here?Pt.2: DCMI steps in ...
Is FRBR the only model relevant here?Pt.2: DCMI steps in ...
25
Zoom DSL/T-burg Tel
A Dublin Core View of the WorldA Dublin Core View of the World
DCMI Abstract Model: DCMI Abstract Model: http://dublincore.org/documents/abstract-model/
26
Zoom DSL/T-burg Tel
A Dublin Core View of the WorldA Dublin Core View of the World
DCMI Abstract Model: DCMI Abstract Model: http://dublincore.org/documents/abstract-model/
27
Anatomy of a StatementAnatomy of a Statement
Place of Production: New York
PropertyPropertyPropertyProperty ValueValueValueValue
ValueValueStringStringValueValueStringString
28
Anatomy of a StatementAnatomy of a Statement
Place of Production: http://www.getty.edu/tgn/7007567
PropertyPropertyPropertyProperty ValueValueValueValue
RelatedRelatedDescriptioDescriptio
nn
RelatedRelatedDescriptioDescriptio
nn
29
A Related DescriptionA Related Description
30
Zoom DSL/T-burg Tel
Description Sets a Key ConceptDescription Sets a Key Concept
31
Description Set=“A set of one or more descriptions, each of which describes a single
resource.”*
Description Set=“A set of one or more descriptions, each of which describes a single
resource.”*
*DCAM Definition*DCAM Definition
32
A Description Set “Package”A Description Set “Package”
33
Don’t we already do vocabularies?
Pt.3: Vocabs and the SemWeb
Don’t we already do vocabularies?
Pt.3: Vocabs and the SemWeb
34
Our traditional vocabularies use text strings as identifiers
Numbers are used only for internal or intra-community transactions
The Semantic Web uses vocabularies much more rigorously, though they often use library-based standards for vocabulary relationships as a starting point
Our traditional vocabularies use text strings as identifiers
Numbers are used only for internal or intra-community transactions
The Semantic Web uses vocabularies much more rigorously, though they often use library-based standards for vocabulary relationships as a starting point
36
37
Managing VocabulariesManaging Vocabularies
Description of entire vocabulary as a collection of concepts
Links to Concepts, History, Versions
Default status and Language for Concepts
URI for the vocabulary itself (includes token)
Links to Users
Links to XML schema and RDF encoding
Description of entire vocabulary as a collection of concepts
Links to Concepts, History, Versions
Default status and Language for Concepts
URI for the vocabulary itself (includes token)
Links to Users
Links to XML schema and RDF encoding
38
Registering ConceptsRegistering ConceptsRequired Preferred Label
Multi-language support
Permanent URI for the Concept
Support for status
Links to other Concept properties
Link to RDF fragment
Required Preferred Label
Multi-language support
Permanent URI for the Concept
Support for status
Links to other Concept properties
Link to RDF fragment
39
These registry examples are for “value vocabularies”
LCSH is a value vocabulary, for example
The same strategies work for RDA Elements ...
RDA Elements is a “schema vocabulary”
These registry examples are for “value vocabularies”
LCSH is a value vocabulary, for example
The same strategies work for RDA Elements ...
RDA Elements is a “schema vocabulary”
40
List of RDA Proposed PropertiesList of RDA Proposed Properties
41
Details of Property RegistrationDetails of Property Registration
42
Metadata “About” the PropertyMetadata “About” the Property
43
Isn’t this pretty complicated?Pt.4: Tying it all
together ...
44
A Description Set “Package”A Description Set “Package”
45
“The process of "profiling" a standard introduces the prospect of a tension between meeting the demands for efficiency, specificity, and localization within the context of a community or service on the one hand, and maintaining interoperability between communities and services on the other. Different metadata standards may provide different levels of flexibility: some standards may be quite prescriptive and leave relatively few options for customization, while others may present a broad range of optional features which demand a considerable degree of selection and tailoring for implementation.”
--- from http://dublincore.org/documents/2008/01/14/singapore-framework/index.shtml
Introducing Application ProfilesIntroducing Application Profiles
46
“It is desirable to be able to use community- or domain-specific metadata standards - or component parts of those standards - in combination. The implementers of metadata standards should be able to assemble the components that they require for some particular set of functions. If that means drawing on components that are specified within different metadata standards, that should ideally be possible. They should also be safe in the knowledge that the assembled whole can be interpreted correctly by independently designed applications.”
--- from http://dublincore.org/documents/2008/01/14/singapore-framework/index.shtml
Introducing Application ProfilesIntroducing Application Profiles
47
Consider how the idea of Application Profiles affects the landscape ...
No more agonizing over which metadata standard to choose
No need to sacrifice specific community needs that aren’t covered in general standards
A standard methodology for extension
Evolving methods for testing conformance
Consider how the idea of Application Profiles affects the landscape ...
No more agonizing over which metadata standard to choose
No need to sacrifice specific community needs that aren’t covered in general standards
A standard methodology for extension
Evolving methods for testing conformance
48
Some examples of Application Profiles
SWAP (Scholarly Works Application Profile)
Collections Application Profile
KMODDL Application Profile
Some examples of Application Profiles
SWAP (Scholarly Works Application Profile)
Collections Application Profile
KMODDL Application Profile
49
Scholarly Works APScholarly Works AP
50
Collections APCollections AP
51
KMODDL APKMODDL AP
52
Declaration of Voigt1 VocabularyDeclaration of Voigt1 Vocabulary
53
Using the Vocabulary to OrganizeUsing the Vocabulary to Organize
54
Designing Datavs.
Choosing a Data Format
Designing Datavs.
Choosing a Data Format
55
Functional requirements The functional requirements of a Dublin Core Application Profile describe the functions that the application profile is designed to support, as well as functions that are out of scope.
Domain model The domain model defines the basic entities described by the application profile and their fundamental relationships. The purpose of the domain model is to define a basic scope for the application profile.
Description Set Profile (DSP)A Description Set Profile defines a set of metadata records that are valid instances of an application profile.
Mandatory Components of a Dublin Core Application Profile:
56
Usage guidelines The optional usage guidelines describe how to apply the application profile, how the used properties are intended to be used in the application context, etc.
Encoding syntax guidelines The optional encoding syntax guidelines describe any application profile- specific syntaxes and/or syntax guidelines, if any.
Optional Components of a Dublin Core Application Profile
57
Implications for our future
An end to the closed library community
A different approach to standards
A library community engaged with the Web, sharing and accepting data more broadly
Implications for our future
An end to the closed library community
A different approach to standards
A library community engaged with the Web, sharing and accepting data more broadly
Thank you!Thank you!Contact: Diane I. Hillmann
Director of Metadata Initiatives, Information Institute of Syracuse
Contact: Diane I. HillmannDirector of Metadata Initiatives, Information
Institute of [email protected]
Slides from this presentation may be re-used in conformance to the Creative Slides from this presentation may be re-used in conformance to the Creative Commons Attribution-Noncommercial-Share Alike 3.0 (United States) licenseCommons Attribution-Noncommercial-Share Alike 3.0 (United States) license