Editing How-To Guide for Implementing ESIP Federated Search Servers

Jump to: navigation, search

Warning: You are not logged in.

Your IP address will be recorded in this page's edit history.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 43: Line 43:
 
</pre>
 
</pre>
 
Note especially the <link> entry with type "application/opensearchdescription+xml".  This is the URL to the OpenSearch Description Document describing how to construct a URL to search for ML2CO.002 data.
 
Note especially the <link> entry with type "application/opensearchdescription+xml".  This is the URL to the OpenSearch Description Document describing how to construct a URL to search for ML2CO.002 data.
== Dataset Search OpenSearch Description Document ==
+
= Dataset Search OpenSearch Description Document ==
 
Once your have a dataset search that can return Atom results of the kind above, the next step is to create an OpenSearch Description Document for the dataset-level search.  Here is an example:
 
Once your have a dataset search that can return Atom results of the kind above, the next step is to create an OpenSearch Description Document for the dataset-level search.  Here is an example:
 
<pre>
 
<pre>
Line 60: Line 60:
 
This is probably the hardest aspect.  The Granule (or File) search engine should support queries based on some sort of dataset identifier, time and space (if appropriate).  Note however, that because of the way the 2-step search works, you can actually have different search engines for different datasets, say, if you have a specialized search algorithm for some data.  Also, if your data are global, you need not offer the spatial part of the search.  How does the client know which search engine, what dataset identifier to use and whether spatial criteria area allowed?  Easy, it's in the OpenSearch Description Document template described in the following section.
 
This is probably the hardest aspect.  The Granule (or File) search engine should support queries based on some sort of dataset identifier, time and space (if appropriate).  Note however, that because of the way the 2-step search works, you can actually have different search engines for different datasets, say, if you have a specialized search algorithm for some data.  Also, if your data are global, you need not offer the spatial part of the search.  How does the client know which search engine, what dataset identifier to use and whether spatial criteria area allowed?  Easy, it's in the OpenSearch Description Document template described in the following section.
  
 +
The response to the query should again be in Atom form.  Here is a partial example:
 
The response to the query should again be in Atom form.  Here is a partial example:
 
The response to the query should again be in Atom form.  Here is a partial example:
 
<pre>
 
<pre>

WikiText

'''Bold''' | ''Italic'' | [[Wiki Page Name| Text to show]] | [http://external link.com Text to show]
==Heading== | * Bullets list | # Number List | sign ~~~ | sign and date ~~~~

More Wiki Help
Please note that all contributions to Federation of Earth Science Information Partners are considered to be released under the GNU Free Documentation License 1.2 (see Federation of Earth Science Information Partners:Copyrights for details). If you don't want your writing to be edited mercilessly and redistributed at will, then don't submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. DO NOT SUBMIT COPYRIGHTED WORK WITHOUT PERMISSION!

Cancel | Editing help (opens in new window)
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox