Using Dublin Core
Using Dublin Core™ - The Elements
| Creator: | Diane Hillmann |
|---|---|
| Date Issued: | 2005-08-15 |
| Identifier: | http://dublincore.org/specifications/dublin-core/usageguide/2005-08-15/elements/ |
| Replaces: | http://dublincore.org/specifications/dublin-core/usageguide/2003-08-26/elements/ |
| Is Replaced By: | http://dublincore.org/specifications/dublin-core/usageguide/2005-11-07/elements/ |
| Is Part Of: | http://dublincore.org/specifications/dublin-core/usageguide/2005-08-15/ |
| Latest Version: | http://dublincore.org/specifications/dublin-core/usageguide/elements/ |
| Status of Document: | DCMI Recommended Resource |
| Description of Document: | This document is intended as an entry point for users of Dublin Core™. For non-specialists, it will assist them in creating simple descriptive records for information resources (for example, electronic documents). Specialists may find the document a useful point of reference to the documentation of Dublin Core, as it changes and grows. |
This section lists each element by its full name and label. For each element there are guidelines to assist in creating metadata content, whether it is done "from scratch" or by converting an existing record in another format.
In the element descriptions below, a formal single-word label is specified to make the syntactic specification of elements simpler for encoding schemes. Although some environments, such as HTML, are not case-sensitive, it is recommended best practice always to adhere to the case conventions in the element names given below to avoid conflicts in the event that the metadata is subsequently converted to a case-sensitive environment, such as XML.
Some information may appear to belong in more than one metadata element. While there will normally be a clear preferred choice, there is potential semantic overlap between some elements. Consequently, there will occasionally be some judgment required from the person assigning the metadata.
4.1. Title
Label: Title
Element Description: The name given to the resource. Typically, a Title will be a name by which the resource is formally known.
Guidelines for creation of content:
If in doubt about what constitutes the title, repeat the Title element and include the variants in second and subsequent Title iterations. If the item is in HTML, view the source document and make sure that the title identified in the title header (if any) is also included as a Title.
Examples:
Title="A Pilot's Guide to Aircraft Insurance"
Title="The Sound of Music"
Title="Green on Greens"
Title="AOPA's Tips on Buying Used Aircraft"
4.2. Subject
Label: Subject and Keywords
Element Description: The topic of the content of the resource. Typically, a Subject will be expressed as keywords or key phrases or classification codes that describe the topic of the resource. Recommended best practice is to select a value from a controlled vocabulary or formal classification scheme.
Guidelines for creation of content:
Select subject keywords from the Title or Description information, or from within a text resource. If the subject of the item is a person or an organization, use the same form of the name as you would if the person or organization were a Creator or Contributor.
In general, choose the most significant and unique words for keywords, avoiding those too general to describe a particular item. Subject might include classification data if it is available (for example, Library of Congress Classification Numbers or Dewey Decimal numbers) or controlled vocabularies (such as Medical Subject Headings or Art and Architecture Thesaurus descriptors) as well as keywords.
When including terms from multiple vocabularies, use separate element iterations. If multiple vocabulary terms or keywords are used, either separate terms with semi-colons or use separate iterations of the Subject element.
Examples:
Subject="Aircraft leasing and renting"
Subject="Dogs"
Subject="Olympic skiing"
Subject="Street, Picabo"
4.3. Description
Label: Description
Element Description: An account of the content of the resource. Description may 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.
Guidelines for creation of content:
Since the Description field is a potentially rich source of indexable terms, care should be taken to provide this element when possible. Best practice recommendation for this element is to use full sentences, as description is often used to present information to users to assist in their selection of appropriate resources from a set of search results.
Descriptive information can be copied or automatically extracted from the item if there is no abstract or other structured description available. Although the source of the description may be a web page or other structured text with presentation tags, it is generally not good practice to include HTML or other structural tags within the Description element. Applications vary considerably in their ability to interpret such tags, and their inclusion may negatively affect the interoperability of the metadata.
Examples:
Description="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."
Description="Teachers Domain is a multimedia library for K-12 science educators, developed by WGBH through funding from the National Science Foundation as part of its National Science Digital Library initiative. The site offers a wealth of classroom-ready instructional resources, as well as online professional development materials and a set of tools which allows teachers to manage, annotate, and share the materials they use in classroom teaching."
4.4. Type
Label: Resource Type
Element Description: The nature or genre of the content of the resource. 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 DCMIType vocabulary ). To describe the physical or digital manifestation of the resource, use the FORMAT element.
Guidelines for content creation:
If the resource is composed of multiple mixed types then multiple or repeated Type elements should be used to describe the main components.
Because different communities or domains are expected to use a variety of type vocabularies, best practice to ensure interoperability is to include at least one general type term from the DCMIType vocabulary in addition to the domain specific type term(s), in separate Type element iterations.
Examples:
Type="Image"
Type="Sound"
Type="Text"
Type="simulation"
Note: The first three values are taken from the DCMI Type Vocabulary, and follow the capitalization conventions for that vocabulary. The last value is a term from an unspecified source.
The item described is an Electronic art exhibition catalog:
Type="Image"
Type="Text"
Type="Exhibition catalog"
Note: The first two values are taken from the DCMI Type Vocabulary, and follow the capitalization conventions for that vocabulary. The last value is a term from an unspecified source.
The item described is a Multimedia educational program with interactive assignments:
Type="Image"
Type="Text"
Type="Software"
Type="Interactive Resource"
Note: All values in this example are taken from the DCMI Type Vocabulary, and follow the capitalization conventions for that vocabulary.
4.5. Source
Label: Source
Element Description: A Reference to a resource from which the present resource is derived. The present resource may be derived from the Source resource in whole or part. Recommended best practice is to reference the resource by means of a string or number conforming to a formal identification system.
Guidelines for content creation:
In general, include in this area information about a resource that is related intellectually to the described resource but does not fit easily into a Relation element.
Examples:
Source="RC607.A26W574 1996" [where "RC607.A26W574 1996" is the call number of the print version of the resource, from which the present version was scanned]
Source="Image from page 54 of the 1922 edition of Romeo and Juliet"
4.6. Relation
Label: Relation
Element Description: A reference to a related resource. Recommended best practice is to reference the resource by means of a string or number conforming to a formal identification system.
Guidelines for content creation:
Relationships may be expressed reciprocally (if the resources on both ends of the relationship are being described) or in one direction only, even when there is a refinement available to allow reciprocity. If text strings are used instead of identifying numbers, the reference should be appropriately specific. For instance, a formal bibliographic citation might be used to point users to a particular resource.
Because the refined terms used with Relation provide significantly more information to a user than the unqualified use of Relation, implementers who are describing heavily interrelated resources might choose to use qualified Dublin Core™.
Examples:
Title="Reading Turgenev"
Relation="Two Lives" [Resource is a collection of two novellas, one of which is "Reading Turgenev"]
[Relationship described is IsPartOf.__[Part/Whole relations are those in which one resource is a physical or logical part of another]> Title="Candle in the Wind"
Subject="Diana, Princess of Wales"
Date="1997"
Creator="John, Elton"
Type="sound"
Description="Tribute to a dead princess."
Relation="Elton John's 1976 song Candle in the Wind"
[Relationship described is IsVersionOf.
[Version relations are those in which one resource is an historical state or edition, of another resource by the same creator]
Title="Electronic AACR2"
Relation="Anglo-American Cataloging Rules, 2nd edition"
[Relationship described is IsFormatOf]> Title="Landsat TM dataset of Arnhemland, NT, Australia"
Relation="arnhem.gif"
[Relationship described is HasFormat]
[Format transformation relations are those in which one resource has been derived from another by a reproduction or reformatting technology which is not fundamentally an interpretation but intended to be a representation.]
Title="Morgan's Ancient Society"
Relation="Engels' Origin of the Family, Private Property and the State"
[Relationship described is IsReferencedBy]> Title="Nymphet Mania"
Relation="References Adrian Lyne's 'Lolita'"
[Relationship described is References]
[Reference relations are those in which the author of one resource cites, acknowledges, disputes or otherwise make claims about another resource.]
Title="Peter Carey's novel Oscar and Lucinda"
Relation="1998 movie Oscar and Lucinda"
[Relationship described is IsBasisFor]> Title="The movie My Fair Lady"
Relation="Shaw's play Pygmalion"
[Relationship described is IsBasedOn]
[Creative relations are those in which one resource is a performance, production, derivation, adaptation or interpretation of another resource.]
Title="Dead Ringer"
Relation="Gemstar e-book"
[Relationship described is Requires]
[Dependency relations are those in which one resource requires another resource for its functioning, delivery, or content and cannot be used without the related resource being present.]
4.7. Coverage
Label: Coverage
Element Description: The extent or scope of the content of the resource. Coverage will typically include spatial location (a place name or geographic co-ordinates), 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 [Getty Thesaurus of Geographic Names, http://www.getty.edu/research/tools/vocabulary/tgn/]). Where appropriate, named places or time periods should be used in preference to numeric identifiers such as sets of co-ordinates or date ranges.
Guidelines for content creation:
Whether this element is used for spatial or temporal information, care should be taken to provide consistent information that can be interpreted by human users, particularly in order to provide interoperability in situations where sophisticated geographic or time-specific searching is not supported. For most simple applications, place names or coverage dates might be most useful. For more complex applications, consideration should be given to using an encoding scheme that supports appropriate specification of information, such as DCMI Period, DCMI Box or DCMI Point.
Examples:
Coverage="1995-1996"
Coverage="Boston, MA"
Coverage="17th century"
Coverage="Upstate New York"
4.8. Creator
Label: Creator
Element Description: An entity primarily responsible for making the content of the resource. Examples of a Creator include a person, an organization, or a service. Typically the name of the Creator should be used to indicate the entity.
Guidelines for creation of content:
Creators should be listed separately, preferably in the same order that they appear in the publication. Personal names should be listed surname or family name first, followed by forename or given name. When in doubt, give the name as it appears, and do not invert.
In the case of organizations where there is clearly a hierarchy present, list the parts of the hierarchy from largest to smallest, separated by full stops and a space. If it is not clear whether there is a hierarchy present, or unclear which is the larger or smaller portion of the body, give the name as it appears in the item.
If the Creator and Publisher are the same, do not repeat the name in the Publisher area. If the nature of the responsibility is ambiguous, the recommended practice is to use Publisher for organizations, and Creator for individuals. In cases of lesser or ambiguous responsibility, other than creation, use Contributor.
Examples:
Creator="Shakespeare, William"
Creator="Wen Lee"
Creator="Hubble Telescope"
Creator="Internal Revenue Service. Customer Complaints Unit"
4.9. Publisher
Label: Publisher
Element Description: The entity responsible for making the resource available. Examples of a Publisher include a person, an organization, or a service. Typically, the name of a Publisher should be used to indicate the entity.
Guidelines for content creation:
The intent of specifying this field is to identify the entity that provides access to the resource. If the Creator and Publisher are the same, do not repeat the name in the Publisher area. If the nature of the responsibility is ambiguous, the recommended practice is to use Publisher for organizations, and Creator for individuals. In cases of ambiguous responsibility, use Contributor.
Examples:
Publisher="University of South Where"
Publisher="Funky Websites, Inc."
Publisher="Carmen Miranda"
4.10. Contributor
Label: Contributor
Element Description: An entity responsible for making contributions to the content of the resource. Examples of a Contributor include a person, an organization or a service. Typically, the name of a Contributor should be used to indicate the entity.
Guideline for content creation:
The same general guidelines for using names of persons or organizations as Creators apply here. Contributor is the most general of the elements used for "agents" responsible for the resource, so should be used when primary responsibility is unknown or irrelevant.
4.11. Rights
Label: Rights Management
Element Description: Information about rights held in and over the resource. Typically a Rights element 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 can be made about the status of these and other rights with respect to the resource.
Guidelines for content creation:
The Rights element may be used for either a textual statement or a URL pointing to a rights statement, or a combination, when a brief statement and a more lengthy one are available.
Examples:
Rights="Access limited to members"
Rights="http://cs-tr.cs.cornell.edu/Dienst/Repository/2.0/Terms"
4.12. Date
Label: Date
Element Description: A date associated with an event in the life cycle of the resource. 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 [Date and Time Formats, W3C Note, http://www.w3.org/TR/NOTE-datetime] and follows the YYYY-MM-DD format.
Guidelines for content creation:
If the full date is unknown, month and year (YYYY-MM) or just year (YYYY) may be used. Many other schemes are possible, but if used, they may not be easily interpreted by users or software.
Examples:
4.13. Format
Label: Format
Element Description: The physical or digital manifestation of the resource. Typically, Format may include the media-type or dimensions of the resource. Examples of dimensions include size and duration. Format may be used to determine the software, hardware or other equipment needed to display or operate the resource.
Recommended best practice is to select a value from a controlled vocabulary (for example, the list of Internet Media Types [http://www.iana.org/assignments/media-types/] defining computer media formats).
Guidelines for content creation:
In addition to the specific physical or electronic media format, information concerning the size of a resource may be included in the content of the Format element if available. In resource discovery size, extent or medium of the resource might be used as a criterion to select resources of interest, since a user may need to evaluate whether they can make use of the resource within the infrastructure available to them.
When more than one category of format information is included in a single record, they should go in separate iterations of the element.
Examples:
Title="Dublin Core™ icon"
Identifier="http://purl.org/metadata/dublin_core/images/dc2.gif"
Type="Image"
Format="image/gif"
Format="4 kB"> Subject="Saturn"
Type="Image"
Format="image/gif 6"
Format="40 x 512 pixels"
Identifier="http://www.not.iac.es/newwww/photos/images/satnot.gif"> Title="The Bronco Buster"
Creator="Frederic Remington"
Type="Physical object"
Format="bronze"
Format="22 in."
4.14. Identifier
Label: Resource Identifier
Element Description: An unambiguous reference to the resource within a given context. Recommended best practice is to identify the resource by means of a string or number conforming to a formal identification system. Examples of formal identification systems include the Uniform Resource Identifier (URI) (including the Uniform Resource Locator (URL), the Digital Object Identifier (DOI) and the International Standard Book Number (ISBN).
Guidelines for content creation:
This element can also be used for local identifiers (e.g. ID numbers or call numbers) assigned by the Creator of the resource to apply to a particular item. It should not be used for identification of the metadata record itself.
Examples:
Identifier="http://purl.oclc.org/metadata/dublin_core/"
Identifier="ISBN:0385424728"
Identifier="H-A-X 5690B" [publisher number]
4.15. Language
Label: Language
Element Description: A language of the intellectual content of the resource. Recommended best practice for the values of the Languge element is defined by RFC 3066 [RFC 3066, http://www.ietf.org/rfc/rfc3066.txt] which, in conjunction with ISO 639 [ISO 639, http://www.oasis-open.org/cover/iso639a.html]), defines two- and three-letter primary language tags with optional subtags. Examples include "en" or "eng" for English, "akk" for Akkadian, and "en-GB" for English used in the United Kingdom.
Guidelines for content creation:
Either a coded value or text string can be represented here. If the content is in more than one language, the element may be repeated.
Examples:
Language="en"
Language="fr"
Language="Primarily English, with some abstracts also in French."
Language="en-US"
NOTE: Audience, Provenance and RightsHolder are elements, but not part of the Simple Dublin Core™ fifteen elements. Use Audience, Provenance and RightsHolder only when using Qualified Dublin Core™.
4.16. Audience
Label: Audience
Element Description: A class of entity for whom the resource is intended or useful. A class of entity may be determined by the creator or the publisher or by a third party.
Guidelines for content creation:
Audience terms are best utilized in the context of formal or informal controlled vocabularies. None are presently recommended or registered by DCMI, but several communities of interest are engaged in setting up audience vocabularies. In the absence of recommended controlled vocabularies, implementors are encouraged to develop local lists of values, and to use them consistently.
Examples:
Audience="elementary school students"
Audience="ESL teachers"
Audience="deaf adults"
4.17. Provenance
Label: Provenance
Element Description: A statement of any changes in ownership and custody of the resource since its creation that are significant for its authenticity, integrity and interpretation. The statement may include a description of any changes successive custodians made to the resource.
Guidelines for content creation:
Examples:
Provenance="This copy once owned by Benjamin Spock."
Provenance="Estate of Hunter Thompson."
Provenance="Stolen in 1999; recovered by the Museum in 2003."
4.18. RightsHolder
Label: Rights Holder
Element Description: A person or organization owning or managing rights over the resource. Recommended best practice is to use the URI or name of the Rights Holder to indicate the entity.
Guidelines for content creation:
Since, for the most part, people and organizations are not typically assigned URIs, a person or organization holding rights over a resource would be named using a text string. People and organizations sometimes have websites, but URLs for these are not generally appropriate for use in this context, since they are not clearly identifying the person or organization, but rather the location of a website about them.
Examples:
RightsHolder="Stuart Weibel"
RightsHolder="University of Bath"