Date: Thu, 28 Mar 2024 15:30:26 +0100 (CET)
Message-ID: <1650963694.7583.1711636226927@wiki01p.surfnet.nl>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_7582_215733955.1711636226927"
------=_Part_7582_215733955.1711636226927
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
Outline - DRIVER Guidelines Summary
Outline - DRIVER Guidelines Summary
The following outl=
ine summarises the basic DRIVER settings for the basic topics textual resou=
rces, metadata usage and OAI-PMH protocol implementation. The elaborated de=
tails can be found in the following chapters.
PART A - Textual =
Resources
mandatory
- The repository contains digital textual resources (see explanation "Wha=
t 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 reposito=
ry for any user worldwide without restrictions such as authorisation or pay=
ment
- Textual resources are described by metadata records
- Metadata plus textual resource are linked together in such a way that a=
n 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 permanentl=
y addressable and is never changed or re-assigned
- A unique identifier identifies the metadata record and the textual reso=
urce (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 ba=
sed on a persistent identifier scheme such as DOIs, URNs, ARKs
- The use of the DIDL XML-container for exposing textual resources (chapt=
er "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 OA=
I_DC" page
recommended
PART C - OAI-PMH Implementation
mandatory
- The repository must be OAI-2.0 compliant and must conform to the specif=
ication on chapter "Us=
e of OAI-PMH" page
- Existence of a repository identifier and use of the OAI identifier sche=
me
- If (and only if) the repository contains resources other than those whi=
ch are mandatory in "PART A - Textual Resources", an OAI-set is defined as =
that which identifies the collection of digital textual resources accessibl=
e in Open Access (see explanations "DRIVER Set naming", "DRIVER Set Content definitions" and=
"Set Location" page=
s -)
recommended
- Provisions for the change of Base-URL
- Completeness of Identify Response, including use of the optional Descri=
ption statement
- Use persistent or Transient deleting strategy
- Use a batch size with corresponding resumption token expiration time.=
li>
------=_Part_7582_215733955.1711636226927--