Changes between Version 26 and Version 27 of Discovery/DiscoveryWebServiceMEDIN


Ignore:
Timestamp:
09/11/09 12:29:20 (10 years ago)
Author:
mpritcha
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Discovery/DiscoveryWebServiceMEDIN

    v26 v27  
    286286If <documentBrief> is specified as the recordDetail, a <documentBrief> element is returned for each result, as outlined in the doSearchResponeMessage, above. This contains the <documentId> element, containing the id of the document, but is accompanied by the additional element <title>, containing the title from the metadata record, and a set of <orderedField> elements corresponding to the <orderByField>s used in the search request. In other words, the requested ordering fields are returned alongside the results so that a client can display the content of those fields which contributed to the resulting record ordering. The purpose of this <documentBrief> detail option is to enable clients to render a results list directly from the search response, without having immediately to invoke the doPresent operation to retrieve additional detail. 
    287287 
    288 Similarly, if <documentSummary> is specified as the recordDetail, a <documentSummary> element is returned for each result, as outlined in the doSearchResponseMessage, above. 
     288Similarly, 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 
    290290