Ignore:
Timestamp:
29/05/07 17:36:43 (12 years ago)
Author:
lawrence
Message:

Sundry minor improvements in layout etc.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • TI07-MOLES/trunk/PythonCode/wsgi/layout/help.html

    r2413 r2522  
    11 
    2 <h3> NDG Search Interface </h3> 
     2<h3> NERC Data Discovery</h3> 
    33 
    44<h4> Background </h4> 
    55 
    6 <p>The NDG serach interface allows one to search the contents of the NERC DataGrid catalogue. 
     6<p> This is an interface which allows one to search the contents of the NERC DataGrid catalogue. 
    77The catalogue is populated with "discovery" metadata, not with data themselves, but the 
    88response sets include links which should lead the user to the datasets of interest</p> 
    99 
    1010<p> The metadata has been harvested from data providers, normally daily. Not all data providers are  
    11 within the NERC datagrid, and not all will provide the same data services.</p> 
     11within the NERC datagrid, and not all will provide the same data services. It is currently not possibleto provide a list of data providers which are indexed, as the membership is volatile. An easy way to find out if the data provider you care about is indexed is to search for it by name. You can limit the result set to NERC data centres or the Marine Data and Information Partnership via the advanced search page. </p> 
    1212 
    1313<h4> Searching </h4> 
    1414 
    15 <p> Free text searches may use xpath wild carding, such as ... </p> 
     15<p> Currently the interface provides free text searching by default, although geographical and temporal constraints can be imposed via the advanced search page. </p> 
     16<p> The current interface allows multiple words to be entered, in which case the search 
     17uses AND to link these together (they do not have to be adjacent). The search is not case sensitive.</p> 
     18<p> The current geographical and temporal searches are "outer-bound' constraints, overlaps will not be returned. A future version will provide more sophisticated alternatives.  
     19<p> The author search is designed to find data creators. Users should be aware that most data centres do not adequately populate all their records with enough information to identify the 
     20authors. We hope that this will change! </p> 
    1621 
    1722<h4> Understanding the Result sets </h4> 
    1823 
    19 <p> The links in each response entry are  
     24<p> The summary result set provdes a title, and perhaps a formal citation, along with a piece of the dataset abstract (and if possible the geographic and temporal domains) along with some important links. The links in each response entry are </p> 
    2025<ul> 
    2126<li> D - to a reformatted version of the discovery metadata harvested from the original data centre</li> 
     
    2429<li> B - if present, should link to a service allowing browsing of context metadata </li> 
    2530</ul> 
    26 Note that unless the original data provider is within the NERC DataGrid, A and B services are unlikely 
    27 to appear, although services with similar functionality may appear as R links. </p> 
    28  
     31Note that 
     32<ul><li> unless the original data provider is within the NERC DataGrid, A and B services are unlikely 
     33to appear, although services with similar functionality may appear as R links. </li> 
     34<li>the operators of this service have no control over the content, so there may be many rendering and other problems. Feel free to email us and let us know, and we'll try and get any such problems corrected. </li> 
     35</ul> 
Note: See TracChangeset for help on using the changeset viewer.