Changes between Version 64 and Version 65 of Discovery/DiscoveryWebServiceMEDIN


Ignore:
Timestamp:
02/03/10 15:22:08 (9 years ago)
Author:
sdonegan
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Discovery/DiscoveryWebServiceMEDIN

    v64 v65  
    298298Similarly, 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.). 
    299299 
    300 Correspondingly the <!DocumentFull> element builds upon the <!DocumentBrief> and <!DocumentSummary> elements adding further information (including <!AdditionalInformation>) but importantly a <Document> element contains a CDATA representation of the original XML metadata with format corresponding to that chosen in <!MetadataFormat> (defaulting to MEDIN_2.3).  These 4 document types comprise a data type "Documents" which is dependant on the values supplied in <!RetrieveCriteria> and is also reused in the DoPresent operation. 
    301  
    302  
    303 === DoPresent operation === 
     300Correspondingly the <!DocumentFull> element builds upon the <!DocumentBrief> and <!DocumentSummary> elements adding further information (including <!AdditionalInformation>) but importantly a <Document> element contains a CDATA representation of the original XML metadata with format corresponding to that chosen in <!MetadataFormat> (defaulting to MEDIN_2.3).  These 4 document types comprise a data type "Documents" which is dependant on the values supplied in <!RetrieveCriteria> and is also reused in the !DoPresent operation. 
     301 
     302 
     303=== !DoPresent operation === 
    304304 
    305305The doPresent operation provides a means of retrieving (presenting) one or more XML documents from the database. The doPresentRequest message is defined as follows (click image to enlarge):