Changes between Version 10 and Version 11 of Discovery/DiscoveryWebService


Ignore:
Timestamp:
20/07/09 17:15:45 (10 years ago)
Author:
sdonegan
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Discovery/DiscoveryWebService

    v10 v11  
    122122    Ranking metric based on relevance of match to search term (metric derived by postgres text ranking function). 
    123123  date::  
    124     The start date of the date range given for the temporal coverage of the metadata record. Records with no start date defined are treated as if their start date is later than that last record with a start date defined. [See note below]  
     124    The start date of the date range given for the temporal coverage of the metadata record. Records with no start date defined are treated as if their start date is later than that last record with a start date defined. [See note 1 below]  
    125125  dataCentre:: 
    126126    The name of the data centre supplying the metadata record. In the case of records supplied in DIF format, this is the Data_Centre_Name/Short_Name field. In the case of other metadata formats, the most appropriate equivalent field is used as this index (e.g. "DistributorName" for MDIP format) 
     
    128128    Measure of the popularity of a metadata record, related to how many times it has appeared in a result set in discovery searches. 
    129129  proximity:: 
    130     ?? 
     130    The geographical proximity of the centre of the spatial coverage defined in the metadata record to the centre of the original search bounding box.  Where no spatial information was originally selected proximity is calculated against the centre of a 'global' bounding box (0N, 0E).  Metadata records with no spatial information defined are treated as if they have a global extent, so that their centroid is 0,0 which when coupled with a search in which no spatial data is defined places these records first [see note 1 below]. 
    131131  proximityNearMiss:: 
    132     ?? 
     132    An ordering based on records that were not within the originally requested spatial extent, but that occur within an arbritrary 10% of the original bounding box extent.  Where records are present that satisfy this scenario, they are ordered according to proximity to the outside edge of the original bounding box.  This option is to give users an idea of datasets that were close to the original bounding box and still matched the search without having to redefine the original bounding box and original search terms.  
    133133  datasetUpdateOrder:: 
    134     ?? 
     134    Date order based on the most recent updates to the metadata record 
    135135  datasetOrder:: 
    136     ?? 
     136    Alphabetical order based on the name of the metadata record.  In DIF records this is the Entry_Title field and for MDIP the Title field. 
    137137 
    138138In addition, the direction of ordering (ascending or descending) can be specified. If omitted, the default direction is ascending. 
    139139 
    140 [Note : a bug has recently been identified whereby records with no metric (as used in the orderByDirection, above) are incorrectly treated, resulting in these records appearing at the top of the list in the case of orderByDirection="descending". See ticket [http://proj.badc.rl.ac.uk/ndg/ticket/1029#comment:4 1029] ]  
     140[Note 1 : a bug has recently been identified whereby records with no metric (as used in the orderByDirection, above) are incorrectly treated, resulting in these records appearing at the top of the list in the case of orderByDirection="descending". See ticket [http://proj.badc.rl.ac.uk/ndg/ticket/1029#comment:4 1029] ]  
    141141 
    142142=== Scope of search: <scope> ===