Changes between Version 27 and Version 28 of Discovery/DiscoveryWebServiceMEDIN


Ignore:
Timestamp:
09/11/09 12:32:21 (10 years ago)
Author:
mpritcha
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Discovery/DiscoveryWebServiceMEDIN

    v27 v28  
    278278        <hits>2</hits> 
    279279        <documents> 
    280           <documentId>id of matching document, result 1]</documentId> 
    281           <documentId>[id of matching document, result 2]</documentId> 
     280          <documentId>idForResult1GoesHere</documentId> 
     281          <documentId>idForResult2GoesHere</documentId> 
    282282        </documents> 
    283283</doSearchReturn> 
     
    288288Similarly, if <documentSummary> is specified as the recordDetail, a <documentSummary> element is returned for each result, as outlined in the doSearchResponseMessage, above. In addition to the content added by the <documentBrief> option, <documentSummary> includes the metadata abstract, and temporal and spatial information. For the temporal and spatial components of this <documentSummary> the schema reuses the structures used for the search request, hence the optional temporalOperator are spatialOperator elements are redundant (and will be omitted) from the return context, however the dateRangeTarget element is useful as a contextual reminder of what the returned date pertains to (temporal coverage of data, last revision date of data, or ingestion date of metadata, etc.). 
    289289 
     290A corresponding <documentFull> structure is used in the [#doPresentOperation doPresent operation] operation as the structure in which the document payload is returned. 
    290291 
    291292=== doPresent operation ===