You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Below full descriptions of the elements are provided.
DCMI definitions come from the DCMI guidelines document "Using Dublin Core - The Elements" see http://dublincore.org/documents/usageguide/elements.shtml .

Title

Element name

Title

DCMI definition

A name given to the resource. Typically, a Title will be a name by which the resource is formally known.

Usage

Mandatory

Usage instruction

Preserve the original wording, order and spelling of the resource title. Only capitalize proper nouns. Punctuation need not reflect the usage of the original. Subtitles should be separated from the title by a colon. . This instruction would result in Title:Subtitle (i.e. no space). If necessary, repeat this character for multiple titles.

Do not confuse with

(n.a.)

Examples 

<dc:title>Main title:Sub-title </dc:title> \\
<dc:title>Dewey Classificatie in Archief systemen:Dewey Classification in Archival systems</dc:title> \\
<dc:title>Preliminary studies for the "Philosophical Investigations", generally known as the blue and brown books </dc:title> \\

Creator

Element name

Creator

DCMI definition

An entity primarily responsible for making the content of the resource. Typically, the name of a Creator should be used to indicate the entity.

Usage

Mandatory

Usage instruction

Examples of a Creator include a person, an organization, or a service. If necessary, repeat this element for multiple authors. Use inverted name, so the syntax will be the following: "surname", "initials" ("first name") "prefix" For example Jan Hubert de Smit becomes
<dc:creator> Smit, J.H.(John) de</dc:creator> Within the scope of Unqualified DC it is recommended to use a standardised writing style for names, use the writing style used by the publisher when this is available. When that is not available use the encoding of the APA bibliographic writing style as in a reference list when applicable. (outside the scope of Unqualified DC more precise and granular formatting methods are available.)When initials and first name are both available use this formatting: <dc:creator> Janssen, J. (John)</dc:creator> Generational suffixes (Jr., Sr., etc.) should follow the surname. When in doubt, give the name as it appears, and do not invert. Omit titles (like "dr", "ir" etc.)
For example: "Dr. John H. de Smit Jr." becomes
<dc:creator> Smit Jr., J.H. (John) de </dc:creator>
In the case of an organization name which clearly includes an organizational hierarchy, list the parts of the hierarchy from largest to smallest, separated by full stops.
For example:
<dc:creator> Utrecht University. Department of Computer Sciences </dc:creator>
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 resource. Only encode organisations in this element to indicate corporate authorship, not to indicate the affiliation of an individual. The inclusion of personal and corporate name headings from authority lists constructed according to local or national thesaurus files is optional.
It is recommended to encode thesauri with an URI, for service providers to recognise the thesaurus schema.
For example:
<dc:creator> urn:NationalOrgThesaurus:nl/234 </dc:creator>
In cases of lesser responsibility, other than authorship, use dc:contributor. If the nature of the responsibility is ambiguous, recommended best practice is to use dc:publisher for organizations, and dc:creator for individuals.

Do not confuse with

  • Contributor (see also User instruction above).
  • Publisher.
    The DC element 'creator' describes the name(s) of the creator(s) of the resource, as mentioned in the resource, whereas the DC element 'contributor' describes the scientist(s) that has/have made contributions to the given scientific output, not as a primary creator or (commercial) publisher.

Examples

<dc:creator>Evans, R.J.</dc:creator>
<dc:creator>Walker Jnr., John</dc:creator>
<dc:creator>International Human Genome Sequencing Consortium</dc:creator>
<dc:creator>Loughborough University. Department of Computer Science</dc:creator>

Subject

Element name

Subject

DCMI definition

The topic of the resource. Typically, a Subject will be expressed as keywords, key phrases or classification codes that describe the intellectual content of the resource.

Usage

Mandatory when applicable

Usage instruction

