E OS C learing HO use

1. EOS ClearingHOuse Robin Pfister Code 423, NASA/GSFC robin.g.pfister@nasa.gov

2. Outline • What is ECHO? • Benefit to Science Users • Benefit to Providers • Using ECHO • Summary

3. Outline • What is ECHO? • Benefit to Science Users • Benefit to Providers • Using ECHO • Summary

4. What is ECHO? ECHO… • Is an Enabling Framework that allows interoperability among diverse and distributed, data, service and client systems • Is a metadata clearinghouse and order broker. In the near-future will also be a granule-level service broker • Is an Open System: Enabling a Collaborative Community

5. What is ECHO? Prior to ECHO… • Users wanting cross-DAAC access to data were confined to a single user interface (EDG) built as a one-size-fits-all solution • Search and retrieval data access paradigm, searches were executed at the archives. Performance was not optimized with this architecture EOSDIS Data Providers EOS Data Gateway Inventory Metadata Catalog Collection Metadata Catalog & Interoperability Middleware Browse Images WWW Browsers User Interface Messages: Search, Browse & Order Data Holdings

6. What is ECHO? User Interface With ECHO… • Individuals and communities can share data, services and tools • Scientists save time by using tools tailored for their data access needs, cutting out unnecessary steps in the data access process ECHO EDG & Other Clients: Machine - Machine & Human - Machine Data & Service Providers - Any Collection & Inventory Catalog + Sample Images Data Holdings Provider APIs Client APIs WWW Browsers Orders Search, Browse & Order Requests Service & Order Broker

7. What is ECHO? ECHO P R O V I D E R A P I C L I E N T A P I Clearinghouse Catalog Order & Service Brokers SERVICE API Client Extensibility Data Extensibility • Graphical User Interfaces (applets, active pages, etc.) • Machine-to-Machine Interfaces • New Data Partners • - Can establish policies for their own data • New Collections/Data Types • Access Mechanisms • Types of services: • Data Services: e.g. • collection, subsetting • Search Services: e.g. • gazetteer, thesaurus (future) • Administrative Services: • e.g. accounting (future) • Service interactions: • Order Options • Advertised • - Context Passing (future) • - Brokered (future) Service Extensibility Views: - Service View - Data View

