Data product specifications (Section 2.1)

• Identify user needs, data tools and services (Section 2.1)
• Select an open, community-standard machine-actionable data file format (Section 2.1 and 3)
• Define data file naming convention (Section 4.2.2)
• Follow standard variable names, units, and other relevant attributes (Section 4.2.3, 4.4, and 4.5)
• Select standard techniques for optimizing data storage and retrieval in data files (Section 5)

Data producers should establish contact with the assigned NASA Distributed Active Archive Center (DAAC) early in the product development lifecycle and work closely with the DAAC throughout the product development lifecycle, such as for 

• understanding DAAC ingest requirements and user needs,
• determining the appropriate data product Level of Service (LoS),
• data delivery and publication schedules,
• obtaining guidance on data file format and structure, metadata, etc. 

(See Section 1 of the DPDG document for a more complete list of areas that benefit from such close interaction). 

Earthdata Pub provides detailed information on data accession and publication processes, relevant to all lifecycle stages.

Metadata (Section 4)

• Define metadata elements for search, discovery and usage, following community standards, conventions, and vocabularies (Section 4, Appendix D and E)
• Define metadata for capturing data provenance and quality (Section 4.6.1, Appendix D.6)
• Define access and usage restriction and/or license (Appendix D.5)
• Identify associated knowledge to be preserved with data (Section 2.1)

DAAC assignment/interaction (Section 8)

• Submit a Data Accession request via Earthdata Pub to obtain DAAC assignment (Section 8)
• Determine Level of Service (LoS) (Section 8)
• Assess the necessity of an Interface Control Document (ICD) (Section 2.1)

Digital Object Identifier (DOI) for the data product (Section 7)

• Work with the assigned DAAC to reserve a DOI and include it in file metadata (Section 7)

Test and review (Section 2.3)

• Create sample data files (Section 2.3)
• Test them with metadata compliance checkers and identified tools and services (Section 2.4, 6.2, and 6.4)
• Have them reviewed by relevant DAAC(s) (Section 2.5)
• Carry out independent external review (Section 2.5)

Data Product User Guide/Readme (Section 4.1)

• Include data product title, version, DOI, variable name(s), spatial and temporal extents (Section 4.1.3)
• Describe the name and version of the algorithm (Section N/A)
• Describe the structure of the data file (Section 3.1 and 3.3)
• Include data usage license (Appendix D.5)
• Capture data product quality information (Section 4.5)
• Provide contact information, recommended citation, and acknowledgement (Appendix D.6.2, 4.5.2, and Appendix D.5)

A Readme file typically contains basic product information which should also be included in the data product metadata record in the Common Metadata Repository (CMR). 

The User Guide, containing more comprehensive details, is increasingly a preferred document. 

ATBDs provide detailed descriptions of the algorithm(s) used to create the data product(s). APT is a web-based application for authoring, managing, and publishing ATBDs.

Algorithm Theoretical Basis Document (ATBD) (Section 4.1)

• Describe algorithm theory, inputs/outputs, and quality assessment method and results (Section 4.1.3 and 4.5)
• Use ATBD Publication Tool (APT) or its templates (Section N/A)

Delivery(Section 8)

• Finalize appropriate LoS for the data product (Section 8)
• Go through DAAC’s ingest checklist if appropriate (Section 7 and 8)
• Prepare and finalize an ICD if advised by the DAAC (Section 2.1 and 4.5.1)
• Finalize data files and data packages and stage them as described in the ICD or advised by the DAAC (Section 4.5, 4.6, 4.7, and 5)

Publication (Section 8)

• Use Earthdata Pub (Section 8)
• Support the DAAC for publishing the data product (Section 8)