Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

OAI 2.0 could also work using the database for querying. To configure that one must change the [dspace]/config/modules/xoai.cfg file, specifically the "storage" parameter, setting it to "database". This decreases performance significantly and likely has no other benefits than leaving out Solr as a dependency.

...

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 see the English version of the document here)

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

What specific metadata values are expected?

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

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

...

The name of the set in OAI-PMH is “ec"ec_fundedresources” fundedresources" and will expose the items of the repository that comply with these guidelines. These guidelines are based on top of DRIVER guidelines. The  See version 2.0 of the Guidelines are available here.

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 rights with the access rights information from vocabulary (possible values here)

...

  • dc:date with the embargo end date (Recommended recommended for embargoed items)
Code Block
languagehtml/xml
linenumberstrue
<dc:date> infodate>info:eu-repo/date/embargoEnd/2011-05-12<dc:date>

...

  • Have a dc:relation field in input-forms.xml to with a list of the projects. You can also use the OpenAIRE Authority Control Addon to facilitate the search process of finding 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 an input-box for dc:date to insert the embargo end date

...