Changes between Version 25 and Version 26 of Discovery/DiscoveryWebServiceMEDIN


Ignore:
Timestamp:
09/11/09 12:23:37 (10 years ago)
Author:
mpritcha
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Discovery/DiscoveryWebServiceMEDIN

    v25 v26  
    284284}}} 
    285285 
    286 If <documentBrief> is specified as the recordDetail, a structure similar to that shown below is returned for each record in place of the <documentId> element shown above (click image to enlarge): 
     286If <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. 
     287 
     288Similarly, if <documentSummary> is specified as the recordDetail, a <documentSummary> element is returned for each result, as outlined in the doSearchResponseMessage, above. 
    287289 
    288290