NASA - National Aeronautics and Space Administration
Follow this link to skip to the main content
+ NASA Homepage
+ NASA en Español
+ Contact NASA
Planetary Data System Banner
Home Data Services Tools Documents Related Sites About PDS Sitemap
Documents
Archive Preparation Guide
Proposer’s Archive Guide
Standards Reference
Data Preparer’s Workbook
Quick-Start Introduction to
PDS Archiving
Data Preparer’s Workbook

DPW Chapter 5: Orientation

Table of Contents


Chapter 5

Orientation Checklist

5.1 Establish Contact with PDS

5.2 Provide General Information to PDS

5.3 Obtain PDS Orientation Materials

5.4 Establish Technical Contacts

Chapter 5

Orientation

This section describes the first phase of the archive process. During this phase contact is established between PDS and flight project managers or potential data suppliers.

5.1 Establish Contact with PDS

The first point of contact with the PDS should be through the PDS Mission Products Manager for active flight projects or through an appropriate Discipline Node Manager. (see Appendix A, Whom to Contact). The Mission Products Manager coordinates support for all aspects of archiving active flight project data and provides additional support to PDS Discipline Nodes for help with data restoration activities.

5.2 Provide General Information to PDS

For active flight projects, the following general kinds of information will be helpful during early contact with the PDS Mission Products Manager:

  • General project information ( mission description, types and numbers of instruments, science objectives, estimated volume of data to be archived)

  • Major project milestones (launch date, encounter date, major project reviews)

  • Project contact(s) for archive issues

For data restorations or other kinds of experiment or observation data, general information that may be useful to the PDS Discipline Node Manager, to the extent it is known, may include:

  • Scientific value of the data

  • Descriptive information about the data (spacecraft, instrument/experiment, targets, events, range of data)

  • Physical description of the data (current media, total data volume, data organization, formats, data condition)

  • Description of supporting software needed for understanding and/or analyzing the data (e.g. data processing, reduction, analysis software, supporting documentation)

  • Description of relevant ancillary data (SEDRs, SPICE kernels, calibration data, etc.)

  • Special considerations (e.g., tapes in danger of deterioration, PIs may move on to other projects, data is in demand, data would be easy to restore)

5.3 Obtain PDS Orientation Material

For active flight projects, a PDS Orientation will be scheduled. At this orientation, you will be given an overview of PDS, including general descriptions of the roles and responsibilities of the project, the PDS Central and Discipline Nodes and the NSSDC during the archive process. A Data Preparation Package will be handed out, providing you with additional information.

You may also arrange for an overview and demonstration of PDS software tools to help determine their applicablilty to your project needs. These demonstrations are geared to software or system engineers involved in designing a ground data system for the project. Further information on PDS Tools is provided in Appendix B.

For data restorations, if you will be preparing the data for archive yourself, your Discipline Node contact may suggest that you obtain a Data Preparation Package also.

The Data Preparation Package consists of:

PDS Data Preparation Workbook (this document)

PDS Standards Reference

Planetary Science Data Dictionary

PDS Toolbox Overview

5.4 Establish Technical Contacts

For flight projects, the Mission Products Manager will identify a data engineer from the Central Node and one or more PDS Discipline Nodes who will provide technical support to the project. The project should also identify their management and technical contacts for archive issues at this time.

Generally, flight projects will establish teams (such as the Data Product Working Group on Magellan or the Data Working Group on Galileo) to address project-wide archive issues. These teams are chaired by members of the project's science community and consist of representatives from each instrument team, PDS representatives, and flight project engineers involved in data archiving.

In addition, PDS may establish a team, called a Mission Interface Team (MIFT), which meets more frequently than the flight project team, and addresses some of the more detailed archive issues. The MIFT will consist of members of the PDS Central and Discipline Nodes, the NSSDC, and the flight project.

For data restorations, your primary technical contact will be with the PDS Discipline Node. In addition, the PDS Mission Products Manager will identify a Data Engineer from the Central Node to assist the Discipline Node as needed during the archive process.

NASA Privacy StatementCopyrightFeedbackSitemapSystem Requirements
FirstGov Logo
+ Freedom of Information Act
+ NASA 2003 Strategic Plan
+ NASA Privacy Statement, Disclaimer, and
   Accessiblity Certification

+ Copyright/Image Use Policy
NASA Logo
Curator: Emily.S.Law
Webmaster: Brian Truong
NASA Official: William Knopf
Last Updated:
+ Comments and Questions