Page History

...

NOTE: Changes in [dspace]/config/crosswalks/oai/xoai.xml requires reloading/restarting the servlet container.

Driver/OpenAIRE compliance

The default OAI 2.0 installation provides two new contexts. They are:

...

However, in order to be exposed DSpace items must be compliant with Driver/OpenAIRE guide-lines.

Driver Compliance

DRIVER Guidelines for Repository Managers and Administrators on how to expose digital scientific resources using OAI-PMH and Dublin Core Metadata, creating interoperability by homogenizing the repository output. The set driver of OAI-PMH is based on DRIVER Guidelines 2.0 (The english version of the document here)

This set is used to expose items of the repository that are in open access and it’s not necessary if all the items of the repository are in open access.

What specific metadata values are expected?

To have items on this set, you must configure your input-forms.xml file in order to comply with DRIVER Guidelines:

• Must have a publication date - dc.date.issued (already configured in DSpace items)
• dc.language must use ISO639-3
• dc.type must be one of the 16 options of the guidelines (see page 68)

...

How do you easily add those metadata values? 

As DRIVER guidelines use Dublin Core, all the needed items are already registered in DSpace. You just need to configure the deposit process.

OpenAIRE compliance

The OpenAIRE Guidelines 2.0 provide the OpenAIRE compatibility to repositories and aggregators. By implementing these Guidelines, repository managers are facilitating the authors who deposit their publications in the repository in complying with the EC Open Access requirements. For developers of repository platforms, the Guidelines provide guidance to add supportive functionalities for authors of EC-funded research in future versions.

...

See the Application Profile of OpenAIRE here. 

What specific metadata values are expected?

These are the OpenAIRE metadata values only, to check these and driver metadata values check page 11 of the OpenAIRE guidelines 2.0.

• dc:relation with relation with the project ID (see p.8)
• dc:rights with the access rights information from vocabulary (possible values here)

...

<dc:date> info:eu-repo/date/embargoEnd/2011-05-12<dc:date>

...

How do you easily add those metadata values?

...

• Have a dc:relation field in input-forms.xml to projects. You can also use the OpenAIRE Authority Control Addon to facilitate the search process of the project identification.
• Just use a combo-box for dc:rights to input the 4 options:
  
  • info:eu-repo/semantics/closedAccess
  • info:eu-repo/semantics/embargoedAccess
  • info:eu-repo/semantics/restrictedAccess
  • info:eu-repo/semantics/openAccess
• Use a input-box for dc:date to insert the embargo end date

...