1. ESIP Discovery – Show & Tell ESIP Summer Meeting 2011 Matt Cechini
ECHO & OpenSearch
ESIP Discovery – Show & Tell
ESIP Summer Meeting 2011
Matt Cechini

2. Outline Data Discovery & ECHO APIs OpenSearch’s Impact to ECHO
ECHO-ESIP Client
Future Activities

3. Data Discovery & the ECHO APIs
SOAP
Supports “legacy” SOAP data discovery & response format.
REST
Implements core discovery capability against index.
Dynamic metadata translation to ECHO 10, ISO 19115, & OS v1.0 Atom (XML & JSON-tentative)
OpenSearch
Supports OpenSearch request/response capability.
Future activity : Utilize dynamic format translation in ECHO REST API.
Future
REST
SOAP
OpenSearch
Search Index
ECHO XML DB
(Native Metadata & Spatial Index)

4. OpenSearch’s Impact to ECHO
Simple REST-ful Interface
Legacy SOAP interface had an inherently high learning and development curve due to technology
OpenSearch was ECHO’s first foray into a simple REST Interface
Quick & Simple to develop service on top of existing capabilities.
Provided a head start for eventual full REST API.
Increased Client Exposure
Significantly reduced development complexity
Broad usage of OpenSeach API allowed for quicker interoperability
Immediate response from client developer community
Mirador – GES DISC
SCS3 – GHRC
Mercury - ORNL
Simple Results Format
Simple results reduces the amount of data transferred to requesting client.
Reduced OpenSearch results vs. client application needs forces custom elements and opens the door for granule result scope creep.
Keyword Searching
Opened up the concept of an indexed textual search for ECHO metadata.
Required triage of all metadata fields to determine what should or should not be indexed.

5. ECHO-ESIP Client
ECHO-ESIP
Reference client exposing OpenSearch dataset & granule discovery.
Intended for ECHO Internal & External Validation Use

6. Future Activities Support OpenSearch 1.1 Specification
Support correct ‘rel’ attribute links
Support translation of all spatial types to Georss:Simple or GML
Provide MBR for all non-orbit granules.
Computing MBRs for new indexed searching capability
Move ECHO-ESIP to utilize ECHO REST API
Leverage ECHO translation of dataset & granule metadata to Atom OpenSearch format.
Leverage advanced keyword text searching
Provide result count in results
Investigate Reverb Usage
Utilize Atom OpenSearch format as the default response type for dataset & granule result lists
For performance reasons, response data may actually be a JSON representation of the Atom feed
Will require additional custom elements (e.g. LocalGranuleID & ArchiveCenter)
Unclear how orbit parameters will be represented, if required in results.
Data (Collection & Granule) Casting?
Leverage the ECHO REST API query capability & Atom conversion support