Document History

Date	Version	Owner	Changelog	PDF
July 2006	Addendum	DARE	Addendum on v2.0	Download
December 2004	2.0	DARE	Second edition to be used starting from December 1 2004	Download
October 2003	1.0	DARE	First edition to be used starting from November 1 2003	Download
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

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

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

Creator

Subject

Description

Publisher

Contributor

Date

Type

Format

Identifier

Example of a Dublin Core Description of a Journal Article: dare_qdc

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

Language

Relation

Coverage

Rights

Additional fields (in accordance with DCMI)

Audience