8. What is ECHO? Data Providers (Grid and non-GRID Client Providers Other Federated Systems Future Future Interoperable User Interface Functions In progress Interoperable Service Providers (Grid and non-GRID) Systems of diverse standards and protocols can interoperate through standards mapping in ECHO V0 Protocol XML XML SOAP SOAP ECHO OGC SOAP XML SOAP UDDI XML XML WSDL

9. Outline • What is ECHO? • Benefit to Science Users • Benefit to Providers • Using ECHO • Summary

10. Benefit to Science Users Alternate User Interfaces • ECHO provides flexibility in supporting new data access paradigms and tailored clients to optimize the data access process. Alternate interfaces in progress • Mercury EOS - (built by ORNL) • MODIS Websites (via ORNL shopping cart-demo) - In testing, (built by MODIS, ORNL & ESDIS) • Power User Interface (script based) - In testing (built by ESDIS) • Data Validation User Interface (DVUI) Prototype for MODIS Land Data Validation, going into operations • NEO (New Earth Observer) (NASA/GSFC) • DODS (University of Rhode Island) • GISMO (University of Colorado at Boulder, under development) • NEpster (NASA/GSFC) • EDG (ESDIS, under development) • SNOWI-E - For internal use, National Snow and Ice Data Center, Distributed Active Archive Center (under development) • SIMECC - GSFC Simple MODIS ECHO Client (under development) • Invasive Species Data Service (in formulation)

11. Benefit to Science Users • Data Validation User Interface (DVUI) Prototype for MODIS Land Data Validation, going into operations

12. Benefit to Science Users Data Providers to ECHO • Operational Data Providers • Oak Ridge National Laboratory (ORNL) • Data Providers Readying for Operations • GES DAAC - GSFC Earth Sciences, Distributed Active Archive Center • LARC DAAC - Langley Research Center, Distributed Active Archive Center • LP DAAC - Land Processes, Distributed Active Archive Center • NSIDC DAAC - National Snow and Ice Data Center, Distributed Active Archive Center • ORNL DAAC - Oak Ridge National Laboratory, Distributed Active Archive Center • SEDAC - Socioeconomic Data and Applications Center • Others in negotiation

13. Benefit to Science Users Summary of user benefits • Scientists have more options in data and service access • Scientists can save time: • Through optimized clients. (The DVUI was an example of how data access time was reduced from a few days to an hour or so) • Through improved System Availability • Scientists will be relieved of the burden of getting data, finding and downloading software to perform services and applying services themselves. This will all be brokered for them at the data granule (or dataset level if applicable).

14. Outline • What is ECHO? • Benefit to Science Users • Benefit to Providers • Using ECHO • Summary

15. Benefit to Providers Reminder: Direct Users of ECHO are Providers - DEVELOPERS SCIENCE USER DEVELOPER Enables developers to create & plug-in clients, data or services Enables science users to find & use data & services Data Provider Client Provider Service Provider

16. Benefit to Providers Data Providers • Reduces system workload by removing search loads. Saves money in hardware, software and operations staff • Allows flexibility to support community-specific services and functionality • Visibility control at both a dataset, and granule level • Standards compliance through mapping layers (e.g. ISO Compliance) • Metadata correction through mapping layers • Wider reach of developed technologies • Increased opportunity for technology infusion

17. Benefit to Providers Client Providers • Enables better support of their science users through more varied and flexible data access options and capabilities • Improves system availability • Represents all of ECHO’s metadata holdings as if they were managed directly by the client without the hassle of interacting with multiple providers • Provides a common metadata model • Can provide more accuracy in results sets through ECHO’s flexible spatial searching

18. Outline • What is ECHO? • Benefit to Science Users • Benefit to Providers • Using ECHO • Summary

19. Using ECHO • Participating in ECHO • As a Data Provider • Active Metadata Provider • Passive Metadata Provider • Distributed Search Provider • As a Client Provider • As A Service Provider • Comprehensive System (all of the above) • Re-use of ECHO as a separate clearinghouse • Interoperable or Standalone system • Paperwork for NASA approval for reuse of ECHO is being processed

20. Using ECHO • Participating in ECHO • As a Data Provider • Active Metadata Provider • Passive Metadata Provider • Distributed Search Provider • As a Client Provider • As A Service Provider • Comprehensive System (all of the above) • Re-use of ECHO as a separate clearinghouse • Interoperable or Standalone system • Paperwork for NASA approval for reuse of ECHO is being processed • How a provider participates depends on • network availability • how much metadata is being conveyed • how often metadata needs to be refreshed • other factors • Performance studies have not yet been performed to determine guidelines for participation

21. Using ECHO • Participating in ECHO • As a Data Provider • Active Metadata Provider • Passive Metadata Provider • Distributed Search Provider • As a Client Provider • As A Service Provider • Comprehensive System (all of the above) • Re-use of ECHO as a separate clearinghouse • Interoperable or Standalone system • Paperwork for NASA approval for reuse of ECHO is being processed • Provides metadata and updates on a regular basis • Manages the representation of their data holdings themselves (e.g. access control) • Provides a mechanism to accept orders and provide order status

22. Using ECHO • Participating in ECHO • As a Data Provider • Active Metadata Provider • Passive Metadata Provider • Distributed Search Provider • As a Client Provider • As A Service Provider • Comprehensive System (all of the above) • Re-use of ECHO as a separate clearinghouse • Interoperable or Standalone system • Paperwork for NASA approval for reuse of ECHO is being processed • Enables harvesting of metadata by ECHO (capability to harvest is not yet developed in ECHO)

23. Using ECHO • Participating in ECHO • As a Data Provider • Active Metadata Provider • Passive Metadata Provider • Distributed Search Provider • As a Client Provider • As A Service Provider • Comprehensive System (all of the above) • Re-use of ECHO as a separate clearinghouse • Interoperable or Standalone system • Paperwork for NASA approval for reuse of ECHO is being processed • Use only as necessary (technical factors) • Bound by limitations of distributed searching • Protocols currently supported: • ECHO Native • Version 0 (complete by September 2004; needed to support EDG access)

24. Using ECHO • Participating in ECHO • As a Data Provider • Active Metadata Provider • Passive Metadata Provider • Distributed Search Provider • As a Client Provider • As A Service Provider • Comprehensive System (all of the above) • Re-use of ECHO as a separate clearinghouse • Interoperable or Standalone system • Paperwork for NASA approval for reuse of ECHO is being processed • You can provide your own view of ECHO holdings by leveraging the APIs on the clearinghouse

25. Using ECHO • Participating in ECHO • As a Data Provider • Active Metadata Provider • Passive Metadata Provider • Distributed Search Provider • As a Client Provider • As A Service Provider • Comprehensive System (all of the above) • Re-use of ECHO as a separate clearinghouse • Interoperable or Standalone system • Paperwork for NASA approval for reuse of ECHO is being processed • In the future you can provide a service in such a way that it is linked to applicable data, at the granule-level • Reduces burden on user to find and apply services to data • Phase 1 of this capability will be in ECHO 6.0 to include: • Registration of service • Advertising • Coupling of services with applicable data

26. Using ECHO • Participating in ECHO • As a Data Provider • Active Metadata Provider • Passive Metadata Provider • Distributed Search Provider • As a Client Provider • As A Service Provider • Comprehensive System (all of the above) • Re-use of ECHO as a separate clearinghouse • Interoperable or Standalone system • Paperwork for NASA approval for reuse of ECHO is being processed • You can provide an entirely new data system that combines existing data and services, along with those you provide, using ECHO as the infrastructure • This would be a ‘view’ created by your application (or client) that ties a tailored view of data and services for a particular discipline or purpose

27. Using ECHO • Participating in ECHO • As a Data Provider • Active Metadata Provider • Passive Metadata Provider • Distributed Search Provider • As a Client Provider • As A Service Provider • Comprehensive System (all of the above) • Re-use of ECHO as a separate clearinghouse • Interoperable or Standalone system • Paperwork for NASA approval for reuse of ECHO is being processed

28. Outline • What is ECHO? • Benefit to Science Users • Benefit to Providers • Using ECHO • Summary

29. ECHO Summary • ECHO… • Is an enabling framework that provides increased flexibility, efficiency, extensibility and interoperability. • Enables sharing and interoperability of data, services, clients and other tools that operate at a granule or dataset level. • Operational and continues to evolve through incremental releases to incorporate planned capabilities • Extendable to a wide range of other applications making it a good candidate for reuse and commercialization

30. ECHO Summary • ECHO… • We would like to find a way to put this out as open source. • We would like to find someone to collaborate with on building OGC proxies and other mappings to support CEOS Standards (e.g. CIP). • We would also like to collaborate with the Grid community to determine interoperability requirements across Grid systems.

31. ECHO Summary • 5.0 is Operational. Several new capabilities include: Provider Data Management Tools Provider User Management Tools (e.g. access control manipulation Metadata Reconciliation Support Tools • 5.5 is going to External Test soon, includes: • Orbit-Based Searching • 6.0 is starting development, includes: • Phase 1 Services EDG Transition is targeted to complete by September ‘04 • For EDG providers who choose to NOT participate in ECHO, the distributed search capability will be moved to ECHO which will still support the V0 protocols for distributed searching. • Participation in ECHO is preferable http://eos.nasa.gov/echo