Evolving the EOSDIS Information Architecture a.k.a. Coherent Web

1. Evolving the EOSDIS Information Architecturea.k.a. Coherent Web Kevin MurphyAugust 26, 2010

2. Context • NASA Earth Science Data Systems are a large and continuing investment in science data management activities • Websites are the front door to our data and services for users (science, programmatic, missions, citizen scientist, etc…), but are currently underutilized and discordant • How do we present ourselves to be a coherent system of systems while remaining flexible to integrate new missions and technologies and remain relevant • We must preserve what we currently do very well

3. Current Earth Science Links • Earth Science Data • Getting Earth Science Data • EOSDIS • Link to: EOSDIS (ESDIS Project link) • Link to: Earth Science Data Centers (HQ) • Data and Information Policy • Link to: USGCRP & IEOS (external) • Link to: Read our Data Policy(HQ) • Link to: Mission Data system Requirements (HQ) • Information about data • Data Levels • Link to: Detailed definition of data levels (HQ) • Link to: Data Maturity Levels (HQ) • Data System Standards • Link to: List of Approved Standards • About Earth Science Data Systems Program • Core and Community Data System Elements • Data System Evolution Activities • Link to: Decadal Survey Data Systems Links/sites Actual Future Proposed Key HQ ESDS ESDIS • Earth • Earth Science at NASA • Earth Science Data • Decadal Survey • Etc. • ESDSWG • Working groups • Projects • - ACCESS • - MEaSUREs • - REASoN Data Systems Planning • ESDIS Web Site • ESDIS pages as-is • ESDIS Data System Documents • Plans • Interfaces • DSDS • DSDS web site • DSPG • DSPG web site WIKI?

4. Inspiration Examples Powered By Powered By Powered By Lesson: Content management system helped unify the message of National Geographic across 20+ departments/branches Lesson: Hosting and maintenance of web applications can be separated from the user interface and the UI can still be immersive and useful for users (aside from the whole social networking fad ;-)

5. Process • Realization • Community discussion • Rob Covey (Nat. Geo.) • DAAC manager working group sessions and report • Pre-Formulation • Today…Next steps?

6. Goals • Present EOSDIS as a coherent yet transparent system of systems by leveraging SOAs provided by DAACs, ECHO, GCMD, EMS, User Reg…. New missions, technology and partnerships • Users navigate the system without needing to know how/who is providing each service. • DAAC web sites and services still exist, but use the same high-level navigation, nomenclature and other functionalities so users are familiar when they arrive. • More than just a website or portal • An active and immersive user experience leveraging existing and future Web Services (e.g. W*S, SOAP, RESTful) into a seamless package – search, subset, visualize and deliver data in one session with one username and password while invoking multiple remotely hosted tools • Cloud capable • Fresh and continually updated and coordinated content One Site Leveraging Multiple Remote Services Presented as a Coherent System of Systems Login Content Search/Browse Subset/Reformat Visualize Deliver MRTWeb Giovanni GCMD and ECHO DMAS DAACs User Reg. Chained Services

7. Grossly simplified mockup Standards for new missions Powered by User Reg. EOSDIS Welcome Back Kevin (not Kevin – Sign In) Uniform Top Hat Nav. ROSES HOME | ABOUT | PRODUCTS | GET DATA | TOOLS | USER COMMUNITY | SUPPORT | LABS ABOUT Project | Program | DAACs | Research | Architecture | Metrics | Open Solicitations Browse Data Sets Measurement Veg. Index (30) Sea Ice (15) Platform Aqua (275) Terra (350) Flux Tower (127) Project Spatial Coverage Near-Real-Time EOSDIS Watch This Week Downlinks 123 NRT Latency Archived Sci Files .. This Year xxxx xxxx Totals xxxx xxxx xxxx Powered by ECHO Story of the Day/Week Links to data sources embedded Powered by (Earth Observatory | Rapid Fire | DAAC User Services) Powered by EMS Powered by LANCE, Outreach, etc Powered by GCMD Keyword Search 1 2 3 Land Cover News, Events and Notices --MODIS Collection 6 Status --LEPSEC Issue with AQUA --?? --Download Apps (iPhone, Android) Science Spotlight Ice Blog Atmosphere Blog Search Powered by DAAC Scientists DataCasting GeoRSS Powered by DAAC CMS Feeds Motto: So easy, Dawn can do it.

8. Architectural Concept NASA HQ Site EOSDIS WEB SITE External Sites (Earth Observer, Climate, USGS, NOAA) Content Management System Application Server Middleware Invoke DAAC Specific Services Reuse/Repurpose/Integrate Content Utilize EOSDIS-Wide Services Outreach ECHO (gran search) Rapid Response SIPS Subsetter GCMD (keyword search) ESDSWG Community Directed Infusion DAAC DAAC DAAC DAAC ACCESS Infusion User Reg ESDIS LANCE Web Services EMS DAACs (maintain web sites but implement CMS so they can feed content to ESDS site) WCS WMS GeoRSS KML VizTool(s) Others

9. Phasing – straw-man Phase/Release 1 Phase/Release 2 Phase/Release n CMS ECHO GCMD ESDSWG/ Community DS Viz Reformat EOSDIS Web Site USR Reg. EMS DataCasting/GeoRSS LANCE Reprojection Subsets • Develop content management system infrastructure/expertise • Converge and implement uniform navigation • Implement some cross-DAAC functionality • Chain available web services so they behave as a single entity • Limited social networking • Mobile accessibility • Integration of FY10 tech. infusion projects • Harvest data from DAAC CMSs • Web center of excellence • Transparent user experience Objectives • Uniform top hat nav. • Expose web services • Cross DAAC web content search • Integrated User Reg. • Expose additional web services • Formulate nomenclature • Implement CMSs • Support visualization tool • Widely available W*S • ISO… DAACs

10. Does this Vision Resonate? • Refine vision and phasing • Near-term steps • Develop and deploy brochure Earth Science Data System site • Choose URL • Develop infrastructure • Formulate DAAC information architecture working group and begin converging

11. Working Group Defined Objectives • Increase use of NASA Earth science data and services • Encourage interdisciplinary researchers to find and use the data they need • interoperable data and services • reduce barriers to non-expert users – e.g. MISR expert wanting to use LIDAR • Actively experiment with technology and presentation • being in front and not following others • realize when something does not work and move to something else • Web services – separating the content from the display - platform for displaying current capabilities • Enable community engagement • Increase ACSI survey scores

12. Working Group Recommendations • Develop a coherent web presence for the Earth Science Data System Program from top-to-bottom (HQ-EOSDIS-DAACs) • Better represent EOSDIS programmatic investments and capabilities • Have data centers more clearly represented as elements of a larger system • Facilitate multidisciplinary research and data integration • Quickly respond to emerging environmental issues with the wealth of data at our disposal (earthquakes, volcanoes, etc…) • Provide a platform for demonstration of interoperability throughout all of our systems • Don’t lose sight of what we do well now • Data centers (DAACs) are experts and need to tailor content and services to their users, thus they must maintain websites • DAACs are related to other NASA Earth Science Programs and this relationship should be shown