Page History

OAI-PMH Data Provider 2.0 (Internals)

...

DSpace exposes collections and communities as sets.

Each community and collection has a corresponding OAI set, discoverable by harvesters via the ListSets verb. The setSpec is the Handle of the collectionbased on the community/collection handle, with the ":" and "/" converted to underscores so that the Handle is underscore to form a legal setSpec, for . The setSpec is prefixed by "com_" or "col_" for communities and collections, respectively (this is a change in set names in DSpace 3.0 / OAI 2.0). For example:

hdlcol_1721.1_1234

Naturally enough, the community/collection name is also the name of the corresponding set.

...

A question is, "is all metadata public?" Presently the answer to this is yes; all metadata is exposed via OAI-PMH, even if the item has restricted access policies. The reasoning behind this is that people who do actually have permission to read a restricted item should still be able to use OAI-based services to discover the content. But, exposed data could be changed by changing the XSLT defined at [dspace]/config/modulescrosswalks/oai/metadataFormats.

Modification Date (OAI Date Stamp)

...

As part of each record given out to a harvester, there is an optional, repeatable "about" section which can be filled out in any (XML-schema conformant) way. Common uses are for provenance and rights information, and there are schemas in use by OAI communities for this. Presently DSpace does not provide any of this information, but XOAI core library allows its definition. This require requires to dive into code and perform some changes.

...

Each OAI-PMH ListRecords request will return at most 100 records (by default) but it could be configured in the [dspace]/config/modulescrosswalks/oai/xoai.xml file.

When a resumption token is issued, the optional completeListSize and cursor attributes are included. OAI 2.0 resumption tokens are persistent, so expirationDate of the resumption token is undefined, they do not expire.

...