[Go-essp-tech] [ESGF-Search] Opensearch and XML representation of a search query

[stephen.pascoe at stfc.ac.uk]

Thanks Chris and Matt,

It's great to have such high-quality info up-front and these ESIP patterns look very interesting.

As Mark said previously, what I think we are aiming at is a first-draft search API that isn't tied to an implementation (e.g. SOLr) without over-implementing for the sake of following standards.

Cheers,
Stephen.

---
Stephen Pascoe  +44 (0)1235 445980
Centre of Environmental Data Archival
STFC Rutherford Appleton Laboratory, Harwell Oxford, Didcot OX11 0QX, UK


-----Original Message-----
From: Lynnes, Christopher S. (GSFC-6102) [mailto:christopher.s.lynnes at nasa.gov] 
Sent: 08 June 2011 15:16
To: Pascoe, Stephen (STFC,RAL,RALSP)
Cc: Cinquini, Luca; Mattmann, Chris A; go-essp-tech at ucar.edu
Subject: Re: [Go-essp-tech] [ESGF-Search] Opensearch and XML representation of a search query

BTW, on a technical note, the ESIP Federated Search convention can be summed up (mostly) as follows:

(1) Currently, we stick to the Atom response type, but there is pressure to add RSS.

(2) We adopt the draft Spatial and Temporal extensions to OpenSearch.

(3) We use a recursive mechanism to link dataset-level searches to file-level searches. The response to an OpenSearch request for datasets is expected to include links to OpenSearch Description Documents (OSDD) for the respective file-level searches for each dataset.  In practice, this usually means generating the file-search OSDD on the fly with the dataset identifier already "filled in" in the search template.  (Of course if you are only doing dataset-level or file-level searches, this is irrelevant.)

(4) We are trying to canonicalize the links in the response (using the "rel" attribute) to make them less ambiguous to clients, i.e., which one is the link to the data file, vs. the link to the metadata file, etc.
--
Dr. Christopher Lynnes     NASA/GSFC, Code 610.2    phone: 301-614-5185


-- 
Scanned by iCritical.