The following outline summarises the basic DRIVER settings for the basic topics textual resources, metadata usage and OAI-PMH protocol implementation. The elaborated details can be found in the following chapters.

PART A - Textual Resources

mandatory

• The repository contains digital textual resources (see explanation "What do you mean with textual resources?" on page )
• Textual resources have popular and widely-used formats (PDF, TXT, RTF, DOC, TeX etc.)
• Textual resources are open access, available directly from the repository for any user worldwide without restrictions such as authorisation or payment
• Textual resources are described by metadata records
• Metadata plus textual resource are linked together in such a way that an end user can access the textual resource through an identifier (usually a URL) in the metadata record
• The URL of a resource once encoded in the metadata record is permanently addressable and is never changed or re-assigned
• A unique identifier identifies the metadata record and the textual resource (no pointers to external systems such as a national library system or a publisher)

recommended

• Transparent verification of the integrity of a textual resource
• Quality (of the scientific content) assurance measures for the textual resources exposed such as a limitation to those textual resources included in the yearly scientific report (or equivalent)
• The URL of the textual resource as encoded in the metadata record is based on a persistent identifier scheme such as DOIs, URNs, ARKs
• The use of the DIDL XML-container for exposing textual resources (chapter "Use of MPEG-21 DIDL (xml-container) - Compound object wrapping")

PART B - Metadata

mandatory

• Metadata are structured as Unqualified Dublin Core (ISO 15836:2003)
• Individual elements of DC are to be used according to the chapter "Use of Metadata OAI_DC" page

recommended

• Preferably use Metadata that is structured according to more comprehensive schemes such as Qualified Dublin Core or MODS. (Guidelines for these comprehensive schemas will follow in the future version of the DRIVER Guidelines. Preview of the MODS guidelines https://www.surfgroepen.nl/sites/oai/metadata/Shared%20Documents/Use%20of%20MODS%20for%20institutional%20repositories-version%201.doc )
• Recommended language is English
• Recommended language for an abstract (including an abstract is optional) of the article is English

PART C - OAI-PMH Implementation

mandatory

• The repository must be OAI-2.0 compliant and must conform to the specification on chapter "Use of OAI-PMH" page
• Existence of a repository identifier and use of the OAI identifier scheme
• If (and only if) the repository contains resources other than those which are mandatory in "PART A - Textual Resources", an OAI-set is defined as that which identifies the collection of digital textual resources accessible in Open Access (see explanations "DRIVER Set naming", "DRIVER Set Content definitions" and "Set Location" pages -)

recommended

• Provisions for the change of Base-URL
• Completeness of Identify Response, including use of the optional Description statement
• Use persistent or Transient deleting strategy
• Use a batch size with corresponding resumption token expiration time.