Why Update DAAC Landing Pages Project Motivation: Users are - PowerPoint PPT Presentation

Why Update DAAC Landing Pages Project Motivation: Users are becoming frustrated with the data access workflow currently in place on our data set landing pages. We have inadvertently contributed to the a lack of coherence in the user's workflow by presenting incomplete solutions or requiring users to obtain information, tools, and services from several different sites or locations. Users want to stay on our data set landing page to evaluate the data set and download the data. Vision: "Don't make me leave your site to get the data.” ( If I know what I want and I’m already on the data set landing page.) Targeting: High value data set landing pages

Prior Projects Data Reuse Landing Pages Building a Foundation

Data Transformation Concept Page (October 2017 UWG Meeting) (March 2018 UWG Telecon)

Prior Projects Data Reuse Landing Pages Building a Foundation

 NASA’s Common Metadata Repository (CMR) ❄ Access file metadata to filter data files and create data access URL lists  NASA’s Global Imagery Browse Service (GIBS) ❄ Using Blue Marble base layer  Incorporated Earthdata Login ❄ Required for data access ❄ Future plans to save searches, areas of interest, share data within NSIDC apps  Ordering System ❄ Icebridge Portal ordering backend extracted to a standalone system that can take orders from any compatible client application.

Prior Projects Data Reuse Landing Pages Building a Foundation

 Created file-level metadata for high value SSM/I- SSMIS data sets ❄ Why: Without file-level metadata, we could not enable the data access improvements planned for the landing pages ❄ Benefits: Users will be able to spatially and temporally filter data files within these data sets through NSIDC DAAC landing page and Earthdata Search

 New (or new uses of) Technology ❄ Landing page content managed as part of the NSIDC web site using Drupal Content Management System (CMS) ❄ Imbedding into Drupal pages. Custom module added to load Landing Page UI in the context of a landing page. This accomplishment paves the way for future integration of front-end applications with static web site content.  Ops Tools ❄ Robust customer support ❄ Status of CMR to determine if problems are internal or external ❄ Early detection of potential system problems like disk utilization ❄ Coming features: resubmit, queue prioritization optimization, auto suspend  Blink Study  User Input/Feedback

 Beta Version ❄ Releasing as a new “Beta” tab in mid -September in order to introduce users to new workflows without breaking the existing ones ❄ Phased rollout of data 5 sets to monitor performance  MODIS, SMAP, MEaSUREs  Remove Beta Label and Release 1.0 ❄ Internal development milestones reached ❄ Operational testing passes  Add additional data sets 1-2 week intervals ❄ MODIS, NISE, MEaSUREs