|
||
DRIVER Guidelines 2.0 |
||
Guidelines for content providers - Exposing textual resources with OAI-PMH |
||
|
||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="261f13c2-2c02-4ea7-93ad-dda4f333a75d"><ac:plain-text-body><![CDATA[ |
[November 2008] |
]]></ac:plain-text-body></ac:structured-macro> |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="24d94e50-a63d-46df-9801-ccc401bfcafc"><ac:plain-text-body><![CDATA[ |
[Guidelines for Repository Managers and Administrators on how to expose digital scientific resources using OAI-PMH and Dublin Core Metadata, creating interoperability by homogenising the repository output. ] |
]]></ac:plain-text-body></ac:structured-macro> |
cc-by wordle.net
Abstract
For communication in general it is important that person B is able to understand what person A is saying. For this common understanding one needs a common ground, a basic lexicon with an awareness of the meaning of things. From this point on one can start reasoning. In order to support scholarly communication with the use of repositories, repositories should speak the same language and it is therefore essentialto create a common ground.
In technical terms we create a common ground by conducting "interoperability". Interoperability can be managed at different layers. In the DRIVER Guidelines we basically try to reach interoperability on two layers, syntactical (Use of OAI-PMH & Use of OAI_DC) and semantic (Use of Vocabularies).
Table of Contents
Introduction
Acknowledgements & Contributors (version 1.0)
Acknowledgements & Contributors (version 2.0)
Editors
Experts & Reviewers
About DRIVER
What DRIVER is
DRIVER as data-infrastructure
The current DRIVER information space
Challenges
What researchers expect
The full-text challenge
What's next?
About the DRIVER Guidelines
Why use the DRIVER Guidelines?
How to comply with the DRIVER Guidelines? (validation)
What if I don't comply?
Is there support?
Scope of the DRIVER Guidelines
Further Resources
Outline - DRIVER Guidelines Summary
PART A - Textual Resources
PART B - Metadata
PART C - OAI-PMH Implementation
What's New
Chapter 1: Use of OAI-PMH
DRIVER Set naming
Harvest batch size
Resumption token lifespan
Deleted records strategy
Chapter 2: Use of Metadata OAI_DC
Identifier
Date
Rights
Language
Creator
Source
Type
Format
Chapter 3: Use of Best Practices for OAI_DC
DRIVER-TYPEMappings
DRIVER-VERSION Mappings
Use of OAI_DC with Theses
DC:SOURCE and DC:RELATION
Chapter 4: Use of Compound Object Wrapping
Chapter 5: Use of Vocabularies and Semantics
Chapter 6: Annex: Use of Quality labels
Chapter 7: Annex: Use of Persistent Identifiers
Chapter 8: Annex: Use of Usage Statistics Exchange
Chapter 9: Annex: Use of Intellectual Property Rights (IPR)
Use of OAI-PMH
Introduction
Remark:
Acknowledgements
Source material
Definitions and concepts: item, record and unique identifier
Item and Record
Identifier
MetadataPrefix naming
DIDL document
Datestamp
Datestamp syntax
Deleted records
Resumption token
Harvest batch size
DRIVER Set naming
DRIVER Set Content definitions
Set Location
adminEmail for error logging feedback
Prefix & namespace declaration
XML validation
Communication for Repository modification
Use of Metadata OAI_DC
Acknowledgements
Definitions
Introductory remarks
Scope
Minimal requirements
Recommendations
The Elements: short description
Unqualified DC: oai_dc
The Elements: full description
Title
Creator
Subject
Description
Publisher
Contributor
Date
Type
Format
Identifier
Source
Language
Relation
Coverage
Rights
Audience
Use of Best Practices for OAI_DC
DRIVER-TYPE Mappings
DRIVER v1.1 types to DRIVER v2.0 types
E-Print type vocabulary to DRIVER v2.0 types
DRIVER-VERSION Mappings
Eprints Version types to DRIVER Guidelines v2.0 VERSION types
Common version terms to DRIVER Guidelines v2.0 VERSION types
Journal Article Versions (JAV) Technical Working Group versions to DRIVER Guidelines v2.0 VERSION types
Use of OAI_DC with Theses
Example
DC:SOURCE and Citation information
DC:RELATION and Linking related objects
Use of MPEG-21 DIDL (xml-container) - Compound object wrapping
Introduction and Goal
Background information
OAI Response with a DIDL document
DIDL as wrapper
Root Element: DIDL document Identification attribute
Item Descriptor Elements (optional)
Descriptor Statement: Item 'Identifier'
Descriptor Statement: Item 'modified'
Descriptor Statement: Item 'ObjectType'
Compound Element: representation of the complex work
ObjectType: Metadata Item
ObjectType: Object Item
ObjectType: Jump-off-page Item
Example of a DIDL embedded in OAI-PMH
Use of Vocabularies and Semantics
info:eu-repo - A namespace for URI-fying un-URIfied Schema's and Identifiers
Author Identification
Format of a DAI
Persistence of a DAI
Subject classification
Publication type vocabulary
Version vocabulary
Encoding schemes
Annexes: Future Points of Interest
Annex: Use of Quality Labels
Annex: Use of Persistent Identifiers
Implementation plan on using URN:NBN Persistent Identifiers
Annex: Use of Usage Statistics Exchange
PIRUS: Publisher and Institutional Repository Usage Statistics
OA-Statistik
Preliminary results of the project OA-Statistik
Goals of OA-Statistics
Information needed to generate COUNTER, LogEc and IFABC
Additional pieces of information which comply with OpenURL Context Objects
Additional suggestions
Table of Web Usage Standards
Use of Intellectual Property Rights (IPR)