Page History

...

OAI 2.0 is a separate webapp which is a complete substitute for the old "oai" webapp. OAI 2.0 has a configurable data source, by default it will not query the DSpace SQL database at the time of the OAI-PMH request. Instead, it keeps the required metadata in its Solr index (currently in a separate "oai" Solr core) and serves it from there. It's also possible to set OAI 2.0 to only use the database for querying purposes if necessary, but this decreases performance significantly. Furthermore, it the webapp caches the requests, so doing the same query repeatedly is very fast. In addition to that it also compiles DSpace items to make uncached responses much faster.

...

OAI 2.0 could also work using the database for querying. To configure that one must change the [dspace]/config/modules/xoaioai.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.

...

And at /openaire context it provides:

1. OAI_DC
2. METS

Configuration

Basic Configuration

Advanced Configuration

OAI 2.0 allows you to configure following advanced options:

• Contexts
• Transformers
• Metadata Formats
• Filters
• Sets

It's an XML file commonly located at: [dspace]/config/crosswalks/oai/xoai.xml

General options

These options influence the OAI interface globally. "per page" means per request, next page (if there is one) can be requested using resumptionToken provided in current page.

Encoding problems

There are two main potential sources of encoding problems:

a) The servlet connector port has to use the correct encoding. E.g. for Tomcat, this would be <Connector port="8080" ... URIEncoding="UTF-8" />, where the port attribute specifies port of the connector that DSpace is configured to access Solr on (this is usually 8080, 80 or in case of AJP 8009).

b) System locale of the dspace command line script that is used to do the oai import. Make sure the user account launching the script (usually from cron) has the correct locale set (e.g. en_US.UTF-8). Also make sure the locale is actually present on your system.

Configuration

Basic Configuration

Advanced Configuration

OAI 2.0 allows you to configure following advanced options:

• Contexts
• Transformers
• Metadata Formats
• Filters
• Sets

It's an XML file commonly located at: [dspace]/config/crosswalks/oai/xoai.xml

General options

These options influence the OAI interface globally. "per page" means per request, next page (if there is one) can be requested using resumptionToken provided in current page.

• identation [boolean] - whether the output XML should be indented to make it human-readable

• maxListIdentifiersSize [integer] - how many identifiers to show per page (verb=ListIdentifiers)

• maxListRecordsSize [integer] - how many records to show per page (verb=ListRecords)

• maxListSetsSize [integer] -

• identation [boolean] - whether the output XML should be indented to make it human-readable

• maxListIdentifiersSize [integer] - how many identifiers to show per page (verb=ListIdentifiers)

• maxListRecordsSize [integer] - how many records to show per page (verb=ListRecords)

• maxListSetsSize [integer] - how many sets to show per page (verb=ListSets)

• stylesheet [relative file path] - an xsl stylesheet used by client's web browser to transform the output XML into human-readable HTML

...

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

Add/Remove Metadata Fields

The internal DSpace fields (Dublin Core) are exposed in the internal XOAI format (xml). All other metadata formats exposed via OAI are mapped from this XOAI format using XSLT (xoai.xsl itself is just an identity transformation). These XSLT stylesheets are found in the [dspace]/config/crosswalks/oai/metadataFormats directory. So e.g. oai_dc.xsl is a transformation from the XOAI format to the oai_dc format (unqualified Dublin Core).

Therefore exposing any DSpace metadata field in any OAI format is just a matter of modifying the corresponding output format stylesheet (This assumes the general knowledge of how XSLT works. For a tutorial, see e.g. http://www.w3schools.com/xsl/).

For example, if you have a DC field "local.note.librarian" that you want to expose in oai_dc as <dc:note> (please note that this is not a valid DC field and thus breaks compatibility), then edit oai_dc.xsl and add the following lines just above the closing tag </oai_dc:dc>:

<xsl:for-each select="doc:metadata/doc:element[@name='local']/doc:element[@name='note']/doc:element/doc:element/doc:field[@name='librarian']">
    <dc:note><xsl:value-of select="." /></dc:note>
</xsl:for-each>

If you need to add/remove metadata fields, you're changing the output format. Therefore it is recommended to create a new metadata format as a copy of the one you want to modify. This way the old format will remain available along with the new one and any upgrades to the original format during DSpace upgrades will not overwrite your customizations. If you need the format to have the same name as the original format (e.g. the default oai_dc format), you can create a new context in xoai.xsl containing your modified format with the original name, which will be available as /oai/context-name.

NOTE: Please, keep in mind that the OAI provider caches the transformed output, so you have to run [dspace]/bin/dspace oai clean-cache after any .xsl modification and reload the OAI page for the changes to take effect. When adding/removing metadata formats, making changes NOTE: Changes in [dspace]/config/crosswalks/oai/xoai.xml requires reloading/restarting the servlet container.

...

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

<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

...