Dublin Core Metadata Jenn Riley Metadata Librarian IU Digital Library Program.

Dublin Core Metadata

Jenn Riley

Metadata Librarian

IU Digital Library Program

November 21, 2005 L597: Advanced Cataloging 2

Many definitions of metadata

“Data about data” “Structured information about an information

resource of any media type or format.” (Caplan)

“Any data used to aid the identification, description and location of networked electronic resources.” (IFLA)

…


Types of Metadata

Descriptive metadata Administrative metadata

Technical metadata Preservation metadata Rights metadata

Structural metadata

…cataloging, AND MUCH MORE!


How metadata is used


Uses of Dublin Core

By information specialists Describing non-traditional materials Cataloging Web sites

By novices Web sites Eprints Non-library applications

Metadata sharing


DC History

1995: 13-element set emerged from a meeting in Dublin, OH, hosted by OCLC

1996: Expanded to 15 elements 1998: Issued as IETF RFC 2413 2000: Qualifiers created 2001: Released as ANSI/NISO Z39.85 2003: Released as ISO 15836


DCMI Mission

The mission of DCMI is to make it easier to find resources using the Internet through the following activities: Developing metadata standards for discovery

across domains, Defining frameworks for the interoperation of

metadata sets, and, Facilitating the development of community- or

disciplinary-specific metadata sets that are consistent with items 1 and 2


DC Principles

“Core” across all knowledge domains No element required All elements repeatable Extensible 1:1 principle “Dumb-down” principle


Simple Dublin Core

Content elements Intellectual property elements Instantiation elements


DC Content Elements

Coverage Description Type Relation Source Subject Title


DC:Coverage

Definition: The extent or scope of the content of the resource.

Comment: Typically, Coverage will include spatial location (a place name or geographic coordinates), temporal period (a period label, date, or date range) or jurisdiction (such as a named administrative entity). Recommended best practice is to select a value from a controlled vocabulary (for example, the Thesaurus of Geographic Names [TGN]) and to use, where appropriate, named places or time periods in preference to numeric identifiers such as sets of coordinates or date ranges.

Examples: Boston, MA; 17th century


DC:Description

Definition: An account of the content of the resource. Comment: Examples of Description include, but is not

limited to: an abstract, table of contents, reference to a graphical representation of content or a free-text account of the content.

Examples: Illustrated guide to airport markings and lighting signals, with particular reference to SMGCS (Surface Movement Guidance and Control System) for airports with low visibility conditions.


DC:Type

Definition: The nature or genre of the content of the resource.

Comment: Type includes terms describing general categories, functions, genres, or aggregation levels for content. Recommended best practice is to select a value from a controlled vocabulary (for example, the DCMI Type Vocabulary). To describe the physical or digital manifestation of the resource, use the FORMAT element.

Examples: Image; Text


DC:Relation

Definition: A reference to a related resource. Comment: Recommended best practice is to

identify the referenced resource by means of a string or number conforming to a formal identification system.

Examples: References Adrian Lyne's ‘Lolita’; 1998 movie Oscar and Lucinda


DC:Source

Definition: A reference to a resource from which the present resource is derived.

Comment: The present resource may be derived from the Source resource in whole or in part. Recommended best practice is to identify the referenced resource by means of a string or number conforming to a formal identification system.

Examples: RC607.A26 W574 1996; Image from page 54 of the 1922 edition of Romeo and Juliet


DC:Subject

Definition: The topic of the content of the resource.

Comment: Typically, Subject will be expressed as keywords, key phrases or classification codes that describe a topic of the resource. Recommended best practice is to select a value from a controlled vocabulary or formal classification scheme.

Examples: Dogs; Olympic skiing; Street, Picabo


DC:Title

Definition: The topic of the content of the resource.

Comment: Typically, Title will be a name by which the resource is formally known.

Examples: A Pilot's Guide to Aircraft Insurance; The Sound of Music


DC Intellectual Property Elements

Creator Contributor Publisher Rights


DC:Creator

Definition: An entity primarily responsible for making the content of the resource.

Comment: Examples of Creator include a person, an organization, or a service. Typically, the name of a Creator should be used to indicate the entity.

Examples: Shakespeare, William; Wen Lee


DC:Contributor

Definition: An entity responsible for making contributions to the content of the resource.

Comment: Examples of Contributor include a person, an organization, or a service. Typically, the name of a Contributor should be used to indicate the entity.

Examples: Hubble Telescope; Internal Revenue Service. Customer Complaints Unit


DC:Publisher

Definition: An entity responsible for making the resource available.

Comment: Examples of Publisher include a person, an organization, or a service. Typically, the name of a Publisher should be used to indicate the entity.

Examples: University of South Where; Funky Websites, Inc.


DC:Rights

Definition: Information about rights held in and over the resource.

Comment: Typically, Rights will contain a rights management statement for the resource, or reference a service providing such information. Rights information often encompasses Intellectual Property Rights (IPR), Copyright, and various Property Rights. If the Rights element is absent, no assumptions may be made about any rights held in or over the resource.