In the DC subject element two kinds of values are possible: encode either a keyword or a classification. When both are available use separate occurrences of this element.
Use the first occurrence of the DC element 'subject' for a human readable keyword.
In general, choose the most significant and unique words for keywords, avoiding those too general to describe a particular resource. If the subject of the resource is a person or an organization, use the same form of the name as you would if the person or organization were an author, but do not repeat the name in the dc:creator element.
For keywords/keyphrases that are not controlled by a vocabulary or thesaurus either encode multiple terms with a semi-colon separating each keyword/keyphrase; or repeat the element for each term. There are no requirements regarding the capitalization of keywords though internal (within archive) consistency is recommended.
Where terms are taken from a standard classification schema: encode each term in a separate element. Encode the complete subject descriptor according to the relevant scheme. Use the capitalisation and punctuation used in the original scheme.
It is recommended to use an URI when using classification schemes or controlled vocabularies especially when codified schemes are used DDC or UDC. Service providers can recognise encoding schemas more easy when the schema is "URI-fied" by an authority namespace. When the classification scheme is codified, use a human readable text of the code, preferably in English, directly below the codified element. For example:
<dc:subject>info:eu-repo/classification/ddc/641</dc:subject>
<dc:subject>Anatomy</dc:subject>

If no specific classification scheme is used we recommend the Dewey Decimal Classification (DDC). The first 1000 terms is called the Dewey Decimal Classification Summary and can be downloaded at http://www.oclc.org/dewey/resources/summaries/ if one agrees with the following terms and conditions:
http://www.oclc.org/research/researchworks/ddc/terms.htm

Do not confuse with

  • Type
    DC element 'subject' describes the topic(s) of an resource; DC element 'type' describes the kind of academic output / Publication Type the resource is a representation of.

Schema

More on subject classification, see the section Subject classification on page in chapter "Use of Vocabularies and Semantics".

Examples

<dc:subject>polar oceanography; boundary current; mass transport; water masses; halocline; mesoscale eddies</dc:subject>
<dc:subject>Germany-History-1933-1945</dc:subject>
<dc:subject>info:eu-repo/classification/ddc/641</dc:subject>
<dc:subject>Anatomy</dc:subject>

Description

Element name

Description

DCMI definition

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.

Usage

Mandatory if applicable

Usage instruction

This element is used for a textual description of the content. When a resource consists of several separate physical object files, do not use dc:description to list the URL's of these files.
Default = abstract

Do not confuse with

(n.a.)

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="18a99090-6ff0-4eba-ba78-d88a759705cf"><ac:plain-text-body><![CDATA[

Examples

<dc:description>Foreword [by] Hazel Anderson; Introduction; The scientific heresy: transformation of a society; Consciousness as causal reality [etc]</dc:description>
]]></ac:plain-text-body></ac:structured-macro>
<dc:description>A number of problems in quantum state and system identification are addressed. </dc:description>

Publisher

Element name

Publisher

DCMI definition

An 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.

Usage

Mandatory if applicable

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="1a871e13-0a5d-4674-b846-eb43a08710ac"><ac:plain-text-body><![CDATA[

Usage instruction

The (commercial or non-commercial) publisher of the resource; not the (sub)institution the author is affiliated with. Publisher is used only in the bibliographic / functional sense, not an organisational one. Use only the full name of the given (commercial) publisher, not the name of an organization or institute that is otherwise [in a broader sense] associated with the creator.
]]></ac:plain-text-body></ac:structured-macro>
With university publications place the name of the faculty and/or research group or research school after the name of the university. 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. 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 eprint.
The use of publisher names from authority lists constructed according to local or national thesaurus files is optional.

Do not confuse with

  • Contributor
  • Creator
    In most cases the publisher and the creator are not the same.

Examples

<dc:publisher>Loughborough University. Department of Computer Science</dc:publisher>
<dc:publisher>University of Cambridge. Department of Earth Sciences</dc:publisher>
<dc:publisher>University of Oxford. Museum of the History of Science</dc:publisher>
<dc:publisher>University of Reading. Rural History Centre</dc:publisher>
<dc:publisher>University of Exeter. Institute of Cornish Studies</dc:publisher>
<dc:publisher>European Bioinformatics Institute</dc:publisher>
<dc:publisher>John Wiley & Sons, Inc. (US)</dc:publisher>


Contributor

Element name

Contributor

