Index

What DRIVER is DRIVER, the "Digital Repository Infrastructure Vision for European Research" project is conducted by an EC funded consortium that is building an organisational and technological framework for a panEuropean datalayer, enabling the advanced use of contentresources in research and higher education. DRIVER ...

Why use the DRIVER Guidelines? The "DRIVER Guidelines for Content Providers: Exposing textual resources with OAIPMH" will provide orientation for managers of new repositories to define their local datamanagement policies, for managers of existing repositories to take steps towards improved services and for developers ...

Acknowledgements & Contributors (version 1.0) Martin Feijen (SURFfoundation, NL) Maurice Vanderfeesten (SURFfoundation, NL) Wolfram Horstmann (University of Goettingen, DE) Friedrich Summann (University of Bielefeld, DE) Muriel Foulonneau (CNRS, FR) Karen Van Godtsenhoven (University ...

See: http://www.openarchives.org/OAI/openarchivesprotocol.html#Identify http://www.openarchives.org/OAI/openarchivesprotocol.html#Identify The repository must provide an administrator email address in the Identify request. In the near future we want the harvester to give immediate response to the Repository Administrator ...

section addresses an important issue on Usage Rights and Deposit Rights. In practice this must be implemented. The DRIVER Guidelines should say something on how Usage Rights should be exposed and formatted in metadata. The basis of this section will be the Copyright Toolbox developed by SURFfoundation ...

Persistent Identifiers for web resources are needed to create a stable and reliable infrastructure. This does not concern technicalities, but mainly agreements on organisational level. DRIVER Guidelines could make some recommendations on the implementation for repository managers. This is based on the Report on Persistent Identifiers of the PILIN ...

DRIVER Guidelines 2.0 provides basic information on the importance of Quality, and Interoperability. Quality labels can be used to assure Stable and reliable repositories that last longer than the hype, and have also an archival purpose for Long Term Preservation. Examples ...

section will not appear in the DRIVER Guidelines 2.0 Final release. The input for this section will be make from the experiences and best practices that comes from the two European projects who harvest Statistic reports from repositories to present statistics on an aggregated level ...

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

information is cited and modified from the European NEEO project. Network of European Economists Online (NEEO): project information see http://www.nereus4economics.info/neeo.html http://www.nereus4economics.info/neeo.html. For the DAI information see specifications: http://homepages.ulb.ac.be/bpauwels/NEEO/WP5/WP5%20Technical ...

DIDL XML container was originally developed within the DARE program of SURF as a first implementation of MPEG21 DIDL. The rationale behind this development was: A solution for resource harvesting via OAIPMH for transport of the digital resources (PDF's etc) from the local repository to the National ...

What researchers expect Researchers and other users of digital information systems have high expectations for provision of digital content. Retrieval should be fast, direct (within a few clicks) and versatile. The current culture in the landscape of digital repositories does not fully ...

Modification to baseURL, setSpec, metadataPrefix, or metadata schema's When a DRIVER repository modifies either the baseURL, setSpec, metadataPrefix or metadata schemas which influence the DRIVER content cycle, then the concerning repository administrator must report this to the DRIVER community and the DRIVER harvester ...

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

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

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

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

According to the protocol, each record contains a header with a datestamp with "the date of creation, modification or deletion of the record for the purpose of selective harvesting." The protocol also explains the selective harvesting as follows: "..{}modification the response must include records, corresponding to the metadataPrefix argument, which ...

See: http://www.openarchives.org/OAI/openarchivesprotocol.html#Datestamp http://www.openarchives.org/OAI/openarchivesprotocol.html#Datestamp , http://www.openarchives.org/OAI/openarchivesprotocol.html#Dates http://www.openarchives.org/OAI/openarchivesprotocol.html#Dates and http://www.w3.org/TR/NOTEdatetime http://www.w3.org/TR/NOTEdatetime The value ...

DC:RELATION field can typically be used for describing relations to other expressions, or versions of the document. For example the Published version of an article and the author version of an article. These can be referred to each other by using the "most appropriate" identifier that is actionable ...

publications use the DC:SOURCE field for inserting information a person can use to appropriately make a citation of the record he/she has found. Preferably use the APA style of writing references. For example <dc:source>Ecology Letters (1461023X ...

Item and Record It is important to make a distinction between Item and Record. The protocol text states: "...An item is conceptually a container that stores or dynamically generates metadata about a single resource in multiple formats, each of which can be harvested as records via ...

See: http://www.openarchives.org/OAI/openarchivesprotocol.html#DeletedRecords http://www.openarchives.org/OAI/openarchivesprotocol.html#DeletedRecords If a record is no longer available then it is said to be deleted. Repositories must declare one of three levels of support for deleted records in the deletedRecord element of the Identify response: no \ the repository ...

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 freetext account of the content. Usage Mandatory if applicable Usage instruction This element ...

description container of the Identify response may be used to deliver additional information on the repository. Service providers may look for this and improve their data processing and the services based on the metadata and their quality. Best practice: Use this container to describe as many common information about ...

DIDL XML container, as defined in DRIVER, is a document with one toplevel Item element. The Item contains several child Item elements. These child item elements appear in three different kind of types. Between the straight brackets the cardinality of the XML elements ...

driverIIlogo.jpg thumbnail, align=centre!\\ Digital Repository Infrastructure Vision for European Research DRIVER Guidelines 2.0 Guidelines for content providers Exposing textual resources with OAIPMH !worddav42d6ff743ceebbd07247c0f3727fe27b.png align=center!\\ ccby wordle.net \November 2008\ Guidelines for Repository Managers ...

specific content of the 'driver' set is determined at the local repository. A DRIVER repository using this kind of sets must conform to the following rules when inserting a record into the DRIVER set: The DRIVER set contains records that must contain open access digital ...

See: http://www.openarchives.org/OAI/openarchivesprotocol.html#Set The OAIPMH document states: Repositories may organize items into sets. Set organization may be flat, i.e. a simple list, or hierarchical. The DRIVER agreement is that hybrid DRIVER repositories that contain metadataonly and metadatawithfulltext ...

Mapping of other Publication type lists with the one made available in the section Publication type DRIVERguidelines:Publication type vocabulary page in chapter "Use of Vocabularies and Semantics". In that section one can find details definitions of the terms used in that vocabulary in order ...

Below are the mappings of the DRIVER versioning scheme compared to other versioning schemes In the library and repository world. More about DRIVER versions in the section Version on page in chapter "Use of Vocabularies and Semantics". Eprints Version types to DRIVER Guidelines v2.0 VERSION ...

DRIVER Guidelines use the following encoding schemes: {}Name{} {}Field{} {}Scheme{} Author dc:creator APA bibliographic writing style as in a reference list. Syntax: surname, initials (first name) \http://en.wikipedia.org/wiki/Apastyle#Referencelist http://en.wikipedia.org ...

xml version="1.0" encoding="UTF8"?> <?xmlstylesheet type="text/xsl" href="DIDLdocumentHTML.xsl"?> <OAIPMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchemainstance" xsi:schemaLocation=" http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAIPMH.xsd"> <responseDate ...

Element name Format DCMI definition The physical or digital manifestation of the resource. Typically, Format may include the mediatype 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 ...

batch size is the number of records a repository delivers to the harvester for one resumption token and determines how many request processes have to be executed. The agreement is that DRIVER repositories must set the batch size between 100 and 500 records. Using this batch ...

Introduction This is the home of the DRIVER guidelines wiki space. Additional information and translations of the Guidelines are available from the DRIVER website http://www.driversupport.eu/managers/html. DRIVER stands for Digital Repository Infrastructure Vision for European Research. The guidelines have been created ...

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

First of all we would like to say that the persistency of Identifiers and web resources is not about the technology one uses, but about organisation and sustainable business models. For more information about Persistent Identifier policies take a look at the successful Persistent Identifier ...

namespace info:eurepo is registered at http://infouri.info http://infouri.info/registry/OAIHandler?verb=GetRecord&metadataPrefix=reg&identifier=info:eurepo/ This name space is an authoritive placeholder for semantic terms, controlled vocabularies and identifiers. By using this namespace all the terms used ...

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

See: http://www.openarchives.org/OAI/openarchivesprotocol.html#MetadataNamespaces http://www.openarchives.org/OAI/openarchivesprotocol.html#MetadataNamespaces OAIPMH supports the dissemination of records in multiple metadata formats from a repository. The ListMetadataFormats request returns the list of all metadata formats. metadataPrefix arguments are used ...

ease of access experienced with Open Access publications lacking any need for authentication, financial transactions or personal identification makes it much easier to achieve a satisfying level of reception in a scientific community. This and similar hypotheses can be investigated by empirical analysis. # What ...

DIDL document is part of an OAIPMH response. The DIDL document will be returned within an OAIrecord when using didl as value of the metadataPrefix verb. This enables the repository to generate this particular DIDL format that is described in the document below. Within the OAI XML ...

following outline summarises the basic DRIVER settings for the basic topics textual resources, metadata usage and OAIPMH protocol implementation. The elaborated details can be found in the following chapters. \\ \\ \\ PART A \ Textual Resources mandatory The repository contains digital textual resources ...

aim of this project is to develop COUNTERcompliant usage reports at the individual article level that can be implemented by any entity (publisher, aggregator, IR, etc.,) that hosts online journal articles and will enable the usage of research outputs to be recorded, reported and consolidated at a global level ...

See: http://www.openarchives.org/OAI/openarchivesprotocol.html#Record http://www.openarchives.org/OAI/openarchivesprotocol.html#Record namespace declarations the declarations of the namespaces used within the metadata part, each of which is prefixed with xmlns. Namespace declarations within the metadata part fall into two ...

Goals of OAStatistics We aim to produce valid and reliable document usage statistics based solely on information gathered from the HTTP layer. There are two main issues addressed by all existing standards which generate the bulk of the necessary corrections: Identification ...

div style="width:425px;textalign:left" id="ss2236829"><a style="font:14px Helvetica,Arial,Sansserif;display:block;margin:12px 0 3px 0;textdecoration:underline;" href="http://www.slideshare.net/maurice.vanderfeesten/20091020ghentdriverguidelinesandvalidatorbymauricevanderfeesten" title="2009 ...

Publication type vocabulary listed below has a deep history from within the European repository community. It is a combination of the types DARE uses from DC guidelines, types listed in the DINI certificate and the ePrints publication types Vocabulary of the Eprints Application ...

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 Usage instruction ...

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

See: http://www.openarchives.org/OAI/openarchivesprotocol.html#Idempotency http://www.openarchives.org/OAI/openarchivesprotocol.html#Idempotency Repositories that implement resumptionTokens must do so in a manner that allows harvesters to resume a sequence of requests for incomplete lists by reissuing a list request with the most recent ...

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

DRIVER set and the other sets can be located at a different locations/baseURLs

http://dublincore.org/documents/dccitationguidelines/ 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 ...

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

Metadata delivered via OAIPMH contain a broad range of subject headings and classification information. The used classification and subject heading systems and the presentation formats vary broadly. In most cases this information appears in simple dc format in the subject element. Classification ...

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 http://dublincore.org/documents/usageguide/elements.shtml

Within DRIVER the use of elements is either: mandatory (M) = the element must always be present in the metadata record. An empty element is not allowed. mandatory when applicable (MA) = when the element can be obtained it must be present in the metadata record recommended ...

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

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

chapter deals with common problems that repository administrators come across when installing a repository. These practices are not mandatory, but form the best possible solution to common problems. These solutions come from best practices from other repository administrators who already ...

chapter describes the way DRIVER envisions interoperability for scholarly communication. This means qualitative correct metadata of the records based on the use of standards. Acknowledgements This document is largely based on the recommendations for the use of Unqualified (simple) Dublin Core metadata as described in: USING SIMPLE ...

Introduction and Goal This document is an addition to the existing DIDL specification document for repositories which is being used by the Dutch Universities, Koninklijke Bibliotheek, National Library of The Netherlands, and NARCIS. The goal of this document is to make the use of DIDL unambiguously clear by describing: # the nature ...

Introduction This chapter explains how to use OAIPMH in a way so that repositories and service providers can seamlessly work together by creating interoperability on a protocol level. Remark: The examples used for DIDL; do NOT use them literally\! For the precise use of the DIDL ...

recommendation is based on the study report " {}A PORTAL FOR DOCTORAL ETHESES IN EUROPE; Lessons Learned from a Demonstrator Project{} http://igiturarchive.library.uu.nl/DARLIN/20070803222337/ETDLessonsLearnedFullReport%2bAnnex.pdf" This study is aiming at generic scholarly communication services harvesting OAIDC. For context specific etheses services we ...

section is about the versions that describe the status of the document. We have introduced version information to make it possible to describe the Publication type without mixing the terms with version or status information. For example, the term "PeerReviewedArticle" can be split into info:eu repo ...

section provides information about what has changed compared to the DRIVER guidelines v1.0. The reason to change several parts wat becouse of the questions that came it. Most of the changes are enhancements and improved explanations rather then real fundamental changes

See: Use of Intellectual Property Rights Annex Use of Intellectual Property Rights (IPR) (IPR) page for a starting document. This addresses an important issue on Usage Rights and Deposit Rights. In practice this must be implemented. The DRIVER Guidelines should tell ...

See Annex: Use of Persistent Identifiers DRIVERguidelines:Annex Use of Persistent Identifiers page for a starting document. Persistent Identifiers for web resources are needed to create a stable and reliable infrastructure. This does not concern technicalities, but mainly agreements on an organisational level ...

See Annex: Use of Quality Labels DRIVERguidelines:Annex Use of Quality Labels page for a starting document. The DRIVER Guidelines 2.0 provides basic information on the importance of Quality, and Interoperability. Quality labels can be used to assure stable and reliable repositories ...

See Annex: Use of Usage Statistics Exchange DRIVERguidelines:Annex Use of Usage Statistics Exchangepage for a starting document. In order to see the value of Open Access and offer extra services to your authors, repositories should think about aggregating usage ...

DRIVERTYPEMappings Explanation: how to map \x\ Local categories to \y\ DRIVER categories. See: DRIVERTYPE Mappings DRIVERguidelines:DRIVERTYPE Mappings page. DRIVERVERSION Mappings Explanation: how to use the different status/versions of Publication and to map \x\ Local categories ...

Several major important changes have been made Wrong DIDL schema location, validation not possible Modify reference of info:eurepo namespace Modifications are also put in the example Changes to meet future transport of Author Identifiers Add namespace ...

Identifier How to handle other identifiers that are in the repository. Are OAI identifiers allowed? Where should the identifier point to? How should they be exposed? Explanation The Identification of a resource has been broadened. The repository can use any identifier that is necessary to identify the resource ...

DRIVER Set naming Added information to answer questions about "Recommended Set names for "Open Access" and "Embargoed/Delayed Access" subcollections \ See DRIVER Set naming DRIVERguidelines:DRIVER Set naming page. Explanation: Recommended for hybrid repositories ...

Two vocabularies have been made to deambiguify the concepts and terms used in scholarly communication in Europe. Several more issues therefore have been solved: Document type : Preprint and Postprint versioning Document type: What is the difference between "external ...

XML that the repository provides will be validated automatically during the DRIVER repository registration process and the DRIVER harvesting process. A DRIVER repository must provide a valid XML according to all XML schemas used (OAIPMH, DIDL, oaidc etc) Validation can ...