Child pages
  • KE Usage Statistics Guidelines

Versions Compared

Key

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

...

  • Incorrect data which has already been offered by the data provider shall be corrected. There are two possibilities:
    • Re-issuing of a corrected set of data carrying the same identifier in the OAI-PMH record header as the set of data to be corrected, with an updated OAI-PMH record header datestamp
    • When the correction is a full deletion of the incorrect issued data, the OAI-PMH record has to be re-issued without a Context Object payload, with specified "<deleted>" flag and updated datestamp in the OAI-PMH record header.
  • Records that fall out of the time frame for which the data provider offers data: These records are silently neglected, i. e. not offered via the OAI-PMH interface anymore, without using the deletion tracking features of OAI-PMH.

Metadata formats (see OAI-PMH, 3.4)

All data providers have to provide support for <context-object> documents or <context-objects> aggregations, respectively.This choice also has to be announced in the response to the "listMetadataFormats" query OAI-PMH, 4.4 by the data provider. While a specific "metadataPrefix" is not required, the information about "metadataNamespace" and "schema" is fixed for implementations: <metadataFormat>
<metadataPrefix>ctxo</metadataPrefix>
<schema>http

Code Block
xml
xml
linenumbertrue
titleOAI-PMH record
collapsetrue

<metadataFormat>
  <metadataPrefix>ctxo</metadataPrefix>
  <schema>http://www.openurl.info/registry/docs/xsd/info:ofi/fmt:xml:xsd:ctx</schema>

...


  <metadataNamespace>info:ofi/fmt:xml:xsd:ctx</metadataNamespace>

...


</metadataFormat>
Info

Using OAI-PMH, the mandatory MetadataPrefix for UpenURL Context Objects will be: "ctxo"

...