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

2. November 21, 2005 L597: Advanced Cataloging2 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) …

3. November 21, 2005 L597: Advanced Cataloging3 Types of Metadata Descriptive metadata Administrative metadata Technical metadata Preservation metadata Rights metadata Structural metadata …cataloging, AND MUCH MORE!

4. November 21, 2005 L597: Advanced Cataloging4 How metadata is used

5. November 21, 2005 L597: Advanced Cataloging5 Uses of Dublin Core By information specialists Describing non-traditional materials Cataloging Web sites By novices Web sites Eprints Non-library applications Metadata sharing

6. November 21, 2005 L597: Advanced Cataloging6 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 2413IETF RFC 2413 2000: Qualifiers created 2001: Released as ANSI/NISO Z39.85ANSI/NISO Z39.85 2003: Released as ISO 15836ISO 15836

7. November 21, 2005 L597: Advanced Cataloging7 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

8. November 21, 2005 L597: Advanced Cataloging8 DC Principles “Core” across all knowledge domains No element required All elements repeatable Extensible 1:1 principle “Dumb-down” principle

9. November 21, 2005 L597: Advanced Cataloging9 Simple Dublin Core Content elements Intellectual property elements Instantiation elements

10. November 21, 2005 L597: Advanced Cataloging10 DC Content Elements Coverage Description Type Relation Source Subject Title

11. November 21, 2005 L597: Advanced Cataloging11 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; 17 th century

12. November 21, 2005 L597: Advanced Cataloging12 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.

13. November 21, 2005 L597: Advanced Cataloging13 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.DCMI Type Vocabulary Examples: Image; Text

14. November 21, 2005 L597: Advanced Cataloging14 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

15. November 21, 2005 L597: Advanced Cataloging15 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

16. November 21, 2005 L597: Advanced Cataloging16 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

17. November 21, 2005 L597: Advanced Cataloging17 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

18. November 21, 2005 L597: Advanced Cataloging18 DC Intellectual Property Elements Creator Contributor Publisher Rights

19. November 21, 2005 L597: Advanced Cataloging19 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

20. November 21, 2005 L597: Advanced Cataloging20 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

21. November 21, 2005 L597: Advanced Cataloging21 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.

22. November 21, 2005 L597: Advanced Cataloging22 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

23. November 21, 2005 L597: Advanced Cataloging23 DC Instantiation Elements Date Format Identifier Language

24. November 21, 2005 L597: Advanced Cataloging24 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.W3CDTF Examples: 1998-02-16; 1998-02; 1998

25. November 21, 2005 L597: Advanced Cataloging25 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).MIME Examples: bronze; 22 in.; image/gif

26. November 21, 2005 L597: Advanced Cataloging26 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 5690Bhttp://purl.oclc.org/metadata/dublin_core/

27. November 21, 2005 L597: Advanced Cataloging27 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.RFC3066ISO639 Examples: en; fr; Primarily English, with some abstracts also in French

28. November 21, 2005 L597: Advanced Cataloging28 DC Qualified (DMCI Terms)DMCI Terms Additional elements Element refinements Encoding schemes Vocabulary encoding schemes Syntax encoding schemes

29. November 21, 2005 L597: Advanced Cataloging29 DC Qualifier Status Recommended Conforming Obsolete Registered

30. November 21, 2005 L597: Advanced Cataloging30 DC Qualified Additional Elements Audience (Recommended) Provenance (Conforming) accrualMethod (Conforming) accrualPeriodicity (Conforming) accrualPolicy (Conforming) instructionalMethod (Conforming) rightsHolder (Conforming)

31. November 21, 2005 L597: Advanced Cataloging31 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

32. November 21, 2005 L597: Advanced Cataloging32 Conforming DC Element Refinements Audience.educationLevel Date.dateAccepted Date.dateCopyrighted Date.dateSubmitted Identifier.bibliographicCitation Rights.accessRights Rights.license

33. November 21, 2005 L597: Advanced Cataloging33 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

34. November 21, 2005 L597: Advanced Cataloging34 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

35. November 21, 2005 L597: Advanced Cataloging35 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

36. November 21, 2005 L597: Advanced Cataloging36 DC Encodings HTML XML RDF Spreadsheets Databases

37. November 21, 2005 L597: Advanced Cataloging37 DC is not a data content standard

38. November 21, 2005 L597: Advanced Cataloging38 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

39. November 21, 2005 L597: Advanced Cataloging39 More information DC Usage Guide DCMI Metadata Terms DC Mailing Lists jenlrile@indiana.edu These presentation slides: