Table of contents
Document information
Title: DARE use of Dublinc Core Unknown macro: {page-info}
|
Document History
Date |
Version |
Owner |
Changelog |
|
---|---|---|---|---|
July 2006 |
Addendum |
DARE |
Addendum on v2.0 |
|
December 2004 |
2.0 |
DARE |
Second edition to be used starting from December 1 2004 |
|
October 2003 |
1.0 |
DARE |
First edition to be used starting from November 1 2003 |
|
September 2003 |
0.2 |
DARE |
Second internal version presented to project managers |
|
August 2003 |
0.1 |
DARE |
First internal version presented to project managers |
|
Abstract
The abstract describes what the application profile is about. It should contain a problem definition, the standards described by the application profile and the goal of the application profile.
Acknowledgements This document is largely based on the recommendations for the use of simple Dublin Core metadata as described in: USING SIMPLE DUBLIN CORE TO DESCRIBE EPRINTS, by Andy Powell, Michael Day and Peter Cliff, UKOLN, University of Bath, Version 1.2
[see also: http://www.intute.ac.uk/publications/eprints-uk/simpledc-guidelines.html ]
Definitions: "A DARE institutional repository is a facility, consisting of hardware, software, data and procedures, that contains digital resources representing any type of scientific output..." Specifications for a Networked Repository for Dutch Universities, version 3.0, p 6
"digital resources = any bit stream, independent of content or format, which has been marked as scientific output by an approved person..."
Within this document we use the word "resource" to describe the instance of scientific output, and the word "object" to refer to the digital bit stream.
Introductory remarks
Scope These guidelines are written primarily to facilitate the exchange of metadata between Dare partners and exchange with non-Dare partners, in compliance with the OAI-PMH definitions as distributed by DCMI. Basically these guidelines describe the mapping from an internal E.g. a Dare partner might use Marc 21 as internal format format to unqualified DC to support harvesting. The guidelines are not to be used as cataloguing instructions.
Within Dare we use unqualified DC (oai_dc).
Use of qualified DC (dare_qdc) is encouraged. Only those refinements that have been added by DCMI are to be used as refinements within Dare. These refinements have also been added in the text of the guidelines below. If a Dare partner has implemented any other (not DCMI endorsed) elements or refinements, he is obliged to eliminate these elements from the metadata during the harvesting process.
Dare partners will implement two XML schemas: one for unqualified DC for OAI compatible harvesting within the Dare community as well as outside the DARE community. Also a XML scheme will be presented for qualified DC for use within Dare.
Language of the metadata is at the discretion of the local Dare partner.
The use of Unicode is mandatory.
Only one metadata record should be used for different versions of a digital object (e.g. a postscript and a pdf version), unless the intellectual content of the versions is different. The rule of thumb is to create a new metadata record when the metadata of a version is different. This happens for instance when a new version of the resource with modifications is created and in that case recommended best practice is to use the relation element to link the newer version to the older.
In some cases (DC element 'subject' and 'type') additional information may be useful for the harvesting party and service provider. A DARE compliant data provider releases this type of information via the 'Identify request' - on IR level; not on the metadata level.
See for instance: 3. Guidelines for Optional Containers at:
http://www.openarchives.org/OAI/2.0/guidelines.htm and: http://arXiv.org/oai2?verb=Identify as well as: http://doc.utwente.nl/oai/ir?verb=Identify for best practices. Additional information can also be given in the form of textual documentation about the use metadata elements subject and type, e.g. to give information on the local classification or keywords, or information on local review policies.
The values (i.e. actual content) of the elements given below must not contain any HTML (or XML) markup. They may contain LaTeX commands, but there is no mechanism for explicitly indicating that LaTeX is being used.
Within DARE the use of elements is either:
- mandatory = the element must always be present in the metadata record
- mandatory when applicable = when the element can be obtained it should be added to the metadata record (this refers more to the input of metadata, not so much to the harvesting)
- recommended = the use of the element is recommended
- optional = it is not important whether the element is used or not
The "mandatory when applicable" status is stronger then the recommended one and this distinction is made primarily to encourage users to input certain elements when creating a metadata record to enhance services.
Some words on the use of refinements (qualifiers). When mapping to unqualified DC the IR manager has to make choices when the internal format is "richer" than unqualified DC. This means that during the mapping process all refinements are simply dropped (the DCMI dumb down principle). The effect of the dumb down principle is that the simple form of the element, i.e. without the refinement, is the default one. E.g. when the internal format distinguishes between main title and parallel title this would show as follows in DC:
Internal format
245 $aMain title$pParallel title
Qualified DC
<dc:title>Main title</dc:title>
<dcterms:alternative>Parallel title</dcterms:alternative>
Simple DC
<dc:title>Main title, Parallel title </dc:title>
However, within DARE the following values are selected as the default values for simple oai_dc
dc:descriptiondefault "abstract"
dc:date ->default "created"
dc:relation->no default
dc:coverage-> no default
dc:rights-> no default
dc:audience->default: "education level"
Within DARE this means that the date element always pertains to the date created etc. It is advised that all DARE repositories supply this information to external harvesters as information about their repository.
Second edition: major changes
As per 1/1/05 all DARE repositories are required to support oai_dc and are free to use dare_qdc. Harvesting within DARE will be based upon oai_dc.
Most important new or changed guidelines in oai_dc
- dc:identifier: In case of one object file dc:identifier contains a link (uri) to the object file OR to a jump off page. In case of more then one related object files, dc:identifier contains a link (uri) to a jump off page. Jump off pages must also be used when linking to a pre- or postprint, HTML version or any other situation where additional info must be given to the user.
- dc:creator: use: inverted name, so: surname, forename, prefix
- dc:format: URL in dc:format -> deleted
- dc:source: Reference to journal in dc:source -> changed in conformity with bibliographic citation guidelines in dc:identifier and dc:relation.
- dc:title: subject headings from title when absent -> deleted
- Subject headings mandatory -> changed into mandatory when applicable (MA)
- dc:type: "Letter to editor" is separated from the value "Article"
- dc:language: use of ISO 639-1 instead of ISO 639-2
- dc:type: the optional use of dc:type; specifically: the reviewed status of the resource (Reviewed / NonReviewed) and the status of the resource (Draft / Final) are no longer supported.
- General remark: for dumb down purposes (for instance for mapping from dare_qdc to oai_dc) the default values for oai_dc are given. See below in the short element description (oai_dc).
Most important new or changed guidelines in dare_qdc
- Correction of minor errors.
- Addition of DCMI texts from official DCMI documentation on Dublin Core and its refinements. Used document: DCMI metadata terms, version 2004-06-14 (http://www.dublincore.org/documents/dcmi-terms/#H2).
The Elements: short description
Simple DC:oai_dc
Basic element |
Status |
Encoding schemes |
|
|
|
Title |
M |
None |
Creator |
M |
None |
Subject |
MA |
Choice of keywords and classifications is free |
Description |
MA |
None |
Publisher |
MA |
None |
Contributor |
O |
None |
Date |
M |
Date | ISO 8601 W3C-DTF |
Type |
M |
METIS-list with additional DCMI types. |
Format |
R |
IANA list of MIME types |
Identifier |
M |
URI |
Source |
O |
None |
Language |
R |
ISO 639-1 |
Relation |
R |
none |
Coverage |
O |
Period |
Rights |
M |
None |
Audience |
O |
None |
If no defaults are mentioned in the oai_dc elements, please describe the specific use of the oai_dc elements in the Identify section of your IR. See for instance: 3. Guidelines for Optional Containers at:
http://www.openarchives.org/OAI/2.0/guidelines.htm and: http://arXiv.org/oai2?verb=Identify as well as: http://doc.utwente.nl/oai/ir?verb=Identify for best practices.
Qualified DC:oai_dc
Basic element |
Refinement |
Status |
Encoding schemes |
|
|
|
|
Title |
- |
M |
None |
|
Alternative |
MA |
|
Creator |
- |
M |
None |
Subject |
GOO, NBC, LCSH, MESH, DDC, LCC, UDC, LOCAL |
MA |
Choice of keywords and classifications is free. Use refinements when appropriate. |
Description |
- |
MA |
None |
|
TableOfContents |
R |
|
|
Abstract |
R |
|
Publisher |
- |
MA |
None |
Contributor |
- |
O |
None |
Date |
- |
M |
Date | ISO 8601 W3C-DTF |
Type |
- |
M |
METIS-list with additional DCMI types. |
Format |
- |
R |
IANA list of MIME types |
Identifier |
- |
M |
URI |
Source |
- |
O |
None |
Language |
- |
R |
ISO 639-1 |
Relation |
- |
R |
None |
Coverage |
- |
O |
|
Rights |
- |
M |
None |
Audienc |
- |
O |
None |
The Elements: full description
This section lists each of the Dublin Core elements. For each element the authoritative definitions and comments (except usage mandatory/optional etc, which is DARE specific) from the Dublin Core Metadata Initiative are given, followed by a DARE-specific user instruction derived form the UKOLN usage guidelines.
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 |
User 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. |
Do not confuse with |
- |
Refinements |
Alternative (Mandatory if present). [DCMI:]Any form of the title used as a substitute or alternative to the formal title of the resource. This qualifier can include Title abbreviations as well as translations. |
Examples |
Qualified DC |
Scheme |
Not applicable |
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 |
User instruction |
Examples of a Creator include a person, an organization, or a service. |
Do not confuse with |
Contributor (see also User instruction above). |
Refinements |
- |
Examples |
<dc:creator>Sulston, John E.</dc:creator> |
Scheme |
Not applicable |
Subject
Element name |
Subject |
DCMI definition |
The topic of the resource. Typically, a Subject will be expressed as keyword, key phrases or classification codes that describe the intellectual content of the resource. |
Usage |
Mandatory when applicable |
User instruction |
In the DC subject element two kinds of values are possible. The first - the use of keywords - is mandatory. The second - the use of a classification - is optional. |
Do not confuse with |
Type. |
Refinements |
LCSH, MESH, DDC, LCC, UDC, GOO, NBC and LOCAL |
Examples |
<dc:subject>polar oceanography; boundary current; mass transport; |
Scheme |
LCSH, MESH, DDC, LCC, UDC, NBC and GOO |
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 |
User 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. |
Do not confuse with |
- |
Refinements |
Tableofcontent (recommended) [DCMI:] A list of subunits of the content of the resource. |
Examples |
<dc:description>Inleiding; 5 hoofdstukken over geschiedenis; 2 hoofdstukken met praktische tips; index</dc:description> |
Scheme |
Not applicable |
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 |
User 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. |
Do not confuse with |
|
Refinements |
- |
Examples |
<dc:publisher>Loughborough University. Department of Computer Science</dc:publisher> |
Scheme |
Not applicable |
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 |
User instruction |
Examples of contributors are: a supervisor, editor, technician or data collector. |
Do not confuse with |
-Creator |
Refinements |
- |
Examples |
<dc:contributor>Sulston, John E.</dc:contributor> |
Scheme |
Not applicable |
Date
Element name |
Date |
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. |
Usage |
Mandatory |
User instruction |
The date should be formatted according to the W3C encoding rules for dates and times : |
Do not confuse with |
- |
Refinements |
DateAccepted (Optional) [DCMI:] Date of acceptance of the resource (e.g. of thesis by university department, of article by journal, etc.). |
Examples |
<dc:date>2000-12-25</dc:date> |
Schema |
Date | ISO 8601 W3C-DTF see: http://www.w3.org/TR/NOTE-datetime |
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 |
Mandatory. In every metadata record one DC element 'type' should be used. |
User instruction |
Use the first occurrence of the DC element 'type' for the type indication of the scientific output. The list shown below is identical with the list used within the Metis application. Repeat if applicable. Use the text, not the numbers.
|
Do not confuse with |
Format |
Refinements |
- |
Examples |
<dc:type>preprint</dc:type> |
Scheme |
|
Format
Element name |
Format |
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). |
Usage |
Recommended |
User instruction |
The DC element 'format' is used in order to give DARE partners the necessary context to base services on. A DARE partner can selectively harvest those records that link to resources that use or operate on software, hardware or other equipment that is supported by the DARE partner's institute. |
Do not confuse with |
Type |
Refinements |
Extent (Optional) [DCMI:] The size or duration of the resource. E.g. number of pages of an article. |
Examples |
<dc:format>application/pdf</dc:format> |
Scheme |
the IANA registered list of Internet Media Types (MIME types) |
Identifier
Element name |
Identifier |
DCMI definition |
An unambiguous reference to the resource within a given context. |
Usage |
Mandatory |
User instruction |
Use an URI to point to the resource (metadata). |
Do not confuse with |
dc:source and dc:relation |
Refinements |
|
Example |
Open URL syntax example: |
Scheme |
Dcterms |
Further information |
Open URL: See also: http://library.caltech.edu/openurl/ |
Example of a Dublin Core Description of a Journal Article: dare_qdc
Property |
Encoding Scheme |
Value |
dc:title |
|
Studying E-Journal User Behavior Using Log Files |
dc:creator |
|
Yu, L. |
dc:creator |
|
Apps, A. |
dc:subject |
dcterms:DDC |
020 |
dc:subject |
dcterms:LCC |
Z671 |
dc:publisher |
|
Elsevier |
dc:type |
dcterms:DCMIType |
Text |
dcterms:issued |
dcterms:W3CDTF |
2000 |
dcterms:isPartOf |
dcterms:URI |
urn: ISSN:0740-8188 |
dcterms:bibliographicCitation |
|
Library and Information Science Research 22(3), 311-338. (2000) |
For oai_dc repeat dc:subject and dc:type and describe in the order in which oai_dc elements are used in the Identify section of your IR. See for instance: http://arXiv.org/oai2?verb=Identify for best practice.
Source
Element name |
Source |
DCMI definition |
A reference to a resource from which the present resource is derived. |
Usage |
Optional |
User 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. |
Do not confuse with |
dc:relation and dc:identifier |
Refinements |
Bibl. Citation (Optional) [DCMI:] A bibliographic reference for the resource. |
Example |
<dc:source>Ecology Letters (1461023X) vol.4 (2001)</dc:source> |
Scheme |
ISSN, ISBN |
Language
Element name |
Language |
DCMI definition |
A language of the intellectual content of the resource. |
Usage |
Recommended |
User instruction |
A specific resource (an instance of scientific output) is either written in one human readable 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 readable language and is translated into other human readable languages, these translations are distinguished from the original version and therefore described separately. |
Do not confuse with |
- |
Refinements |
- |
Examples |
<dc:language>en</dc:language> |
Scheme |
ISO 639-1 and ISO 639-2, see: http://www.loc.gov/standards/iso639-2/englangn.html |
Relation
Element name |
Relation |
DCMI definition |
The reference to a related resource. |
Usage |
Recommended |
User instruction |
Recommended best practice is to reference the resource by means of a string or number conforming to a formal identification system.
|
Do not confuse with |
dc:identifier and dc:source. |
Refinements |
Isversionof (recommended) [DCMI:] The described resource is a version, edition, or adaptation of the referenced resource. Changes in version imply substantive changes in content rather than differences in format. |
Example |
<dc:relation:haspreviousversion>uri</dc:relation:haspreviousversion> |
Scheme |
- |
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 |
User 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. |
Do not confuse with |
- |
Refinements |
Spatial (Optional) [DCMI:] Spatial characteristics of the intellectual content of the resource. |
Examples |
Example Spatial - ISO 3166 |
Scheme |
Point http://dublincore.org/documents/dcmi-point/ |
Rights
Element name |
Rights |
DCMI definition |
Information about rights held in and over the resource. |
Usage |
Mandatory |
User 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. |
Do not confuse with |
- |
Refinements |
Access rights (Mandatory if formulated) [DCMI:] Information about who can access the resource or an indication of its security status. |
Examples |
<dc:rights>(c) University of Bath, 2003</dc:rights> |
Scheme |
- |
Additional fields (in accordance with DCMI)
Audience
Element name |
Audience |
DCMI definition |
A class of entity for whom the resource is intended or useful. |
Usage |
Optional |
User instruction |
A class of entity may be determined by the creator or the publisher or by a third party. |
Do not confuse with |
- |
Refinements |
Mediator (Optional) [DCMI:] A class of entity that mediates access to the resource and for whom the resource is intended or useful. |
Examples |
<dc: audience>Researchers</dc: audience> |
Scheme |
- |