Changes between Version 11 and Version 12 of Discovery/DiscoveryWebService


Ignore:
Timestamp:
06/08/09 09:22:42 (10 years ago)
Author:
sdonegan
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Discovery/DiscoveryWebService

    v11 v12  
    121121  textRelevance:: 
    122122    Ranking metric based on relevance of match to search term (metric derived by postgres text ranking function). 
    123   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 1 below]  
     123  datasetStartDate::  
     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, hence appearing at the end of the results. 
     125  datasetEndDate::  
     126    The end date of the date range given for the temporal coverage of the metadata record. Records with no end date defined are treated as if their end date is later than that last record with a start date defined, hence appearing at the end of the results. 
    125127  dataCentre:: 
    126128    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) 
     
    128130    Measure of the popularity of a metadata record, related to how many times it has appeared in a result set in discovery searches. 
    129131  proximity:: 
    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]. 
     132    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 originally defined are omitted from the search 
    131133  proximityNearMiss:: 
    132134    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.  
    133135  datasetUpdateOrder:: 
    134     Date order based on the most recent updates to the metadata record 
     136    Date order based on the most recent update/edit by the original provider to the metadata record. 
    135137  datasetOrder:: 
    136138    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. 
     139  discoveryIngestDate:: 
     140    Date order based on the date of insertion of that record into the underlying database supporting the service.  Note that this differs from "datasetUpdateOrder" in that this records the actual date a record was placed in the database as opposed to the last edit date of that record. 
    137141 
    138142In addition, the direction of ordering (ascending or descending) can be specified. If omitted, the default direction is ascending.