Solutions Master List (for ESDIS Review)

1

Facilitate DAAC - PI Communication;

Support Metadata Creation (dataset-level)

1. Confidence in metadata accuracy
2. Quick and easy to provide metadata
3. Metadata completeness

1. DAACs
2. MEaSUREs PIs
3. NASA Flight Mission Science Data Systems
4. Science Mission PIs
5. ESDIS (GCMD/CMR)

A

Metadata for current ASDC (BEDI identified) data products has been imported into the CAMP Database and are within weeks of being validated by science teams. Depending on required CMR fields, there may be fields added.

5

This is dependent on the completion of CMR efforts.

4

https://camp.larc.nasa.gov/

2

Metadata Compliance Checker (PO.DAAC)

Provides tool for both DAACs and Data Producers to evaluate metadata standards compliance at granule level. Multiple forms of compliance check: ACDD, CF, ... quality flags, completeness/compliance, ...netCDF/HDF/OPeNDAP, Target at data producers as major user community. Output report from the checker will contain useful information and be exposed to end users? validate time against ISO 8601

Standards Compliance Checking and Reporting (granule-level);

Support Metadata Creation (granule-level)

Capturing;

Enabling Use

1. DAACs
2. MEaSUREs PIs
3. NASA Flight Mission Science Data Systems

4

Operational and available for the public to use.

Undergoing Beta testing. Issues have been identified that need to be addressed.

2

Efforts

1

User interface is friendly and easy to use. It will be ideal if the report can be more descriptive.

Options

3

Provides open web form for metadata entry by data producer which is interfaced with a backend metadata archive database maintained by the data center.

Note: Whether this resource/tool is developed directly by ESDIS or by a DAAC, the important aspect is that the DAAC must have immediate access to the metadata that is input by this tool for the purpose of verifying accuracy and completeness.

Support Metadata Creation (dataset-level);

Standards Compliance Checking and Reporting (dataset-level);

1. DAACs
2. MEaSUREs PIs
3. NASA Flight Mission Science Data Systems
4. ESDIS (GCMD/CMR)

4

Operational and available for public use.

3

Software for backend and front-end GUI is proprietary to NOAA, but we can look at the front-end GUI as a model and make the interface compatible with existing ESDIS and DAAC data/metadata systems (e.g., CMR, ISO 19115, ISO 19157, etc...).

1

User interface may require initial training for familiarity of terms and various metadata fields, but once familiarity is established the ease of use should be relatively straightforward with an expected turnaround time of 1 30 minutes to 1 hour after proficiency with the interface is established.

Options

4

Facilitate DAAC - PI Communication;

Support Metadata Creation (dataset-level);

1. DAACs
2. MEaSUREs PIs
3. NASA Flight Mission Science Data Systems

3

Quasi-operational as source-code exists and seems to be ready for use,  but cannot locate an operational instance of this on a web page. Will likely need to be evaluated by the wider ESDIS community, other DAACs and MEaSUREs PIs for long-term community acceptance and adoption.

First release is currently operational at the ORNL DAAC internally.

2

Software for backend and front-end GUI made available on the ESDIS GIT server. Requires Drupal to be installed on a web server. There is currently no explicit inclusion of data quality information or metadata with this tool, so further work would need to be done in that regard.

1

This is a best-guess based upon that this is seems to be at least a partially automated workflow and assumes the GUI interface is straightforward to use. This may need to be re-evaluated once an operational instance of this tool is made available to test.

https://git.earthdata.nasa.gov/projects/DAACSUB/repos/daac-ingest-dashboard/browse

ORNL DAAC Ingest Automation Swimlanes

Presentation at 2015 ESIP Summer Meeting

Need to scope this out further through direct communication with Daine Wright to evaluate an existing operational implementation of this tool.

Demonstrate current capabilities of the ORNL DAAC IA Dashboard across ESDIS.

5

Collection-level metadata collection form developed by ORNL for oceanic in situ observation datasets tailored for CO2 collection. Could potentially be extended to include satellite datasets.

Same as the metadata editor in the ORNL DAAC Ingest Automation System

Capturing;

Describing

1. DAACs
2. MEaSUREs PIs
3. NASA Flight Mission Science Data Systems
4. ESDIS (GCMD/CMR)

4

Operational and available for public use.

2