DCMI definition

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.

Usage

Optional

Usage instruction

Examples of contributors are: a supervisor, editor, technician or data collector.
Personal names should be listed as: see instructions under Creator. A "promotor", i.e. a professor supervising a student's work for a doctor's degree - is considered a contributor of a dissertation in his or her role as promotor / examiner. In less-rich Unqualified DC it is difficult to express all roles in different contexts. In the PhD thesis as a document, the key figures are the author and the supervisor. In the overall PhD process other roles are involved, such as committee members and the Master of Ceremonies, but in Unqualified these roles have to be sacrificed.
In the case of organizations : see instructions under Creator The inclusion of personal and corporate name headings from authority lists constructed according to local or national thesaurus files is optional.

Do not confuse with

  • Creator
  • Publisher
    The DC element "contributor" describes the scientist(s) that has/have made contributions to the given scientific output, not as a primary creator or (commercial) publisher.)

Examples

<dc:contributor>Sulston, John E.</dc:contributor>
<dc:contributor>Evans, R. J.</dc:contributor>
<dc:contributor>International Human Genome Sequencing Consortium</dc:contributor>
<dc:contributor>Loughborough University. Department of Computer Science</dc:contributor>

Date

Element name

Date

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="fb8a9b3d-8c10-4bba-ac38-7d36f9b87a12"><ac:plain-text-body><![CDATA[

DCMI definition

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 [W3CDTF] and follows the YYYY-MM-DD format.

]]></ac:plain-text-body></ac:structured-macro>

Usage

Mandatory

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="c50caee8-50c9-4acd-bb82-00d3b223bf36"><ac:plain-text-body><![CDATA[

Usage instruction

The date should be formatted according to the W3C encoding rules for dates and times : Complete date: - YYYY-MM-DD (e.g. 1997-07-16)where: - YYYY [four-digit year] is mandatory- MM [two-digit month (01=January, etc.)] is optional- DD [two-digit day of month (01 through 31)] is optional
]]></ac:plain-text-body></ac:structured-macro>
One date field - Date of Publication:
Often repository systems have more then one date fields that serve different purposes. Date of creation, publication, modified, promotion, etc. Unqualified DC is unable to express all these dates, and for the end-user perspective it is confusing to receive more dates from the service provider. The service provider should make a choice what date-field to pick. Preferrably in the end-users perspective the most logical and meaningful date will be the date of publication.
To reduce the ambiguity of having a number of date fields without qualifiers, we recommend to reduce the number of fields and present the most meaningful date to the service provider. In most cases this is the date of the publication. In other cases this is the date of promotion of a PhD degree.

No date of publication available:
If no date of publication is available, use any other date available. It is better to use one date than no date at all.

Datestamp additions:
Additions like "Zulu time" should NOT be part of the metadata.
Fuzzy dates:
For fuzzy dates use a logical year that most represents that period, e.g. "1650" instead of "17th century"
To express more about that temporal period, one can use the dc:coverage field. A temporal period can be expressed in a standard way when precisely defined (see Coverage) or when "fuzzy" or uncertain by free text expressions.
A service provider is able to sort dates based on date standards like W3CDTF. Since there is no standard for fuzzy dates for terms like "Renaissance" or "17th Century", they will simply not appear on date-based query results.

Do not confuse with

