From NSDLWiki

Jump to: navigation, search




Create a Metadata object (see ObjectTypes) in the NDR.

Request URL
Must be an HTTP POST request.


  • inputXML (required) - contains metadata supplied by a MetadataProvider about a given NDR object, as well as identifiers and relationships for the Metadata object. For metadata harvested via the Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH - see, inputXML could include all the metadata formats available for an OAI item. Individual metadata formats may also be added, removed, or replaced individually through the modifyMetadata request.

    • Properties
      • uniqueID (required) - An identifier that is unique for all Metadata objects supplied by a single MetadataProvider.
      • itemId (optional) - currently (2006-12) this must be provided if the metadata is to be exposed via the NDR's OAI server. This must be a valid NSDL OAI identifier, meaning it must start "" and it must adhere to the OAI guidelines for OAI identifiers ( It must also be unique for each metadata object in the NDR. Best practice is to prepend "" to the uniqueID.

    • Relationships
      • metadataFor (required) - the handle of an NDR object the Metadata describes. This relationship is repeatable if the Metadata describes more than one NDR object (e.g. there are two valid resouce identifiers in the metadata).
      • metadataProvidedBy (required) - the handle of the MetadataProvider object representing the source of the metadata in this request.

    • Datastreams
      • format (required) - There must be at least one metadata format supplied; multiple formats may be supplied. Includes a "type" attribute designating the format-label of the metadata. The format-label must be a known type; as of 2006-12-08, known types include "nsdl_dc" (for NSDL normalized qualified Dublin Core), "oai_dc" (for simple Dublin Core derived from the normalized qualified Dublin Core nsdl_dc format) or "native_(xxx)" for raw, un-normalized metadata, such as "native_oai_dc" or "native_nsdl_dc".
        • meta (required) - each format supplied must contain a complete, schema-valid metadata record. The meta element must must contain XML that complies with another schema, such as or In other words, the meta element must have a single child element that can be interpreted as the root of a schema-valid XML document - all namespace declarations and schema locations must be specified in the children of the meta element.
        • info (currently required) - Information to be exposed in OAI "abouts" bundled with the NDR's OAI server exposure of this metadata. The info element must contain the following (see the XML schema for more information):
          • nsdlAboutCategory - either "item" or "collection" (this is a vestigial field, slated for deprecation and/or removal).
          • repositoryPrimaryIdentifier - The identifier within the metadata which is to be considered the "primary" identifier. For example, if there are two <dc:identifier> fields in metadata that describes a resource, then one of them must be chosen as the "primary" identifier in this metadata. Best practice: a valid URL present in the metadata (you may not choose an identifier that is not present in the provided metadata).
          • link (currently important to the NSDL search service) - the NDR OAI identifier of the OAI metadata describing the NDR Aggregation object which has this Metadata object's described object as a member. This will be the same value for all Metadata objects from a single MetadataProvider. Currently, this should be determined by the following steps: 1) get the handle of the MetadataProvider object responsible for this Metadata from the metadataProvidedBy relationship. 2) get the handle of the Aggregator object describing the aggregation implied by the MetadataProvider from the aggregatedBy relationship in the Aggregator object. 3) get the handle of the Metadata object describing the Aggregator by using the find command to look for a Metadata object that has metadataFor relationship to the Aggregator object. 4) The itemId property of the Metadata object describing the Aggregator (describing the aggregation for the MetadataProvider which is the soure of this Metadata object, which lives in the house that Jack built) is the NDR OAI identifier to be used as the value for this link.
          • harvestDate - when the metadata was harvested, as a UTC datestamp (GMT, in datetime "Z" format)
          • harvestHarvestType - how this metadata was harvested, from enumerated list (e.g. "OAI2.0", "other").
          • harvestDatasourcePublic - flag indicating whether the data source of the harvest is publically available or not (true/false).
          • harvestDatasource - URL for the metadata provider's service (e.g. the baseURL of an OAI data provider). This must be a URI, and may not be empty. If necessary, enter a meaningful fake value, such as: http://fake.baseurl/metadataNotHarvested
          • harvestIdentifier - the metadata provider's unique ID for this metadata. (e.g. the metadata provider's OAI identifier). This should be the same as the value of the uniqueID property.
          • harvestRecordDatestamp - when the metadata was last updated, as a UTC datestamp (GMT, in datetime "Z" format). This is equivalent to the datestamp element of the harvested record's OAI header.
          • metadataNamespace> - XML namespace URI of this format's metadata.

Below is example inputXML for a Metadata object to be added. This Metadata object corresponds to the OAI item with identifier "oai:myDomain:666". The metadata included here describes the NDR Resource object identified by handle 2200/20061111T. This metadata originates from the MetadataProvider with NDR handle 2200/5005. A single metadata format is provided; it is of type -nsdl_dc- and contains an XML schema valid document with root element <nsdl_dc:nsdl_dc> with the proper XML namespace declarations and schema location indicated. The info element has been populated with appropriate information for use in NDR OAI about fields. Note that the command is understood to be "add" (rather than "replace" or "delete") so the inputXML does not require a command as the first child of the <properties>, <relationships>, or <data> elements.
<?xml version="1.0" encoding="UTF-8"?>
      <format type="nsdl_dc">
              schemaVersion="1.02.000" xmlns:dc="" 
            <dc:title>My life: a Monster's Story.</dc:title>
            <dc:description>The story of Frankenstein.</dc:description>
            <dc:creator>Baron Von Frankenstein</dc:creator>
            <dc:author>Mary Shelly</dc:author>

Response Fields

  • handle - the NDR handle for the new Metadata object

Response Example

<?xml version="1.0" encoding="UTF-8"?>

API Links:

Personal tools