ESciDoc OAI PMH Provider And DC Transformation

Implementation

• see https://escidoc.org/JSPWiki/en/OaiPmh
• https://escidoc.org/JSPWiki/en/InfrastructureOaiPmhConfiguration
• official protocol specification see http://www.openarchives.org/OAI/openarchivesprotocol.html
• OAI-DC transformation works on mandatory record, XSLT configurable for the content-model

Issues

• OAI-DC transformation can not include the PID of the resource/resource version in dc:identifier as it only works for metadata record
• in general related not only to the OAI-DC transformation, but as well to the metadata offered with the record (in any metadata profile)
• according OAI-PMH specification:

Note that the identifier described here is not that of a resource. The nature of a resource identifier is outside the scope of the OAI-PMH. To facilitate access to the resource associated with harvested metadata, repositories should use an element in metadata records to establish a linkage between the record (and the identifier of its item) and the identifier (URL, URN, DOI, etc.) of the associated resource. The mandatory Dublin Core format provides the identifier element that should be used for this purpose.

• These would mean that the OAI-PMH recommends to have URI/URL or other PID of the resource as part of the metadata
• that is against escidoc concept as escidoc resources may have various metadata records
• the PID of the resource (being URI or URL or Handle or any string) is stored within the resource properties

Open Archives Initiative Dublin Core

Extensible Stylesheet Language Transformations

Persistent Identifer or Identification

Open Archives Initiative Protocol for Metadata Harvesting

Uniform Resource Locator

Uniform Resource Name

Digital Object Identifier

Uniform Resource Identifier