Space Physics Data Availability Catalog
(Appendices)

Table of Contents

Appendix A: Updating the Catalog

1. Select the "Update the catalog" button from the top page.
2. Select a mission from the pull-down menu and push the "Select Mission" button or push the "New Mission" button to add a mission not in the pull-down menu.
3. Select an investigation from the pull-down menu and push the "Select Investigation" button or push the "New Investigation" button to add an investigation not in the pull-down menu. The investigation "(mission)" indicates data products for the mission as a whole (orbit-attitude, theory, aggregate data).
4. To get an overview of what has already been entered for this investigation, select the button "View One Page Information". Otherwise, fill in the fields and select the button "Update Catalog"; this will submit the changes and return a page of text.
5. Backup to the instrument page. At the bottom of the page are buttons for individual data products and a "New" button for adding another data product. Select one of the Edit buttons and change the fields or enter new information to the New data product form. Select "Update Catalog" to submit your changes. Add a new data product page for each major data product (it is possible to have several data products for each category (graphics, low-res, high-res, telemetry-level).
6. Continue for each data product for each investigation of which you have knowledge.

Appendix B: Database Specifics

Mission Fields

mission             (40 Char.)    Mission Name [1]
experiment          (40 Char.)    Investigation Acronym [1]
full_name           (100 Char.)   Full Investigation Name
instrument_type     (50 Char.)    Instrument Type (ISTP/IACG Keyword) [2]
surname             (25 Char.)    PS/PI Surname
first_name          (25 Char.)    PS/PI First Name
pi_address          (2000 Char.)  PI Contact Address/Phone/FAX/e-mail
data_address        (2000 Char.)  Data Contact Name and Address/Phone/FAX/e-mail
description         (2000 Char.)  Brief Description [5]
objectives          (2000 Char.)  Measurement Objectives [6]
summary_products    (2000 Char.)  Summary of the Major Data Products
homepage            (Yes/No/*)    Home Page? [3]
pi_contact          (Yes/No/*)    PI Contact Information on Home Page? [4]
url                 (2000 Char.)  Home Page URLs [7]
home_page_contents  (2000 Char.)  Contenets of the Home Page
Notes               (2000 Char.)  Additional Notes
nssdc_id            (11 Char.)    NSSDC ID [8]
ok                  (DATE)        Date that the Record was Certified [9]
pi_ok               (DATE)        Date that the PI Certified the Record [9]
who_update          (80 Char.)    Name of the Person who Certified the Record [9]

 [1] The mission name and investigation acronym are entered only when entering
     a new mission or investigation.
 [2] The instrument type is a broad attempt to classify investigations; send
     requests for new options to us.
 [3] Is there a home page for the mission/investigation?
 [4] Is there sufficient contact information on the mission/investigation home
     page to reach the PI without other sources of information?
 [5] Give a brief description of the mission/investigation (general capabilities,
     measurement objectives, time resolution).
 [6] Describe the the measurement objectives and instrument data capabilities of
     the mission/investigation.
 [7] List URLs for the mission/investigation on separate lines, with the main
     URL on the first line.
 [8] An NSSDC ID is assigned to every spacecraft and investigation in the
     form yy-nnna-mm for the nnn'th launch of year yy and mm'th
     investigation on that spacecraft.  This will be used to automatically
     query other databases.
 [9] When you are satisfied that the information on the page is complete and
     correct, check the top box if you are staff or check the bottom box if
     you represent the PI and enter your name in the field provided.

Dataset Fields

dataset_title     (80 Char.)            Short title for data product
graphic           (Yes/No/*)            Graphic? [1]
low_res           (Yes/No/*)            Digital Low Resolution? [1]
high_res          (Yes/No/*)            Digital High Resolution? [1]
full_res          (Yes/No/*)            Digital Full Telemetry Resolution? [1]
description       (2000 Char.)          Brief Description [2]
exist             (Yes/No/*)            Does the Data Product Exist? [3]
begin_production  (20 Char.)            Production Start Date [4]
public            (Yes/No/Request/*)    Public? [5]
citable           (Yes/No/Caution/*)    Citable? [6]
usable            (Yes/No/Difficult/*)  Usable? [7]
format            (80 Char.)            Data Product Format [8]
electronic        (Yes/No/*)            Electronically Available? [9]
url               (2000 Char.)          URL(s) [10]
archived          (Yes/No/*)            Archived at NSSDC? [11]
start_date        (25 Char.)            Start Date [12]
stop_date         (25 Char.)            Stop Date [13]
lag_time          (80 Char.)            Lag Time [13]
volume            (10 Char.)            Estimated Yearly Volume (GBytes/year)
notes             (2000 Char.)          Additional Notes
nssdc_id          (11 Char.)            NSSDC ID [14]

 [1] Choose which types best describe the data product.  For example, if the
     data product is graphic, set the graphic field to "Y".
 [2] Give a brief description of the data product (parameters, resolution).
 [3] Does this data product presently exist?  The valids are yes, no, and
     unknown (*).
 [4] If the data product doesn't currently exist, give the date that the data
     product will begin production.
 [5] Is this data product publicly available?  The valids are yes, no, available
     through a request to PI, and unknown (*).
 [6] Is this data product citable in a paper without extensive review by PI?
     The valids are yes, no, citable with caution, and unknown (*).
 [7] Is this data product usable with the available documentation and software?
     The valids are yes, no, difficult, and unknown (*).
 [8] In what format is the data product stored (preferably a standard format)?
 [9] Is this data product electronically available (WWW, FTP, etc.)?  The valids
     are yes, no, and unknown (*).
[10] List all URLs that give access to the data product on separate lines, with
     the main URL on the first line.
[11] Is the data product archived at NSSDC?  The valids are yes, no, and
     unknown (*).
[12] What is the start date (mm/dd/yy) for the data product.
[13] Give either the stop date (mm/dd/yy) for the data product or the typical
     lag time for adding new data.
[14] For data products archived at NSSDC, NSSDC data product IDs follow the
     investigation ID pattern with a letter suffix.  This will be used to
     automatically query other databases.