Changes between Version 17 and Version 18 of Discovery/DiscoveryWebServiceMEDIN


Ignore:
Timestamp:
06/11/09 11:01:25 (10 years ago)
Author:
mpritcha
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Discovery/DiscoveryWebServiceMEDIN

    v17 v18  
    9494 
    9595=== Choice of search criteria: <termSearch>, <spatialSearch> and <temporalSearch> ===  
    96 The <searchCriteria> element acts as a container enabling the selection of one or more of <termSearch>, <spatialSearch> and <temporalSearch>. Searches of these 3 basic types may be used in combination. Only one of each of <termSearch>, <spatialSearch> and <temporalSearch> may be included, but at least one of these three types of search must be supplied. 
     96The <searchCriteria> element acts as a container enabling the selection of one or more of <termSearch>, <spatialSearch> and <temporalSearch>. Only one of each of <termSearch>, <spatialSearch> and <temporalSearch> may be included, but at least one of these three types of search must be supplied. If more than one is specified, the resulting search combines the components in "AND" combination (i.e. metadata records should match the term search AND the spatial search AND the temporal search criteria). 
    9797 
    9898==== termSearch ==== 
     
    153153An optional <spatialOperator> may be included, populated with a term from the [#spatialOperatorList spatialOperatorList], defining the comparison to be applied to spatial coverage(s) related to metadata records. The default value is "overlaps". Note that in the discovery index database, metadata records may contain several spatial coverages, so a match can occur if any of the spatial coverages related to the metadata item match the criteria specified in the spatial search.  
    154154 
    155 === Temporal searching : <DateRange> === 
    156 Full-text, author or parameter searches my optionally be combined with a further restriction that the temporal coverage ovelaps the specified <DateRange>. Both <DateRangeStart> and <DateRangeEnd> must be specified and must be valid dates of the form YYYY-MM-DD. TODO: it is planned to implement a choice of <temporalOperator> in a similar manner to <spatialOperator>. 
     155=== Temporal searching : <!DateRange> === 
     156The search may incoporate a temporal query to restrict results to those metadata records having temporal coverage(s) matching the search criteria specified within <DateRange>. One or two <date> elements may be specified, to represent either a single date, or a date range. Each <date> element must contain a <DateValue> element populated in the form YYYY-MM-DD, and optionally a <temporalOperator> element, populated with a value from [#temporalOperatorList temporalOperatorList], defining the semantic meaning of this date criterion in the search. In addition, an optional <dateRangeTarget> element may be included, populated with a value from the [#dateRangeTargetList dateRangeTargetList], to enable searching of dates other than the default of "temporal coverage of data".  
     157Examples are shown below: 
     158 
     159{{{ 
     160<DateRange> 
     161  <date> 
     162    <DateValue>2001-01-01</DateValue>     
     163  </date> 
     164  <date> 
     165    <DateValue>2002-02-03</DateValue>     
     166  </date> 
     167</dateRange> 
     168}}} 
     169means 
     170{{{ 
     171Find metadata records where the temporal coverage(s) of the data overlaps the date range 2001-01-01 to 2002-02-03 inclusive. 
     172}}} 
     173 
     174{{{ 
     175<DateRange> 
     176  <date> 
     177    <DateValue>2001-01-01</DateValue> 
     178    <temporalOperator>before</temporalOperator>     
     179  </date> 
     180  <date> 
     181    <DateValue>2002-02-03</DateValue>     
     182    <temporalOperator>after</temporalOperator>     
     183  </date> 
     184</dateRange> 
     185}}} 
     186means 
     187{{{ 
     188Find metadata records where the temporal coverage(s) of the data is outside of the date range 2001-01-01 to 2002-02-03 inclusive. 
     189}}} 
     190 
     191 
     192{{{ 
     193<DateRange> 
     194  <date> 
     195    <DateValue>2001-01-01</DateValue> 
     196    <temporalOperator>onOrbefore</temporalOperator>     
     197  </date> 
     198</dateRange> 
     199}}} 
     200means 
     201{{{ 
     202Find metadata records where the temporal coverage(s) of the data is on or before the date 2001-01-01. 
     203}}} 
     204 
     205{{{ 
     206<DateRange> 
     207  <date> 
     208    <DateValue>2001-01-01</DateValue> 
     209    <temporalOperator>onOrbefore</temporalOperator>     
     210  </date> 
     211  <dateRangeTarget>lastRevisionDate</dateRangeTarget> 
     212</dateRange> 
     213}}} 
     214means 
     215{{{ 
     216Find metadata records where the last revision date of the data is on or before the date 2001-01-01. 
     217}}} 
     218 
     219> Looking at these examples we might need to tidy up the capitalisation of elements in the schema & WSDL. 
    157220 
    158221=== Paging : <start> and <howMany> ===  
     
    317380=== metadataFormatList === 
    318381=== recordDetailList === 
     382