Software for backend and front-end GUI is proprietary to ORNL. Currently only supports in situ observational datasets, but could potentially support airborne. Not immediately clear how much work could be involved in extending this to satellite remote sensing datasets. GUI can be thought of as a model (in concert with ATRAC) for how metadata can be collected from data producers.

1

User interface may require initial training for familiarity of terms and various metadata fields, but once familiarity is established the ease of use should be relatively straightforward with an expected turnaround time of 1 30 minutes to 1 hour after proficiency with the interface is established.

6

Guidance,  Instruction, and Dissemination (for data users)

Capturing;

Describing;

Enabling Use

1. DAACs
2. MEaSUREs PIs
3. NASA Flight Mission Science Data Systems

2

The scale guide does not apply directly in this case. However, as indicated in the URL reference column, there are several models for data quality guides one can start from to develop a few  common templates

5

Integration implies broad adoption by the community, given the fact that the templates have been developed.

3

Development of common templates should be relatively easy.

1. http://docserver.gesdisc.eosdis.nasa.gov/repository/Mission/AIRS/3.3_ScienceDataProductDocumentation/3.3.5_ProductQuality/V6_L2_Quality_Control_and_Error_Estimation.pdf
2. https://eosweb.larc.nasa.gov/project/ceres/quality_summaries/CER_SSF_Terra_Edition3A.pdf
3. http://ceres.larc.nasa.gov/dqs.php
4. https://lpdaac.usgs.gov/sites/default/files/public/modis/docs/MODIS_LP_QA_Tutorial-1b.pdf
5. https://globalmonitoring.sdstate.edu/sites/default/files/QA_paper.pdf
6. http://modis-atmos.gsfc.nasa.gov/_docs/QA_Plan_C6_Master_2015_05_05.pdf

7

A Science Data WG, including participants (funded by the project) from data centers (ORNL DAAC and ASDC) and different research groups, was formed in the ACT-America project to 1) coordinate data management activities with instrument teams, modelers, remote sensing, and external data sources and 2) ensure data, products, and information required to address science questions are available in harmonized forms when needed. Telecons are held periodically to exchange any data-related thoughts between research groups and the data centers.

Currently solution is applicable to modeling (ORNL DAAC) and Airborne observations (ASDC) components of ACT-America data management; But can be applicable to others.

1. Coordinate data management activities with instrument teams, modelers, remote sensing, and external data sources

2. Ensure data, products, and information required to address science questions are available in harmonized forms when needed.

Capturing;

Describing

1. DAACs
2. MEaSUREs PIs
3. NASA Flight Mission Science Data Systems
4. ESDIS

5

The Science Data WG set up monthly telecons and has been providing significant contributions onto the modeling protocol for ACT-America. It provides a platform for domain researchers and data experts to exchange ideas and coordinate data flows and work schedules.

5

Both research projects (e.g. MEaSUREs and EVS-2) and DAACs need funding and FTE resources to support these activities.

1

Once resources are secured, it's easy to set up the WG and conduct activities.

8

Data Quality Information (science perspective);

Guidance, Instruction, and Dissemination

1. Provides early adopters to data products from NASA Earth Science remote sensing projects.
2. Provides beta testers for MEaSUREs ESDRs.

Capturing;

Describing;

Enabling Use

1. DAACs
2. MEaSUREs PIs
3. NASA Flight Mission Science Data Systems
4. ESDIS

1

Does not exist unless there is in fact a review board or committee provided by NASA at project start

2

Science Team established at project start and communicated to DAAC.

9

Guidance,  Instruction, and Dissemination (for data producers and DAACs);

Facilitate DAAC - PI Communication;

Dissemination on Data Quality Information;

Capturing;

Describing

1. MEaSUREs PIs
2. NASA Flight Mission Science Data Systems
3. DAACs

4

Requirements exist for DMPs to be generated by funded entities (PI's and projects). DMP Guidelines are provided by HQ, and call for addressing data quality information. They do not ask for a separate section explicitly.

2

When the PI's and projects do include data quality information in the DMPs, it will be relatively easy for DAACs to work with the PI's and projects to integrate the information into the data systems

4

In practice there is considerable variation among DMPs that have been developed.Broader adoption will involve "blessing" by the responsible Program Scientists and Program Managers.

1) Modify the guidance of a program to include better instructions on data quality section development

2) DAACs to review the DMP, including the data quality section

10

