ESciDoc OAI PMH Provider And DC Transformation

From MPDLMediaWiki
Jump to: navigation, search

Implementation

Requirement

  • the persistent identifier of the resource shall be included in the metadata record served with OAI-PMHOpen Archives Initiative Protocol for Metadata Harvesting

Background information

  • Persistent identifier of a resource assigned in the eSciDocEnhanced Scientific Documentation repository can not be included in the native escidoc metadata record due to the following reasons:
    • there is no clear separation of control who may modify/change the PIDPersistent Identifer or Identification of the resource and at what point of time
    • even if we provide an e.g. application URLUniform Resource Locator to always deal with latest versions of the resource the problem above will persist

Issues

  • OAI-DCOpen Archives Initiative Dublin Core transformation can not include the PIDPersistent Identifer or Identification of the resource/resource version in dc:identifier as it only works for metadata record
  • in general related not only to the OAI-DCOpen Archives Initiative Dublin Core transformation, but as well to the metadata offered with the record (in any metadata profile)
  • according OAI-PMHOpen Archives Initiative Protocol for Metadata Harvesting 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-PMHOpen Archives Initiative Protocol for Metadata Harvesting. 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 (URLUniform Resource Locator, URNUniform Resource Name, DOIDigital Object Identifier, etc.) of the associated resource. The mandatory Dublin Core format provides the identifier element that should be used for this purpose."



Discussion

  • These would mean that the OAI-PMHOpen Archives Initiative Protocol for Metadata Harvesting recommends to have URIUniform Resource Identifier/URLUniform Resource Locator or other PIDPersistent Identifer or Identification of the resource as part of the metadata
  • that is against escidoc concept as escidoc resources may have various metadata records therefore, PIDPersistent Identifer or Identification of the resource (being URIUniform Resource Identifier or URLUniform Resource Locator or Handle or any string) is stored within the resource properties
  • whatever metadata profiles are offered via OAI-PMHOpen Archives Initiative Protocol for Metadata Harvesting these should be transformed before written to the eSciDocEnhanced Scientific Documentation OAI-PMHOpen Archives Initiative Protocol for Metadata Harvesting cache (?)
  • currently, it is possible to relate the XSLTExtensible Stylesheet Language Transformations to DCDublin Core transformation in the content model for one metadata record - this works for one single mandatory metadata record
  • escidoc has a concept of minimum one mandatory metadata record
    • can there be several mandatory metadata records?
    • XSLTExtensible Stylesheet Language Transformations reference in the ContentModel shall be allowed for any metadata record that is associated with the resource
    • XSLTExtensible Stylesheet Language Transformations transformation should be done at the time of writing the resource to the OAI-PMHOpen Archives Initiative Protocol for Metadata Harvesting cache
    • XSLTExtensible Stylesheet Language Transformations transformation shall work not only for the OAI-PMHOpen Archives Initiative Protocol for Metadata Harvesting transformation i.e. envisioned OAI-OREOpen Archives Initiative Object Reuse and Exchange service may make use of it as well ?)
    • what about allowing several transformations in the Content-model related to the service for which these transformations are actually useful (e.g. element content-model:resources) ?
      • Example: Resource R1 has MDRec1 and MDRec2
        • repository user decides to offer OAI-PMHOpen Archives Initiative Protocol for Metadata Harvesting for both MDRec1, MDRec2 and additionally OAI-DCOpen Archives Initiative Dublin Core
        • repository user decides to register the following "service-specific-transformations": Item ->OAIOpen Archives Initiative_MDREC1, Item->OAIOpen Archives Initiative_MDREC2, Item->OAI-DCOpen Archives Initiative Dublin Core
        • in other case repository user may decide to register only 1 "service-specific-transformaton" : Item->OAI-DCOpen Archives Initiative Dublin Core where he merges information he needs from both records into single OAI-DCOpen Archives Initiative Dublin Core record in custom manner and is able to provide the PIDPersistent Identifer or Identification of the item as DCDublin Core identifier