|
|
| The ROSES 2022
Planetary Data Archiving and Restoration (PDAR) Program
Appendix C.4
|
 |
| Notice: This year the program will not be soliciting proposals for the
development or validation of software tools. |
| |
| This program element does not have a proposal due date. Proposals may be submitted at any time, pending certain eligibility timing issues related to resubmissions and
duplicate proposal avoidance. See
C.4, section 3 for further information. |
| |
|
The Planetary Data Archiving and Restoration (PDAR) program solicits proposals to generate higher-order data products, archive
and restore data sets or products, create or consolidate reference databases, generate new reference information and digitize data. . Unlike previous years, this year the
program will not be soliciting proposals for the development or validation of software tools.
|
| |
| Proposals to this program element are subject to a relevance requirement in addition to and that supersedes those detailed in the
ROSES Summary of Solicitation, see
Section 2.1 of this program element. Proposals that do not fulfill these requirements may be returned without review. |
| |
| The information normally contained in a Data Management Plan is an integral part of the proposal and evaluated as part of
the merit. A discussion of data management activities must be integrated as part of the Science/Technical/Management portion of the proposal, no additional DMP section is
required or allowed for this program element. The discussion of data management
activities should include all relevant factors described in this element and should also
address factors outlined in
C.1 Section 3.7.1. |
| |
| Proposers are encouraged to familiarize themselves with the
Planetary Data Ecosystem Independent Review Board (PDE IRB) report , and the
Lunar Critical Data Products report.
|
| Proposals submitted to this Program Element must follow all formatting requirements that are described in program element
C.1 and
Section IV(b)ii of the
ROSES Summary of Solicitation. |
| |
| Selected investigations are expected to result in data products that are of broad use to the science community, including maps, data with improved
calibrations, etc. PDAR requires that data produced by selected investigations be archived in the Planetary Data System NASA Planetary Data System (PDS)
or a PDS equivalent archive by the end of the award period. Proposers should communicate with the PDS Discipline Node responsible
for curating similar data (links to the PDS Discipline Nodes are at http://pds.nasa.gov/ ) to discuss procedures and requirements prior to proposing and to help
with discerning the most efficient way to archive the proposed data products. Proposers intending to archive data or products in the PDS must obtain and include a letter of
confirmation from the appropriate Discipline Node that the PDS is willing to accept their submission. It is the proposer's responsibility to conform to PDS standards. All PDS submissions are
required to be in PDS4 format; if an exception is needed, please contact the lead discipline scientist before submission of the proposal to discuss.
|
|
|
|
| The following Discipline Nodes have additional information: |
Atmospheres Node
Cartography and Imaging Sciences Node
Ring-Moon Systems Node
Small Bodies Node
Geosciences Node
|
| Ancillary data (SPICE files) can be obtained from the
NAIF Node |
|
|
| Proposals to this program element may be submitted at any time without any preliminary statement such as a Notice of Intent or Step-1 proposal. See
Section 1.1 of C.1 of the Planetary Science Research Program Overview
and https://science.nasa.gov/researchers/NoDD. |
| |
| For proposals that
generate higher-order data products from NASA mission or NASA instrument data or otherwise use such data in the development or testing of software, the data to be used in proposed investigations must be available
in the Planetary Data System (PDS) or equivalent publicly accessible archive at least 30 days prior to the proposal submission date. Spacecraft data that have not been obtained yet (i.e.,
future mission data) or those that have not been accepted for distribution in approved archives are not eligible for use in investigations. Regardless of the archive(s) used, if the data to be analyzed
have issues that might represent an obstacle to analysis, the proposers must demonstrate clearly and satisfactorily how such potential difficulties will be overcome. This 30-day rule does
not apply to unarchived data from missions prior to the creation of the PDS if the dataset in question will be archived to PDS through the proposed project. The calendar of record for data released in the PDS is the
PDS Data Release Calendar . |
| |
|
Proposals to answer the need for analysis ready datasets as well as proposals to
generate new high-order data products or to improve or expand current high-order data
products are encouraged.
Proposals to archive complete datasets and/or to restore and archive incomplete datasets (e.g., to re-extract, re-reduce, and/or recalibrate data to fill in fragmentary datasets), to create and/or consolidate
reference databases useful for planetary science research, to make laboratory measurements, conduct experiments, or otherwise generate new reference information that is intended for general use in planetary science,
to recover datasets that currently are available only on media not readable by modern computing equipment, or to digitize data that are only available in analog form (e.g., printed matter, photographs, and manuscripts)
will be considered. This year the program will not be soliciting proposals for the development or validation of software tools.
|