DAACs DMP (or Data Management Guidlines)

Some DAACs (e.g., PODAAC,SEDAC, ...) write their own DMPs for specific datasets or a collection of datasets for the purpose of managing datasets throughout their lifecycle. PO.DAAC is currently finalizing a standardized template for the DAAC-specific DMP. The SEDAC Data Nomination template is used internally and contains sections to capture data quality information.

The ORNL DAAC doesn't have DMPs for specific datasets. Instead, it provides general guidance for data providers to conduct data management and prepare for data archival.

Guidance,  Instruction, and Dissemination (for data producers and DAACs);

Facilitate DAAC - PI Communication

Capturing;

Describing

1. DAACs
2. ESDIS
3. PIs/ NASA Flight Mission Science Data Systems

3

The SEDAC data nomination template was approved by the UWG. Would need to invite other DAACs to review this to see if it would be suitable for all DAACs. Would also be useful to compare and contrast with DMPs used at other DAACs, such as PO.DAAC.

4

Adoption, review, and approval could take 4-6 months, depending on how it is integrated into existing procedures.

2

This assumes a starting template is established, although DMPs typically require multiple back and forth iterations between the DAAC and Data Producer. Also assumes DAAC and Data Producers to not have competing time schedules, in which case this should not take more than 1 month to complete.

ORNL DAAC

1. DAAC determines how DMP template will be used.
2. Customize sections or questions.
3. DMPs can be used to accommodate multiple datasets from a data Producer.
4. Obtain approvals.

11

Kayako

User Services (Help Desk);

Knowledgebase (for data users)

Kayako provides an integrated system for ESDIS and individual DAACS to easily track and coordinate user questions and feedbacks related to data products, websites, tools, etc.

It also allows individual DAACs to easily compile knowledge bases and FAQs by pulling past user support records from Kayako system.

Describing;

Facilitating Discovery;

Enabling Use

1. DAACs

5

It has been operational across a number of DAACs, including ORNL DAAC and PO.DAAC.

3

DAACs need to coordinate with Kayako coordinator at ESDIS and modify their websites and applications to be integrated into the centralized system.

2

A coordinator may be needed in each DAAC to dispatch user questions to persons who are most suitable to take care of the questions.

Contact US on http://daac.ornl.gov/ and http://daymet.ornl.gov/

https://support.earthdata.nasa.gov

Compare Kayako with other solutions?

UserVoice might be comparable.

Add other relevant solutions (e.g. Forums) into this table.

NSIDC User Services uses ZenDesk

12

Daymet Website

Data quality information (program-specific collection);

Daymet website can be considered as one way to convey data product, including quality, information to data users.

Daymet is becoming probably the most popularly used data product recently. The Daymet website helps a lot, even though it's hard to quantify its impact on this popularity.

1. DAACs
2. MEaSUREs PIs

5

The Daymet website has been operational and available to the public for a few years.

5

It takes a fair amount of resources and time for both the Daymet PIs and the ORNL DAAC to work together, compile information, develop tools, and set up the Daymet website.

2

Once the website is set up, it requires medium effort to maintain and keep the information updated.

13

Identify different ways in which DAACs are conveying data quality information

Data quality information (dataset-level);

Different approaches for data quality information (dataset-level)

Describing;

Facilitating Discovery

1. DAACs

1

This is a survey activity that should result in a document. The activity has not been started, but the information exists at each of the DAACs.

4

Integration here means taking the results of the report and implementing changes at the DAACs to conform to the recommendations. The time involved will depend on the workload at the DAACs and priorities.

4

It should be possible to complete the survey and develop a report in 2 to 4 months.

14

Populate a set of FAQs for each new data set upon release by anticipating possible questions that users might ask. From FAQ, identify data sets receiving excessive questions as those to be considered for dissemination of additional or enhanced documentation.

User Services (Help Desk);

Knowledgebase (for data users)

Describing;

Facilitating Discovery;

Enabling Use

1. DAACs

5

UserVoice is fully operational at SEDAC.

3

After purchase, integration and backfill could be completed quickly.

3

Implementation could be quick, prior to backfill.

1. DAAC purchases service.
2. DAAC establishes links from webpages to service.
3. DAAC backfills FAQ with previous questions & answers.
   *Kayako might be a comparable solution for some DAACs

15

Provides DAACs a tool to understand quality attributes for overall documentation to product validation.

