...
Document history
Version | Remarks |
|
|
|
|
August 2003 | First internal version presented to project manangers |
|
September 2003 | Second internal version presented to project managers |
|
1.0 (October 2003) | First edition to be used starting from November 1 2003 | Download PDF |
2.0 (December 2004) | Second edition to be used starting from December 1 2004 | |
Addendum (July 2006) | Addendum on v2.0 |
| Wiki Markup |
|---|
\\ \\ \\ *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.rdn.ac.uk/projects/epri<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="45dbc34d6d829032-e01422c7-49b34427-8d5cb18f-c5b9ceffeeef60e68ee0f602"><ac:parameter ac:name="">_Hlt53475187</ac:parameter></ac:structured-macro><ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="26e849255319ac02-9b6ee203-49bb4160-a771be8d-a5b91f822629deb8d7b4937e"><ac:parameter ac:name="">_Hlt53475188</ac:parameter></ac:structured-macro>nts\-<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="2f2fc52434d26113-099dabae-46124c4d-b8d5b296-f336f9bc8d9596a070c8cbbf"><ac:parameter ac:name="">_Hlt52270635</ac:parameter></ac:structured-macro><ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="2efff83c1457f861-71b42c72-4f56440e-addcba45-1529bf5a1bab1cf7535e552e"><ac:parameter ac:name="">_Hlt52270636</ac:parameter></ac:structured-macro>uk/docs/simpledc-guidelines/|http://www.rdn.ac.uk/projects/eprints-uk/docs/simpledc-guidelines/] \] \\ *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. \\ \\ |
...
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 | - | ||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="4ede007c6b9dc4a2-5e46776c-464840b2-ab88a313-65c88e010ca5a2100ab7a370"><ac:plain-text-body><![CDATA[ | 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. | ]]></ac:plain-text-body></ac:structured-macro> |
Examples | Qualified DC | ||
Scheme | Not applicable |
...
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 | - | ||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="b0279587f4fb5f12-84f9ea74-45d845fa-a0279ab1-44a20cb663a0df284ab3c627"><ac:plain-text-body><![CDATA[ | Refinements | Tableofcontent (recommended) [DCMI:] A list of subunits of the content of the resource. | ]]></ac:plain-text-body></ac:structured-macro> |
Examples | <dc:description>Inleiding; 5 hoofdstukken over geschiedenis; 2 hoofdstukken met praktische tips; index</dc:description> | ||
Scheme | Not applicable |
...
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="49784d14e7b87679-530c4368-48fc4f59-bbd2a3da-171ebb8e1feb4a717e2c9dd9"><ac:plain-text-body><![CDATA[ | 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 |
...
Element name | Date | ||||||||||||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="a3d7612c17354c2a-a491ccf4-44104463-846788a9-21014c07aa2c0daa8b87d618"><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 | ||||||||||||
User instruction | The date should be formatted according to the W3C encoding ru
Complete date: YYYY-MM-DD (eg 1997-07-16) where: <ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="5d607a566d987933-984c5ebc-4db14857-980dbffd-dda2b85d059e8e135824a9d4"><ac:plain-text-body><![CDATA[YYYY [four-digit year] is mandatory ]]></ac:plain-text-body></ac:structured-macro> <ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="00cf7e133135550d-842bf93b-4a064782-af47b77b-ab9ac2f35eb32261f92d7cf7"><ac:plain-text-body><![CDATA[MM [two-digit month (01=January, etc.)] is optional ]]></ac:plain-text-body></ac:structured-macro> <ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="9ec5a469028d496b-29214fff-4c3e4936-a50e933e-79d1759c78db53e270338855"><ac:plain-text-body><![CDATA[DD [two-digit day of month (01 through 31)] is optional ]]></ac:plain-text-body></ac:structured-macro> In the DC element 'date' the most notable differences occur between acting as a data provider based on basic DC unqualified and DC qualified. Where values in other DC elements could - within reason - be interpreted by the user, the values in the date element are excactly similar and context (provided by the DC refinements) is necessary to interpret the values. Based on these observations the following is stated. <ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="bf4d962b2293a7e5-7c250eff-411449d3-baec91be-5b311a9b319d3e313dee8548"><ac:plain-text-body><![CDATA[Basic DC unqualified: use the DC element 'date' for the value [of the refinement]: 'date created'. ]]></ac:plain-text-body></ac:structured-macro> DC qualified: Use of all refinements is permitted / optional, depending of and according to the level of distinction the data provider can make and is willing to offer in harvesting. | ||||||||||||
Do not confuse with | - | ||||||||||||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="c16383200864b738-429d365a-421f4fed-be46828b-53828aed44b648b2258f80ba"><ac:plain-text-body><![CDATA[ | Refinements | DateAccepted (Optional) [DCMI:] Date of acceptance of the resource (e.g. of thesis by university department, of article by journal, etc.). | ]]></ac:plain-text-body></ac:structured-macro> | ||||||||||
Examples | <dc:date>2000-12-25</dc:date> | ||||||||||||
Schema | Date | ISO 8601 W3C-DTF see: http://www.w3.org/TR/NOTE-datetime |
...
Element name | Format | ||||||||||||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="e96c3155e53b6651-1741bced-4ec4481f-9521b45e-b7113a4f5ecd985abc75dd5f"><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 | ||||||||||||
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.
TypeSubtype ----------- textplain richtext enriched tab-separated-values html sgml xml applicationoctet-stream postscript rtf applefile mac-binhex40 wordperfect5.1 zip macwriteii msword sgml ms-excel ms-powerpoint ms-project ms-works imagejpeg gif tiff png jpeg2000 sid audiowav mp3 video quicktime mpeg1 mpeg2 mpeg3 avi | ||||||||||||
Do not confuse with | Type | ||||||||||||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="007404734bef7e15-5dccd657-47a24092-b7b98710-83e5e67c4d45067c43625c4f"><ac:plain-text-body><![CDATA[ | Refinements | Extent (Optional) [DCMI:] The size or duration of the resource. E.g. number of pages of an article. | ]]></ac:plain-text-body></ac:structured-macro> | ||||||||||
Examples | <dc:format>application/pdf</dc:format> | ||||||||||||
Scheme | the IANA registered list of Internet Media Types (MIME types) |
...
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 | ||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="f8d0a13fdfbeffc3-27ce313a-465740d6-844f956c-05b40a63e3dca1089bd01577"><ac:plain-text-body><![CDATA[ | Refinements | Bibl. Citation (Optional) [DCMI:] A bibliographic reference for the resource. | ]]></ac:plain-text-body></ac:structured-macro> |
Example | <dc:source>Ecology Letters (1461023X) vol.4 (2001)</dc:source> | ||
Scheme | ISSN, ISBN |
...
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. | ]]></ac:plain-text-body></ac:structured-macro> |
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 |
...
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. | ||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="c491f3a58906039f-becc7c6a-469d49c5-b55c870a-af9acc1edbc1e61154dd6efd"><ac:plain-text-body><![CDATA[ | 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. | ]]></ac:plain-text-body></ac:structured-macro> |
Example | <dc:relation:haspreviousversion>uri</dc:relation:haspreviousversion> | ||
Scheme | - |
...
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 Na
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="cbd3937cf90d0e1b-f16c8a01-4a614365-a32faad6-f13892093215c8047f59d531"><ac:plain-text-body><![CDATA[ | Refinements | Spatial (Optional) [DCMI:] Spatial characteristics of the intellectual content of the resource. | ]]></ac:plain-text-body></ac:structured-macro> | ||||
Examples | Example Spatial - ISO 3166 | ||||||
Scheme | Point http:/ dublincore.org/documents/dcmi-point/ |
...
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 | - | |||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="9a2581bb65a29a74-0394bba7-40c6422f-b4b89c99-89dcd14c55086f82c9a59624"><ac:plain-text-body><![CDATA[ | Refinements | Access rights (Mandatory if formulated) [DCMI:] Information about who can access the resource or an indication of its security status. | http://creativecommons.org/licenses/]. | ]]></ac:plain-text-body></ac:structured-macro> |
Examples | <dc:rights>(c) University of Bath, 2003</dc:rights> | |||
Scheme | - |
...
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 | - | ||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="b5134ba760c9b972-128eeb3b-400e40fa-a2f1af6b-0cf70aa05bcb7a66c2643ec4"><ac:plain-text-body><![CDATA[ | Refinements | Mediator (Optional) [DCMI:] A class of entity that mediates access to the resource and for whom the resource is intended or useful. | ]]></ac:plain-text-body></ac:structured-macro> |
Examples | <dc: audience>Researchers</dc: audience> | ||
Scheme | - |
...