-

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="3ba73179-6e49-4e42-a55a-f185e6ae33ed"><ac:plain-text-body><![CDATA[

scheme

ISO 8601 [W3CDTF] [{+}http://www.w3.org/QA/Tips/iso-date+

http://www.w3.org/QA/Tips/iso-date]

]]></ac:plain-text-body></ac:structured-macro>

Examples

<dc:date>2000-12-25</dc:date>
<dc:date>1978-02</dc:date>
<dc:date>1650</dc:date>

Type

Element name

Type

DCMI definition

The type of scientific output the resource is a manifestation of. In the DC element type the kind of dissemination, or the intellectual and/or content type of the resource is described. It is used to explain to the user what kind of resource he is looking at. Is it a book or an article. Was it written for internal or external use. Etc.

Usage

DC Element 'type' is used for three purposes:

  1. Mandatory: Publication type (controlled): to indicate the type of publication based on the controlled DRIVER Publication-type vocabulary,
  2. Optional: Publication type (free): to indicate the type of publication based on a local repository vocabulary
  3. Recommended: Version (controlled): to indicate the status in the publication process.

Usage instruction

1. Publication types (controlled):
The first occurrence of the DC Element 'type' is mandatory and should be used for the type indication of the scientific output based on the DRIVER-type vocabulary. Use exact string of characters as shown in the list below. The terms are explained in detail in the chapter about vocabularies and semantics. Info:eu-repo is a namespace where the DRIVER Publication types are registered.

  • info:eu-repo/semantics/article
  • info:eu-repo/semantics/bachelorThesis
  • info:eu-repo/semantics/masterThesis
  • info:eu-repo/semantics/doctoralThesis
  • info:eu-repo/semantics/book
  • info:eu-repo/semantics/bookPart
  • info:eu-repo/semantics/review
  • info:eu-repo/semantics/conferenceObject
  • info:eu-repo/semantics/lecture
  • info:eu-repo/semantics/workingPaper
  • info:eu-repo/semantics/preprint
  • info:eu-repo/semantics/report
  • info:eu-repo/semantics/annotation
  • info:eu-repo/semantics/contributionToPeriodical
  • info:eu-repo/semantics/patent
  • info:eu-repo/semantics/other

    2. Publication types (free text):
    The second occurrence of the DC Element 'type' is optional and should be used for the subtype indication of the scientific output.
    3. Version (controlled):
    The last occurrence of the DC Element 'type' is recommended and should be used for the version of the scientific output based on the DRIVER-version vocabulary. Use exact text as shown in the list below. For more information about the version model see http://www.lse.ac.uk/library/versions/
  • info:eu-repo/semantics/draft
  • info:eu-repo/semantics/submittedVersion
  • info:eu-repo/semantics/acceptedVersion
  • info:eu-repo/semantics/publishedVersion
  • info:eu-repo/semantics/updatedVersion

    Mapping & backwards-transformability:
    For mappings of the DRIVER types from the DRIVER guidelines 1.0 see DRIVER-TYPE Mappings.

Do not confuse with

  • Format
    DC element 'type' describes the kind of academic output the resource is a representation of. DC element 'format' describes the media type of this resource.

Schemes

Publication types: see the section Publication type on page in chapter "Use of Vocabularies and Semantics".
Version vocabulary: See the section Version on page in chapter "Use of Vocabularies and Semantics".
Mappings: see the section DRIVER-TYPE Mappings on page in chapter "Use of Best Practices for OAI_DC".

Examples

<dc:type>info:eu-repo/semantics/article</dc:type>
<dc:type>info:eu-repo/semantics/publishedVersion</dc:type>

or

<dc:type>info:eu-repo/semantics/other</dc:type> <!-1->
<dc:type>image</dc:type><!-2->
<dc:type>info:eu-repo/semantics/updatedVersion</dc:type> <!-3->

Format

Element name

Format

 

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="0969b19d-c0ff-4a4b-8478-4cf4b39e000c"><ac:plain-text-body><![CDATA[

DCMI definition

The physical or digital manifestation of the resource. Typically, Format may include the media-type or dimensions of the resource. Format may be used to determine 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).

 

]]></ac:plain-text-body></ac:structured-macro>

Usage

Recommended

 

Usage instruction

Based on best practice, the IANA registered list of Internet Media Types (MIME types) is used to select a term from. For the full list see the scheme location below. Below will follow an example list of IANA MIME types:

 

 

Type

Subtype

 

 

text

  • plain
  • richtext
  • enriched
  • tab-separated-values
  • html
  • sgml
  • xml

 

 

application

  • octet-stream
  • postscript
  • rtf
  • applefile
  • mac-binhex40
  • wordperfect5.1
  • pdf
  • vnd.oasis.opendocument.text
  • zip
  • macwriteii
  • msword
  • sgml
  • ms-excel
  • ms-powerpoint
  • ms-project
  • ms-works
  • xhtml+xml
  • xml

 

 