Provides Users a tool to better understand how data decisions regarding quality were established.

Capturing;

Facilitating Discovery;

Enabling Use

1. DAACs
2. NASA Flight Mission Science Data Systems

4

Operational and available for the public to use.

2

No effort is needed for integration if other DAACs/PIs want to use the tool with the current set of standards supported. Medium effort will be needed if they want to set up their own instances without changing current project support.

2

Assumption/Unknown

16

Guidance and instruction;

Data quality and information

Capturing;

Describing;

Enabling Use

1. DAACs
2. MEaSUREs PIs
3. NASA Flight Mission Science Data Systems
4. Other data producers

4. Straightforward to integrate as the generic flagging attributes encompass nearly all quality screening use cases.

17

Data quality and information;

User Services

Describing;

Facilitating Discovery

1. DAACs

3

Unclear if this type of information is provided in documents across the DAACs

3

Information from the PI or data set creator will need to be collected. This level of information may not be readily available. Effort level may be medium to difficult depending on the information available

2

If documentation for the data set already exists, it should be medium effort to add additional text

http://nsidc.org/data/docs/daac/smap/sp_l2_smp/index.html#errorsource

(would be good to get examples from other DAACs)

18

LP DAAC Project Lifecycle Plan (PLP)

This document is written from the point of view of the LP DAAC, advocators for products as they move through the lifecycle from Inception to Active
Archive to Long Term Archive, and advocators of products that adhere to interoperability standards.

Product capture is the first step in providing community-wide access to data and information.

PO.DAAC has a very similar policy that covers a series of project lifecycle planning documents and artifacts known as the "Dataset Lifecycle Policy".

Capturing;

Describing;

Enabling Use

1. DAACs
2. MEaSUREs PIs
3. NASA Flight Mission Science Data Systems
4. ESDIS

3

The PLP is published and currently in use at LP DAAC.

The PLP would need to be updated to include quality elements, and to generalize for all DAACs.

2

DAAC Integration at the start of the project.

2

Update general process for each location, and update the Collection Inception Checklist for specific center factors.

http://pubs.usgs.gov/of/2014/1139/pdf/ofr2014-1139.pdf

http://podaac.jpl.nasa.gov/PO.DAAC_DataManagementPractices#Dataset%20Lifecycle

19

Capturing;

Describing

5

Operational and available for public use.

2

Software is on Github. Created using Eclipse 4.5.0, Google Web Toolkit 2.7.0 and Java 1.7.0.79

1

Modification would require some level of effort which could be assessed by looking at the code

20

Guidance and instruction; Metadata creation support

Capturing;

Describing;

Enabling Use

4

https://geo-ide.noaa.gov/wiki/index.php?title=ISO_Data_Quality

ECHO Data Quality Metadata in ISO

21

Capturing;

Describing

22

Capturing;

Describing;

Facilitating Discovery;

Enabling Use

1. DAACs

2. MEaSUREs PIs

3. NASA Flight Mission Science Data Systems

SW: 5

Operational and available for public use.

Doc: 3

Associated documentation is open source and has undergone internal peer review by DIWG and CF group members.

2

Software binaries and builds are available for Linux/Unix, Mac OSX/Darwin, and Windows OS. Higher level scripting may be needed to automate the NCO utilities for specific datasets to enable bulk processing.

2

User will need to familiarize themselves with the various command line options as well as basic file structures of netCDF and HDF.

23

Capturing;

Describing;

Enabling Use

24

User Services (Help Desk);

Knowledgebase (for data users)

Capturing;

Describing;

Facilitating Discovery;

Enabling Use

1. DAACs
2. MEaSUREs PIs
3. NASA Flight Mission Science Data Systems
4. Other data producers
5. Data users

5

Operational and available for the public to use.

2

Integrated through URS and Kayako, thus enabling other DAACs who utilize either URS or Kayako to more easily integrate this service.

2

Works like most other online web forums and requires very little training to use.

Requires URS.

Kayako is an optional 3rd party service that this supports.

25

Data Quality Information Representation;

Guidance, Instruction, & Dissemination

Capturing;

Describing;

Facilitating Discovery;

Enabling Use

1. DAACs
2. MEaSUREs PIs
3. Data Users

5

4

Can be configured for other satellite missions with self describing files and appropriate CF metadata

2

*Requires one python dependency that's not in the base installation