Child pages
  • Outline - DRIVER Guidelines Summary

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

Anchor
_Toc213761386
_Toc213761386
Anchor
_Toc213761548
_Toc213761548
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.


Anchor
_Toc213761387
_Toc213761387
Anchor
_Toc213761549
_Toc213761549
Anchor
_Ref214091796
_Ref214091796
Anchor
_Toc214332831
_Toc214332831
PART A
Anchor
_Toc213761388
_Toc213761388
Anchor
_Toc213761550
_Toc213761550
- Textual Resources

Anchor
_Toc213761551
_Toc213761551
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)

Anchor
_Toc213761552
_Toc213761552
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")

Anchor
_Toc213761389
_Toc213761389
Anchor
_Toc213761553
_Toc213761553
Anchor
_Toc214332832
_Toc214332832
PART B
Anchor
_Toc213761390
_Toc213761390
Anchor
_Toc213761554
_Toc213761554
- Metadata

Anchor
_Toc213761555
_Toc213761555
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

Anchor
_Toc213761556
_Toc213761556
recommended

Anchor
_Toc213761391
_Toc213761391
Anchor
_Toc213761557
_Toc213761557
Anchor
_Toc214332833
_Toc214332833
PART C
Anchor
_Toc213761392
_Toc213761392
Anchor
_Toc213761558
_Toc213761558
- OAI-PMH Implementation

Anchor
_Toc213761559
_Toc213761559
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 -)

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