image

  • jpeg
  • gif
  • tiff
  • png
  • jpeg2000
  • sid

 

 

audio

  • wav
  • mp3
  • quicktime

 

 

video

  • mpeg1
  • mpeg2
  • mpeg3
  • avi

 

 

If one specific resource (an instance of scientific output) has more than one physical formats (e.g. postscript and pdf) stored as different object files, all formats are mentioned in the DC element 'format', for example:

  • <dc:format>application/pdf</dc:format>
  • <dc:format>application/postscript</dc:format>
  • <dc:format>application/vnd.oasis.opendocument.text</dc:format>

 

Do not confuse with with

  • Type
  • Identifier
    DC element 'format' describes the media type of this resource. DC element 'type' describes the kind of academic output the resource is a representation of. Dc:identifier is used to represent manifestations of digital resources.

 

Scheme

the IANA registered list of Internet Media Types (MIME types) - http://www.iana.org/assignments/media-types/

 

Examples

<dc:format>video/quicktime</dc:format>
<dc:format>application/pdf</dc:format>
<dc:format>application/xml</dc:format>
<dc:format>application/xhtml+xml</dc:format>
<dc:format>application/html</dc:format>
<dc:format>application/vnd.oasis.opendocument.text</dc:format>

 

Identifier

Element name

Identifier

DCMI definition

An unambiguous reference to the resource within a given context.

Usage

Mandatory

Usage instruction

