Changes between Version 8 and Version 9 of Discovery/DiscoveryWebService


Ignore:
Timestamp:
20/07/09 15:51:03 (10 years ago)
Author:
mpritcha
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Discovery/DiscoveryWebService

    v8 v9  
    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. [Note : this is a known bug currently causing records with no start date to be treated as if their start date is AFTER that of the last record with a start date. With orderByDirection set to "ascending" this is less of a problem, but at present, with orderByDirection set to "descending", these "incomplete" records are the first in the results list. See ticket ???]  
     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]  
    125125  dataCentre:: 
    126     The name of the data centre supplying the metadata record. In the case of records supplied in DIF format, this is the Data_Centre/Short_Name field. In the case of other metadata formats, the most appropriate equivalent field is used as this index (e.g. "" for MDIP format) 
     126    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) 
    127127  datasetResultsetPopularity:: 
    128     ?? 
     128    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:: 
    130130    ?? 
     
    137137 
    138138In addition, the direction of ordering (ascending or descending) can be specified. If omitted, the default direction is ascending. 
     139 
     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 ???]  
    139141 
    140142=== Scope of search: <scope> ===