Examples: Access limited to members; http://cs-tr.cs.cornell.edu/Dienst/Repository/2.0/Terms


DC Instantiation Elements

Date Format Identifier Language


DC:Date

Definition: A date associated with an event in the life cycle of the resource.

Comment: Typically, Date will be associated with the creation or availability of the resource. Recommended best practice for encoding the date value is defined in a profile of ISO 8601 [W3CDTF] and includes (among others) dates of the form YYYY-MM-DD.

Examples: 1998-02-16; 1998-02; 1998


DC:Format

Definition: The physical or digital manifestation of the resource.

Comment: Typically, Format may include the media-type or dimensions of the resource. Format may be used to identify the software, hardware, or other equipment needed to display or operate the resource. Examples of dimensions include size and duration. Recommended best practice is to select a value from a controlled vocabulary (for example, the list of Internet Media Types [MIME] defining computer media formats).

Examples: bronze; 22 in.; image/gif


DC:Identifier

Definition: An unambiguous reference to the resource within a given context.

Comment: Recommended best practice is to identify the resource by means of a string or number conforming to a formal identification system. Formal identification systems include but are not limited to the Uniform Resource Identifier (URI) (including the Uniform Resource Locator (URL)), the Digital Object Identifier (DOI) and the International Standard Book Number (ISBN).

Examples: http://purl.oclc.org/metadata/dublin_core/; ISBN:0385424728; H-A-X 5690B


DC:Language

Definition: A language of the intellectual content of the resource.

Comment: Recommended best practice is to use RFC 3066 [RFC3066] which, in conjunction with ISO639 [ISO639]), defines two- and three-letter primary language tags with optional subtags.

Examples: en; fr; Primarily English, with some abstracts also in French


DC Qualified (DMCI Terms)

Additional elements Element refinements Encoding schemes

Vocabulary encoding schemes Syntax encoding schemes


DC Qualifier Status

Recommended Conforming Obsolete Registered


DC Qualified Additional Elements

Audience (Recommended) Provenance (Conforming) accrualMethod (Conforming) accrualPeriodicity (Conforming) accrualPolicy (Conforming) instructionalMethod (Conforming) rightsHolder (Conforming)


Recommended DC Element Refinements Audience.mediator Coverage.spatial Coverage.temporal Date.available Date.created Date.issued Date.modified Date.valid Description.abstract Description.tableOfContents Format.extent Format.medium Title.alternative

Relation.conformsTo Relation.hasFormat Relation.hasPart Relation.hasVersion Relation.isFormatOf Relation.isPartOf Relation.isReferencedBy Relation.isReplacedBy Relation.isRequiredBy Relation.isVersionOf Relation.references Relation.replaces Relation.requires


Conforming DC Element Refinements

Audience.educationLevel Date.dateAccepted Date.dateCopyrighted Date.dateSubmitted Identifier.bibliographicCitation Rights.accessRights Rights.license


DC Encoding Schemes

Coverage.spatial Box ISO3166 Point TGN

Coverage.temporal Period

Date W3CDTF

Format IMT

Identifier/Source/Relation URI

Language ISO639-2 RFC1766 RFC3066

Subject DDC LCC LCSH MESH UDC

Type DCMIType


OCLC Connexion DC Qualifiers (1)

Title.alternativeUniform Title.variant Title.translated Title.uniform Type.note Contributor.nameConference Contributor.nameCorporate Contributor.namePersonal Creator.nameConference Creator.nameCorporate Creator.namePersonal Format.extentDuration

Publisher.nameConference Publisher.nameCorporate Publisher.namePersonal Publisher.place Rights.access Relation.isPartOfSeries Relation.indexedBy Relation.findingAid Relation.hasReview Source.dateIssued Source.extent Source.publicationDetail


OCLC Connexion DC Qualifiers (2)

Description.summary Description.scope Description.subject Description.audience Description.audienceAge Description.audienceGrade Description.award Description.note Description.dataQualityNote Description.entity-

AttributeNote Description.actionNote Description.version Description.versionDetails

Subject.class Subject.classAuto Subject.classLocal Subject.geographic Subject.name Subject.nameConference Subject.nameCorporate Subject.namePersonal Subject.titleUniform Subject.topical Identifier.canceled Identifier.citation Identifier.incorrect


DC Encodings

HTML <meta> XML RDF Spreadsheets Databases


DC is not a data content standard


How to create DC records

Articulate use of this record Determine whether to use simple DC or

qualified DC Determine content standard to use Identify any existing metadata for the

resource Use existing metadata and add anything

that’s missing


More information

DC Usage Guide DCMI Metadata Terms DC Mailing Lists

[email protected] These presentation slides:

<http://www.dlib.indiana.edu/~jenlrile/presentations/slis/05fall/l597/advCataloging.ppt>

Dublin Core Metadata Jenn Riley Metadata Librarian IU Digital Library Program.

Documents

Transcript of Dublin Core Metadata Jenn Riley Metadata Librarian IU Digital Library Program.