Recommended best practice is to identify the resource by means of a string or number conforming to a formal identification system. Example formal identification systems include the Uniform Resource Identifier (URI) (including the Uniform Resource Locator (URL), the Digital Object Identifier (DOI) and the NBN
The ideal use of this element is to use a direct link or a link to a jump-off page (persistent URL) from dc:identifier in the metadata record to the digital resource or a jump-off page.
Smart practice:

  1. use stable URL's
    * provide every identifier one can find about the publication.
    • (URL, DOI, NBN, ISBN, ISSN, etc.)
      * place the "most appropriate" identifier in the form of a URL at the top of the list of Identifiers. In almost all cases this is the one that will be used by a service provider to let an end-user refer to. This can be a link to a jump-off page or a direct link to the file. Also this can be a direct URL, or a redirection URL, like PURL, HANDLE or other international resolution mechanisms.

Do not confuse with

  • dc:relation (Use dc:relation to refer from one version of the resource to another.)
  • dc:source (Use dc:source for bibliographic citation of the originating resource.)

Examples

In this example the identifiers are sorted where the URL's are given first. The first URL will be considered as "most appropriate" and will be used in e.g. DRIVER to let an end-user redirect to. In this case the handle redirects to the jump-off page. A Jump-off page is a good way to refer to. The end-user has the opportunity to see more information about the object(s) he has found, see the context and enjoy the other services a local repository has to offer.
<oai_dc:dc>
...
<dc:identifier>http://hdl.handle.net/1234/5628 </dc:identifier>
<dc:identifier>http://arno.unimaas.nl/show.cgi?fid=5628 </dc:identifier>
<dc:identifier>http://n2t.info/urn:nbn:nl:ui:14-123456789</dc:identifier>
<dc:identifier>urn:nbn:nl:ui:13-123456789</dc:identifier>
<dc:identifier>urn:isbn:123456789</dc:identifier>
<dc:identifier>info:doi:10-123456789</dc:identifier>
...
</oai_dc:dc>

Source

Element name

Source

DCMI definition

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

Usage

Optional

Usage instruction

The present resource may be derived from the Source resource in whole or in part. Recommended best practice is to reference the resource by means of a string or number conforming to a formal identification system.
Best practice: Use only when the described resource is the result of digitization of non-digital originals. Otherwise, use Relation. Optionally metadata about the current location and call number of the digitized publication can be added.
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="5f66f436-e596-4494-bacb-030ffd9e4aab"><ac:plain-text-body><![CDATA[Use: Guidelines for Encoding Bibliographic Citation Information in Dublin Core Metadata ([[http://dublincore.org/documents/dc-citation-guidelines/

http://dublincore.org/documents/dc-citation-guidelines/]]).

]]></ac:plain-text-body></ac:structured-macro>

Do not confuse with

  • dc:relation
  • dc:identifier

Examples

<dc:source>Ecology Letters (1461023X) vol.4 (2001)</dc:source>
<dc:source>ISSN: 0928-0987</dc:source>

Language

Element name

Language

DCMI definition

A language of the intellectual content of the resource.

Usage

Recommended

Usage instruction

A specific resource (an instance of scientific output) is either written in one human language or more. In these cases all used languages are used in the DC element 'language'. If a specific resource (an instance of scientific output) is written in one human language and is translated into other human languages, each translation does have its own record..
Recommended: ISO 639-x, where x can be 1,2 or 3.
Best Practice: we use ISO 639-3 and by doing so we follow:
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="c715c35e-5694-48da-92a5-47c8ee7a71f2"><ac:plain-text-body><![CDATA[[[http://www.sil.org/ISO639-3/codes.asp

http://www.sil.org/ISO639-3/codes.asp]]
]]></ac:plain-text-body></ac:structured-macro>
If necessary, repeat this element to indicate multiple languages.
If ISO 639-2 and 639-1 are sufficient for the contents of a repository they can be used alternatively. Since there is a unique mapping this can be done during an aggregation process.

Do not confuse with

Scheme

ISO 639-3 http://www.sil.org/ISO639-3/codes.asp

Examples

<dc:language>eng</dc:language>
<dc:language>deu</dc:language>
<dc:language>nld</dc:language>
<dc:language>nld/dut</dc:language>
<dc:language>dut</dc:language>
<dc:language>nl</dc:language>

Relation

Element name

Relation

DCMI definition

The reference to a related resource.

Usage

Optional

Usage instruction

Recommended best practice is to reference the resource by means of a string or number conforming to a formal identification system. The DC element 'relation' can be used to indicate different kinds of relations between several metadata records. If relations between metadata records are made visible by using metadata the following holds for the distinction between versions (author version and publisher version, preprint, postprint, etc.):

  • A metadata record is self-contained
  • Different manifestations of one and the same resource (an instance of scientific output that can be described with exactly the same bibliographic metadata, except for the DC element 'format') are linked to one single metadata record using dc:relation.
    Changes in the metadata other than the DC element 'format' leads to creating a new metadata record of this new instance of scientific output, which meets all requirements formulated in this document and has a value in the DC element 'relation'.

Do not confuse with

dc:identifier and dc:source.

Examples

<dc:relation>http://hdl.handle.net/10 </dc:relation>
The value of dc:relation is the identifer of the other document.

Linking two documents:
--Document A:--
<dc:type>info:eu-repo/semantics/submittedVersion</dc:type>
<dc:identifier> http://hdl.handle.net/10</dc:identifier>
<dc:relation>http://hdl.handle.net/20</dc:relation>

--Document B:--
<dc:type>info:eu-repo/semantics/acceptedVersion</dc:type>
<dc:identifier> http://hdl.handle.net/20</dc:identifier>
<dc:relation>http://hdl.handle.net/10</dc:relation>

Coverage

Element name

Coverage

DCMI definition

The extent or scope of the content of the resource. Coverage will typically 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).

Usage

Optional

Usage instruction

Recommended best practice is to select the value from a controlled vocabulary (for example, the Getty Thesaurus of Geographic Names or TGN) and that, where appropriate, named places or time periods be used in preference to numeric identifiers as, for example, sets of co- ordinates or date ranges. If necessary, repeat this element to encode multiple locations or periods.

Do not confuse with

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="e13d69bd-f8cd-4393-8275-764ad2e2e38e"><ac:plain-text-body><![CDATA[

Scheme

  • ISO 3166 [[http://www.iso.ch/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/index.html

http://www.iso.ch/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/index.html]]
]]></ac:plain-text-body></ac:structured-macro>
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="064d4c83-0a30-427b-9a9a-ac3963ba4f9f"><ac:plain-text-body><![CDATA[* Box [[http://dublincore.org/documents/dcmi-box/

http://dublincore.org/documents/dcmi-box/]]
]]></ac:plain-text-body></ac:structured-macro>
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="9ba0efad-26f1-4451-b051-fbf45a3f7d18"><ac:plain-text-body><![CDATA[* TGN [[http://www.getty.edu/research/tools/vocabulary/tgn/

http://www.getty.edu/research/tools/vocabulary/tgn/]]
]]></ac:plain-text-body></ac:structured-macro>
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="787bd5c6-1516-4f94-94e2-423b4ef23255"><ac:plain-text-body><![CDATA[* DCMI Period [[http://dublincore.org/documents/2000/07/28/dcmi-period/

http://dublincore.org/documents/2000/07/28/dcmi-period/]]

]]></ac:plain-text-body></ac:structured-macro>

Examples

Example Spatial: ISO 3166
<dc:coverage>NL</dc:coverage>

Example Spatial: BOX
<dc:coverage> name=Western Australia; northlimit=-13.5; southlimit=-35.5; westlimit=112.5; eastlimit=129</dc:coverage>
Note ad BOX: The syntax used here is provisional, and is currently under review as part of the DCMI work on recommending coordinated syntax recommendations for HTML, XML, and RDF. These recommendations and minor editorial changes in this document can be expected to take place in the near future. Point http://dublincore.org/documents/dcmi-point/

Rights

Element name

Rights

DCMI definition

Information about rights held in and over the resource.

Usage

Recommended

Usage instruction

Typically, a Rights element will contain a rights management statement for the access or use of the object, or reference a service providing such information. Rights information often encompasses Intellectual Property Rights (IPR), Copyright, and various Property Rights.
It is preferred to refer to a rights service where the reuse rights are made clear to the end-user by using a URL. For example the Creative Commons organisation has created URIs for their different Licences in the different Jurisdictions. This can be applied to create machine readable usage licenses.

Do not confuse with

Examples

<dc:rights>(c) University of Bath, 2003</dc:rights>
<dc:rights>(c) Andrew Smith, 2003</dc:rights>
Using Creative Commons right services, makes the usage rights much more clear to the end user. More information see Use of Intellectual Property Rights. In this case Andrew Smith referring to {+}http://creativecommons.org/licenses/by-sa/2.0/uk/+
<!-- example 1 -->
<dc:rights>http://creativecommons.org/licenses/by-sa/2.0/uk/</dc:rights>
The URL provides the location where the license can be read. With creative common licenses the type of license can be recognized in the URL name itself. A pro for having the license point to an URL in this way, is that this is machine readable.

<!-- example 2 -->
<dc:rights>cc-by-sa, Andrew Smith</dc:rights>
The string cc-by-sa provides the licence type in a rough sense. The name is the person or party where the rights apply to.

<!-- example 3 -->
<dc:rights>cc-by-sa, info:eu-repo/dai/nl/344568</dc:rights>
or
<dc:rights>cc-by-nc-sa, urn:isni:234562-2</dc:rights>
Also a Digital Author Identifier (DAI) or International Standard Name Identifier (ISNI) can be used to globally uniquely identify persons and organisations and relate thse names with the approprate rights.

Audience

Element name

Audience

DCMI definition

A class of entity for whom the resource is intended or useful.

Usage

Optional

Usage instruction

A class of entity may be determined by the creator or the publisher or by a third party. On the U.S. Department of Education, Metadata Reference site, an example is given of audiences: http://www.ed.gov/admin/reference/index.jsp :

  • Administrators
  • Community Groups
  • Counsellors
  • Federal Funds Recipients and Applicants
  • Librarians
  • News Media
  • Other
  • Parents and Families
  • Policymakers
  • Researchers
  • School Support Staff
  • Student Financial Aid Providers
  • Students
  • Teachers

Do not confuse with

Examples

<dc:audience>Researchers</dc:audience>
<dc:audience>Students</dc:audience>


  • No labels