Changes between Version 69 and Version 70 of Discovery/DiscoveryWebServiceMEDIN


Ignore:
Timestamp:
03/03/10 10:10:04 (9 years ago)
Author:
sdonegan
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Discovery/DiscoveryWebServiceMEDIN

    v69 v70  
    295295}}} 
    296296 
    297 If <!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.  The element <!AdditionalInformation> holds further elements containing further information pertaining to the record in question.  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. 
     297If <!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.  Within <!OrderedField> are 2 elements, <!MetricName> which is the name of the ordering field and <!MetricValue> which is the actual value by which this document is ordered.  These 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 <!AdditionalInformation> element holds child elements containing further detailed information (as requested) relating to the record in question. Where multiple values are associated with this element field within the database they are separated by a ";".  If there is no information available to fill these fields then they are left blank. 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. 
    298298 
    299299Similarly, 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.).