ROSES Data Managment Plan Tips

From The SBN PDS4 Wiki
Jump to: navigation, search

Introduction

Almost all proposals to ROSES are required to have a data management plan (DMP) or an explanation of why one is not necessary.  For more details, confer with:

  • NASA Plan for Increasing Access to the Results of Scientific Research,
  • NASA Research Announcement for ROSES,
  • Planetary Science Division Research Program Overview,
  • ROSES appendix for the particular program to which you are applying.

What follows here is a summary of what a proposer needs to consider if archiving with the PDS Small-Bodies Node.

Small Bodies Node data

The Small Bodies Node archives data concerning comets, asteroids, small satellites, meteorites, and dust, including Kuiper Belt objects, dwarf planets, returned dust samples, and laboratory spectra. Ring data, possibly including small satellites within rings, should be submitted to the Rings Node. Large satellite data is best submitted to the Imaging Node.

Other PDS nodes may have different procedures or guidelines, contact whichever node you think is relevant for your dataset. If you are unsure but think SBN may be the relevant node, contact us first.

Letters of support

Some ROSES program elements require a letter of support from the relevant archiving PDS Node. We encourage all potential SBN data providers to contact us well in advance of the program deadline for a letter of support.  We will ask you a few questions about your potential data set, and, if appropriate, return to you a letter of support that you can attach to your proposal.

ROSES 2016 data management plan

NASA ROSES 2016 Appendix C (Planetary Science Division Research Program Overview) Section 3.5 outlines the requirements for data management plans and archiving. Refer to the overview for a description of what data is covered by the DMP. In general, SBN encourages the submission of any scientifically meaningful data relevant to small bodies in our Solar System. Section C.3.5.1 states that the the data management plan should contain the following elements, as appropriate to the project, in adequate detail for review:

  1. A description of data types, volume, formats, and (where relevant) standards.
  2. A description of the schedule for data archiving and sharing.
  3. A description of the intended repositories for archived data, including mechanisms for public access and distribution.
  4. A discussion of how the plan enables long-term preservation of data.
  5. A discussion of roles and responsibilities of team members in accomplishing the data management plan.

A description of data types, volume, formats, and (where relevant) standards

  • For submission to the SBN, the standard should be the Planetary Data System version 4 (PDS4).
  • PDS4 has a limited set of acceptable data formats, summarized on our PDS4 Wiki and detailed in the PDS4 documentation.
  • Most SBN data providers submit text-based tables, binary 2D arrays (images), and associated documentation.
  • Software is potentially covered by the DMP, but PDS SBN does not archive software or source code. Although well-documented source code may qualify as data documentation, most source code is best archived elsewhere. If you think you will archive your source code with SBN, contact us first.

A description of the schedule for data archiving and sharing

The schedule should include:

  • Time to prepare the archive.
  • Time for the peer-review process, including the review meeting.  We encourage all data providers to attend the review meeting, either in person or via telephone.
  • Time to address referee comments.  It is very common for data providers to have issues that must be addressed before the data can be accepted.
    • Comments are typically related to documentation or formatting.
    • Occasionally more serious issues are discovered (yes, we have some very thorough reviewers!).

Altogether, a general rule is to submit your data set at least 4 months before your project end date, which includes:

  • A few weeks for us to check your data for compliance, and for you to resolve any issues.
  • A couple months for the review to be scheduled.  SBN reviews are scheduled when a sufficient number of data sets have been submitted.  Ultimately, we require the data set 5 weeks before the review date, which includes time for the reviewers to review the data.
  • And, an additional month for you to resolve the review comments and the reviewers to accept the changes (typically executed via e-mail or teleconference).

A description of the intended repositories for archived data, including mechanisms for public access and distribution

The NASA Planetary Data System Archive is the intended repository. The archive is publicly accessible via online servers maintained by NASA and the PDS node host institutions.

A discussion of how the plan enables long-term preservation of data

SBN standards and peer-review practices are designed to archive data files with sufficient documentation and ancillary information that the data will be useful, meaningful, and accessible to astronomers in future generations.

A discussion of roles and responsibilities of team members in accomplishing the DMP

PDS4 labels are XML based. If someone on your team has relevant experience, consider adding appropriate discussion.