Changes between Version 35 and Version 36 of Discovery/DiscoveryWebServiceMEDIN


Ignore:
Timestamp:
09/11/09 13:11:23 (10 years ago)
Author:
mpritcha
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Discovery/DiscoveryWebServiceMEDIN

    v35 v36  
    338338 parameter:: 
    339339   Target is entries in the discovery index database corresponding to parameter keywords extracted from the metadata. 
    340  
    341 MEDINTermTarget.1*:: 
     340 MEDINTermTarget.1*:: 
    342341   Target is entry in the discovery database corresponding to the '''MEDINTermTarget.1''' field in the MEDIN metadata format. (*It has been agreed that the search capability will be extended to support direct searching of a limited number of target fields within the MEDIN metadata format. List of fields currently to be confirmed by MEDIN). 
    343342 
    344343=== presentFormatList === 
    345344 
    346   DC:: 
    347     Dublin Core format  
    348   DIF_v9.4:: 
    349     GCMD DIF format (version 9.4) 
    350   MEDIN_v2.3.1:: 
    351     Metadata format used by the Marine Environmental Data and Information Network, version 2.3.1 
    352   ISO19115:: 
    353     ISO19115 (Geographic Information: Metadata) encoded as ISO19139 XML. Currently an alias for MEDIN_v2.3.1, i.e. the MEDIN format is used as the implementation of ISO within the Discovery Service. 
     345 DC:: 
     346   Dublin Core format  
     347 DIF_v9.4:: 
     348   GCMD DIF format (version 9.4) 
     349 MEDIN_v2.3.1:: 
     350   Metadata format used by the Marine Environmental Data and Information Network, version 2.3.1 
     351 ISO19115:: 
     352   ISO19115 (Geographic Information: Metadata) encoded as ISO19139 XML. Currently an alias for MEDIN_v2.3.1, i.e. the MEDIN format is used as the implementation of ISO within the Discovery Service. 
    354353 
    355354=== orderByFieldList === 
    356   textRelevance:: 
    357     Ranking metric based on relevance of match to search term (metric derived by postgres text ranking function). 
    358   datasetStartDate::  
    359     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. 
    360   datasetEndDate::  
    361     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. 
    362   dataCentre:: 
    363     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) 
    364   datasetResultsetPopularity:: 
    365     Measure of the popularity of a metadata record, related to how many times it has appeared in a result set in discovery searches. 
    366   proximity:: 
    367     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 
    368   proximityNearMiss:: 
    369     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.  
    370   datasetUpdateOrder:: 
    371     Date order based on the most recent update/edit by the original provider to the metadata record. 
    372   datasetOrder:: 
    373     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. 
    374   discoveryIngestDate:: 
    375     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. 
    376     MEDINTermTarget.1*:: 
    377       One of fields specified by MEDIN for use as a termTarget : it should be possible to configure these for use as orderByFields, too. 
     355 textRelevance:: 
     356   Ranking metric based on relevance of match to search term (metric derived by postgres text ranking function). 
     357 datasetStartDate::  
     358   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. 
     359 datasetEndDate::  
     360   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. 
     361 dataCentre:: 
     362   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) 
     363 datasetResultsetPopularity:: 
     364   Measure of the popularity of a metadata record, related to how many times it has appeared in a result set in discovery searches. 
     365 proximity:: 
     366   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 
     367 proximityNearMiss:: 
     368   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.  
     369 datasetUpdateOrder:: 
     370   Date order based on the most recent update/edit by the original provider to the metadata record. 
     371 datasetOrder:: 
     372   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. 
     373 discoveryIngestDate:: 
     374   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. 
     375 MEDINTermTarget.1*:: 
     376   One of fields specified by MEDIN for use as a termTarget : it should be possible to configure these for use as orderByFields, too. 
    378377 
    379378=== scopeList === 
    380   MDIP:: 
    381     Marine Data Information Partnership (organisation now renamed MEDIN) 
    382   NERC_DDC:: 
    383     NERC Designated Data Centres  
    384   NERC:: 
    385     NERC (General) 
    386   DPPP:: 
    387     Data Portals Project Provider 
     379 MDIP:: 
     380   Marine Data Information Partnership (organisation now renamed MEDIN) 
     381 NERC_DDC:: 
     382   NERC Designated Data Centres  
     383 NERC:: 
     384   NERC (General) 
     385 DPPP:: 
     386   Data Portals Project Provider 
    388387 
    389388> Should we deprecate MDIP and add "MEDIN" to the list? 
     
    391390 
    392391=== spatialOperatorList === 
    393   overlaps (default):: 
    394   doesNotOverlap:: 
    395   within:: 
     392 overlaps (default):: 
     393 doesNotOverlap:: 
     394 within:: 
    396395 
    397396 
    398397=== spatialReferenceSystemList === 
    399   EPSG:4326:: 
     398 EPSG:4326:: 
    400399 
    401400=== dateRangeTargetList === 
    402   temporalCoverage:: 
    403   lastRevisionDate:: 
    404   metadataIngestionDate:: 
     401 temporalCoverage:: 
     402 lastRevisionDate:: 
     403 metadataIngestionDate:: 
    405404 
    406405=== temporalOperatorList === 
    407   equals:: 
    408   doesNotEqual:: 
    409   onOrBefore:: 
    410   onOrAfter:: 
    411   before:: 
    412   after:: 
     406 equals:: 
     407 doesNotEqual:: 
     408 onOrBefore:: 
     409 onOrAfter:: 
     410 before:: 
     411 after:: 
    413412 
    414413=== metadataFormatList === 
    415414(Note this is separate from presentFormatList, to distinguish between purposes). metadataFormatList lists values available to distinguish the original source format of a harvested metadata item. 
    416415 
    417   DC:: 
    418     Dublin Core format  
    419   DIF_v9.4:: 
    420     GCMD DIF format (version 9.4) 
    421   MEDIN_v2.3.1:: 
    422     Metadata format used by the Marine Environmental Data and Information Network, version 2.3.1 
    423   ISO19115:: 
    424     ISO19115 (Geographic Information: Metadata) encoded as ISO19139 XML. Currently an alias for MEDIN_v2.3.1, i.e. the MEDIN format is used as the implementation of ISO within the Discovery Service. 
     416 DC:: 
     417   Dublin Core format  
     418 DIF_v9.4:: 
     419   GCMD DIF format (version 9.4) 
     420 MEDIN_v2.3.1:: 
     421   Metadata format used by the Marine Environmental Data and Information Network, version 2.3.1 
     422 ISO19115:: 
     423   ISO19115 (Geographic Information: Metadata) encoded as ISO19139 XML. Currently an alias for MEDIN_v2.3.1, i.e. the MEDIN format is used as the implementation of ISO within the Discovery Service. 
    425424 
    426425=== recordDetailList === 
    427   id:: 
    428   brief:: 
    429   summary:: 
    430   full:: 
    431  
     426 id:: 
     427 brief:: 
     428 summary:: 
     429