Changes between Version 9 and Version 10 of Discovery/DiscoveryWebServiceMEDIN


Ignore:
Timestamp:
06/11/09 09:38:33 (10 years ago)
Author:
mpritcha
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Discovery/DiscoveryWebServiceMEDIN

    v9 v10  
    11= NERC !DataGrid Discovery Web Service : MEDIN Improvements November 2009 = 
    22 
     3[[PageOutline(1-2)]] 
     4 
    35The NERC !DataGrid (NDG) Discovery Web Service provides a search interface to metadata records harvested from collaborating data providers and is the backend server to which the NERC Data Discovery Service is a client. 
    46 
    5   * [#Introduction Introduction] 
    6   * [#Releases Releases] 
    7   * [#Connectivity Connectivity] 
    8   * [#XMLDataTypes XML Data Types] 
    9   * [#DiscoveryServiceOperations Discovery Service Operations] 
    10   * [#TermLists Term Lists] 
    11   * [#SupportedMetadataFormats Supported Metadata Formats] 
    12  
    137== Introduction == 
    148 
     
    1711The search capability provided by the service enables full-text and spatio-temporal searches of catalogued metadata records and returns search results a defined XML structure, enabling search clients to be constructed by interested parties for their own purposes. The [http://ndg.nerc.ac.uk/discovery NERC Data Discovery Service] is one such client, as is the [http://www.edp.nerc.ac.uk Environmental Data Portal], among other examples. 
    1812 
    19 == Releases == 
     13== Scope == 
    2014 
    2115This documentation covers functionality proposed for the improvements commissioned by MEDIN. 
     
    9791The doSearchRequest message is shown in schema form in fig X (click image to enlarge).  
    9892 
    99 [[Image(doSearchSchema.png, 350px)]] 
     93[[Image(doSearchSchema.png, 400px)]] 
    10094 
    10195=== Choice of search criteria: <termSearch>, <spatialSearch> and <temporalSearch> ===  
     
    10397 
    10498==== termSearch ==== 
    105 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: 
     99!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: 
    106100  * <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. 
    107101  * <termTarget> : target field name taken from the termTargetList list of valid term targets. 
    108 If multiple <termSearch> elements are present (e.g. to search different <termTargets) ), these are interpreted as successive term searches to be combined in "OR" combination. For example: 
     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: 
    109103 
    110104{{{ 
     
    127121}}} 
    128122 
    129 If we were to extend the example by adding an additional termSearch, also targetted at the abstract, this would be combined in OR combination with the first termSearch *for that target*, i.e. 
     123If we were to extend the example by adding an additional termSearch '''also''' targetted at the abstract, this would be combined in OR combination with the first termSearch for '''that''' target (abstract), i.e. 
    130124 
    131125{{{