Changes between Version 10 and Version 11 of Discovery/DiscoveryWebServiceMEDIN


Ignore:
Timestamp:
06/11/09 09:46:20 (10 years ago)
Author:
mpritcha
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Discovery/DiscoveryWebServiceMEDIN

    v10 v11  
    9999!TermSearch is a full-text search invoked on a specific target field in the discovery database. Child elements <term> and <termTarget> should be populated as follows: 
    100100  * <term> : text term to search for. Whitespace separates component words, which are searched in "OR" combination unless the "+" symbol is used between them, in which case the words joined in this way are searched in "AND" combination. 
    101   * <termTarget> : target field name taken from the termTargetList list of valid term targets. 
    102 If multiple <termSearch> elements are present (e.g. to search different <termTargets) ), these are interpreted as successive term searches to be combined in '''"AND"''' combination. For example: 
     101  * <termTarget> : target field name taken from the [#termTargetList termTargetList] list of valid term targets. 
     102If multiple <termSearch> elements are present (e.g. to search different <termTargets) ), these are interpreted as successive term searches to be combined in "AND" combination. For example: 
    103103 
    104104{{{ 
     
    145145    author contains "lawrence" 
    146146}}} 
    147  
    148 --Got to here while editing-- 
    149  
    150 This element should be populated with a valid value from the termTargetList list accessible via the getList operation. At present, these are:  
    151  
    152 ==== fullText ==== 
    153 A full-text search is applied to the whole discovery metadata record  
    154 ==== author ====  
    155 A full-text search is applied only to those sections of the discovery metadata record relating to authorship of the dataset  
    156 ==== parameter ====  
    157 A full-text search is applied only to the parameter listing section of the discovery metadata record. 
    158   
    159 <term> should be populated with the search term, which can be a string of one or more words and wildcard characters. The service is currently configured to execute searches by attempting to match XML documents (in the discovery database) where ALL of the components of the search term are matched (as opposed to ANY). In this way, increasingly specific searches can be used to refine the search results. Searches are case-insensitive. Examples of fullText search terms are:  
    160  
    161   temperature:: 
    162     Matches records with the word "temperature" in any node of a document  
    163   sea surface temperature:: 
    164     Matches documents having the words "sea", "surface" AND "temperature" (in any order)  
    165   *neodc*:: 
    166     Matches documents containing the string "neodc", even if embedded within a larger string.  
    167147 
    168148=== Paging : <start> and <howMany> ===  
     
    310290== Term Lists == 
    311291 
    312 == Supported Metadata Formats == 
     292=== termTargetList === 
     293  * fullText 
     294  * author 
     295  * parameter