PDS_VERSION_ID = PDS3 RECORD_TYPE = FIXED_LENGTH RECORD_BYTES = 80 OBJECT = TEXT PUBLICATION_DATE = 1998-07-31 NOTE = "Keywords and definitions used in this archival data set, taken from the PDS Data Dictionary" END_OBJECT = TEXT END ADDRESS_TEXT The address_text data element provides an unlimited-length, formatted mailing address for an individual or institution. ALTERNATE_TELEPHONE_NUMBER The alternate_telephone_number data element provides an alternate telephone number for an individual or node. (Includes the area code.) BYTES The bytes element indicates the number of bytes allocated for a particular data representation. COLUMNS The columns element represents the number of columns in each row of a data object. Note: In the PDS, the term 'columns' is synonymous with 'fields'. COLUMN_NUMBER The column_number element identifies the location of a specific column within a larger data object, such as a table. For tables consisting of rows (i = 1, N) and columns (j = 1,M), the column_number is the j-th index of any row. CONFIDENCE_LEVEL_NOTE The confidence_level_note element is a text field which characterizes the reliability of data within a data set or the reliability of a particular programming algorithm or software component. Essentially, this note discusses the level of confidence in the accuracy of the data or in the ability of the software to produce accurate results. DATA_OBJECT_TYPE The data_object_type element identifies the data object type of a given set of data. Example values: IMAGE, MAP, SPECTRUM Note: Within the PDS, data object types are assigned according to the standards outlined in the PDS Standards Reference. Note: within AMMOS and only for the Magellan catalog, this element is used as an alias for data_set_id. The use of data_object_type as such provides backward compatibility with earlier AMMOS conventions. The use of this element as an alias for data_set_id is not recommended for any new tables. See data_set_id. DATA_SET_COLLECTION_MEMBER_FLG The data_set_collection_member_flg element indicates whether or not a data set is a member of a data set collection. DATA_SET_DESC The data_set_desc element describes the content and type of a data set and provides information required to use the data (such as binning information). DATA_SET_ID The data_set_id element is a unique alphanumeric identifier for a data set or a data product. The data_set_id value for a given data set or product is constructed according to flight project naming conventions. In most cases the data_set_id is an abbreviation of the data_set_name. Example value: MR9/VO1/VO2-M-ISS/VIS-5-CLOUD-V1.0. Note: In the PDS, the values for both data_set_id and data_set_name are constructed according to standards outlined in the Standards Reference. DATA_SET_NAME The data_set_name element provides the full name given to a data set or a data product. The data_set_name typically identifies the instrument that acquired the data, the target of that instrument, and the processing level of the data. Example value: MR9/VO1/VO2 MARS IMAGING SCIENCE SUBSYSTEM/VIS 5 CLOUD V1.0. See also: data_set_id. Note: In PDS, the data_set_name is constructed according to standards outlined in the Standards Reference. Note: This element is defined in the AMMOS Magellan catalog as an alias for file_name to provide backward compatibility DATA_SET_RELEASE_DATE The data_set_release_date element provides the date when a data set is released by the data producer for archive or publication. In many systems this represents the end of a proprietary or validation period. Formation rule: YYYY-MM-DD Note: In AMMOS, the data_set_release_date element is used to identify the date at which a product may be released to the general public from proprietary access. AMMOS-related systems should apply this element only to proprietary data. DATA_TYPE The data_type element supplies the internal representation and/or mathematical properties of a value being stored. See also: bit_data_type, general_data_type. Note: In the PDS, users may find a bit-level description of each data type in the Standards Reference document. DESCRIPTION The description element provides a free-form, unlimited-length character string that represents or gives an account of something. DETAILED_CATALOG_FLAG The detailed_catalog_flag element is a yes-or-no flag which indicates whether additional information is available for this data set in a detailed-level catalog. ELECTRONIC_MAIL_ID The electronic_mail_id element provides an individual's mailbox name on the electronic mail system identified by the electronic_mail_type element. ELECTRONIC_MAIL_TYPE The electronic_mail_type element identifies an electronic mail system by name. Example values: TELEMAIL, NSI/DECNET. FACILITY_NAME The facility_name element identifies a department, laboratory, or subsystem that exists within an institution. FAX_NUMBER The fax_number data element provides the area code and telephone number needed to transmit data to an individual or a node via facsimile machine. FILE_RECORDS The file_records element indicates the number of physical file records, including both label records and data records. Note: In the PDS the use of file_records along with other file-related data elements is fully described in the Standards Reference. FORMAT A specified or predetermined arrangement of data within a file or on a storage medium. Note: In the PDS, the format element indicates the display specification for a collection of data. It is equivalent to the FORTRAN language format specification. Example values: 'Ew.deEXP', A6, I5. FULL_NAME The full_name element provides the complete name or identifier for a person or object. For an individual, full name includes the name as well as titles and suffixes. For an object, full name provides the spelled-out name that in some cases corresponds to an 'id'. INDEXED_FILE_NAME The INDEXED_FILE_NAME element is a string (or set of strings) identifying the files included in an index table on an archive volume. The element is used in the label for a volume index table. The value may include a directory path. The usage of INDEXED_FILE_NAME may vary based on the value of the INDEX_TYPE element in the index label. Note: For Mars Observer, some volume indicies have INDEX_TYPE = SINGLE, and the value of INDEXED_FILE_NAME is a set of wildcard strings matching the product file names on the volume being indexed. Other indicies may have INDEX_TYPE = CUMULATIVE, and the value of INDEXED_FILE_NAME is a list of file names identifying the SINGLE index files which were appended together to create the CUMULATIVE index. INDEX_TYPE The INDEX_TYPE element identifies the type of an index table that describes an archive volume. It is used in the label for a volume index table. In general, the two allowable index types are SINGLE, meaning that every row in the index table describes a file on the current volume; CUMULATIVE, meaning that every row in the index table describes a file residing on the current volume or a previous volume in the volume set. INSTITUTION_NAME The institution_name element identifies a university, research center, or NASA center. INSTRUMENT_DESC The instrument_desc element describes a given instrument. INSTRUMENT_HOST_DESC The instrument_host_desc data element describes the spacecraft or earthbase from which particular instrument measurements were taken. For spacecraft, this description addresses the complement of instruments carried, the on-board communications and data processing equipment, the method of stabilization, the source of power and the capabilities or limitations of the spacecraft design which are related to data-taking activities. The description may be a synopsis of available mission documentation. INSTRUMENT_HOST_ID The instrument_host_id element provides a unique identifier for the host where an instrument is located. This host can be either a spacecraft or an earth base (e.g., and observatory or laboratory on the earth). Thus, the instrument_host_id element can contain values which are either spacecraft_id values or earth_base_id values. INSTRUMENT_HOST_NAME The instrument_host_name element provides the full name of the host on which an instrument is based. This host can be either a spacecraft or an earth base. Thus, the instrument_host_name element can contain values which are either spacecraft_name values or earth_base_name values. INSTRUMENT_HOST_TYPE The instrument_host_type element provides the type of host on which an instrument is based. For example, if the instrument is located on a spacecraft, the instrument_host_type element would have the value SPACECRAFT. INSTRUMENT_ID The instrument_id element provides an abbreviated name or acronym which identifies an instrument. Note: The instrument_id is not a unique identifier for a given instrument. Note also that the associated instrument_name element provides the full name of the instrument. Example values: IRTM (for Viking Infrared Thermal Mapper), PWS (for plasma wave spectrometer). INSTRUMENT_NAME The instrument_name element provides the full name of an instrument. Note: that the associated instrument_id element provides an abbreviated name or acronym for the instrument. Example values: FLUXGATE MAGNETOMETER, NEAR_INFRARED MAPPING SPECTROMETER. INSTRUMENT_TYPE The instrument_type element identifies the type of an instrument. Example values: POLARIMETER, RADIOMETER, REFLECTANCE SPECTROMETER, VIDICON CAMERA. INTERCHANGE_FORMAT The interchange_format element represents the manner in which data items are stored. Example values: BINARY, ASCII. INVALID_CONSTANT The invalid_constant element supplies the value used when the received data were out of the legitimate range of values. Note: For PDS and Mars Observer applications -- because of the unconventional data type of this data element, the element should appear in labels only within an explicit object, i.e. anywhere between an 'OBJECT =' and an 'END_OBJECT'. LAST_NAME The last_name element provides the last name (surname) of an individual. MEDIUM_TYPE The medium_type element identifies the physical storage medium for a data volume. Examples: CD-ROM, CARTRIDGE TAPE. MISSION_ALIAS_NAME The mission_alias_name element provides an official name of a mission used during the initial design, implementation, or prelaunch phases. Example values: mission_name:MAGELLAN, mission_alias_name:VENUS RADAR MAPPER. MISSION_DESC The mission_desc element summarizes major aspects of a planetary mission or project, including the number and type of spacecraft, the target body or bodies and major accomplishments. MISSION_NAME The mission_name element identifies a major planetary mission or project. A given planetary mission may be associated with one or more spacecraft. MISSION_OBJECTIVES_SUMMARY The mission_objectives_summary element describes the major scientific objectives of a planetary mission or project. MISSION_PHASE_NAME The mission_phase_name element provides the commonly-used identifier of a mission phase. MISSION_START_DATE The mission_start_date element provides the date of the beginning of a mission in UTC system format. Formation rule: YYYY-MM-DDThh:mm:ss[.fff] MISSION_STOP_DATE The mission_stop_date element provides the date of the end of a mission in UTC system format. Formation rule: YYYY-MM-DDThh:mm:ss[.fff] NAME The name data element indicates a literal value representing the common term used to identify an element or object. See also: 'id'. Note: In the PDS data dictionary, name is restricted to 30 characters, and must conform to PDS nomenclature standards. NODE_ID The node_id element provides the node id assigned to a science community node. NOTE The note element is a text field which provides miscellaneous notes or comments (for example, concerning a given data set or a given data processing program). PDS_AFFILIATION The pds_affiliation data element describes the type of relationship an individual has with a PDS node. (e.g., staff, advisory group, etc..) PDS_USER_ID The pds_user_id element provides a unique identifier for each individual who is allowed access to the PDS. The system manager at the Central Node assigns this identifier at the time of user registration. PDS_VERSION_ID The PDS_version_id data element represents the version number of the PDS standards documents that is valid when a data product label is created. Values for the PDS_version_id are formed by appending the integer for the latest version number to the letters 'PDS'. Examples: PDS3, PDS4. PREFERENCE_ID The preference_id element indicates a user's degree of preference for one of a set of alternatives (for example, preference for a particular electronic mail system such as Internet). Values range from 1 to 4, with 1 indicating the highest preference. PRODUCER_FULL_NAME The producer_full_name element provides the full_name of the individual mainly responsible for the production of a data set. See also: full_name. Note: This individual does not have to be registered with the PDS. PRODUCER_INSTITUTION_NAME The producer_institution_name element identifies a university, research center, NASA center or other institution associated with the production of a data set. This would generally be an institution associated with the element producer_full_name. PRODUCT_CREATION_TIME The product_creation_time element defines the UTC system format time when a product was created. Formation rule: YYYY-MM-DDThh:mm:ss[.fff] PRODUCT_ID The product_id data element represents a permanent, unique identifier assigned to a data product by its producer. See also: source_product_id. Note: In the PDS, the value assigned to product_id must be unique within its data set. Additional note: The product_id can describe the lowest-level data object that has a PDS label. PRODUCT_RELEASE_DATE The product_release_date data element identifies the date on which a particular data product is released from one system or process to another, according to system- or application-specific criteria. Formation rule: YYYY-MM-DD PRODUCT_VERSION_TYPE The product_version_type element identifies the version of an individual data product. It can be applied to any type of data that might appear in several incarnations, including ephemeris files, sequence files, or software. Example values: VERSION 1, PREDICT, ACTUAL, DRAFT, PRELIMINARY, FINAL, REVISION A. PUBLICATION_DATE The publication_date element provides the date when a published item, such as a document or a compact disc, was issued. Formation rule: YYYY-MM-DD RECORD_BYTES The record_bytes element indicates the number of bytes in a physical file record, including record terminators and separators. Note: In the PDS, the use of record_bytes, along with other file-related data elements is fully described in the Standards Reference. RECORD_TYPE The record_type element indicates the record format of a file. Note: In the PDS, when record_type is used in a detached label file it always describes its corresponding detached data file, not the label file itself. The use of record_type along with other file-related data elements is fully described in the Data Preparation Workbook. REFERENCE_DESC The reference_desc element provides a complete bibliographic citation for a published work. The format for such citations is that employed by the Journal of Geophysical Research (JGR). This format is described in the JGR, Volume 98, No. A5, Pages 7849-7850, May 1, 1993 under 'References'. Data suppliers may also refer to recent issues of the Journal for examples of citations. Elements of a complete bibliographic citation must include, wherever applicable, author(s) or editor(s), title, journal name, volume number, page range and publication date (for journal article citations), or page range, publisher, place of publication, and publication date (for book citations). REFERENCE_KEY_ID The reference_key_id element provides the catalog with an identifier for a reference document. Additionally, it may be used in various catalog descriptions, for example in data_set_desc, as a shorthand notation of a document reference. The reference_key_id element is composed according to the following guidelines: 1. if there is an author for the publication, the general rule is: REFERENCE_KEY_ID = , where is a maximum of 15 characters, and may need to be truncated. is 4 characters for the year published. is optional and consist of one character used to distinguish multiple papers by the same author(s) in the same year. The following variations apply: a. If there is one author: Example value: SCARF1980 b. If there are two authors: & Example value: SCARF&GURNETT1977 c . If there are three or more authors: ETAL Example value: GURNETTETAL1979 d. If one author has the same last name as another: , Example value: FREUD,A1935 e. If the same author(s) published more than one paper in the same year: or & or ETAL Example values: SCARF1980A SCARF&GURNETT1977B f. In cases where an initial reference has been catalogued and published on an Archive medium and subsequent references for the same author and same year are needed at a later date, the following rule applies: Leave the original reference as is, and add a letter to the subsequent references starting with the letter 'B' since the original reference will now be assumed to have an implicit 'A'. For example: PFORD1991, PFORD1991B. Note that if the initial reference has only been catalogued and not yet published, then it can be modified such that the 'A' is explicit, i.e. PFORD1991A. 2. If there is no author for the publication, the general rule is: REFERENCE_KEY_ID = where is a maximum of 10 characters, and may need to be abbreviated is a maximum of 10 characters. This id may consist of a volume number, and/or document or issue number, and/or year of publication. Example values: SCIENCEV215N4532 JGRV88 JPLD-2468 REGISTRATION_DATE The registration_date element provides the date as of which an individual is registered as an authorized user of the PDS system. Formation rule: YYYY-MM-DD ROWS The rows element represents the number of rows in a data object. Note: In PDS, the term 'rows' is synonymous with 'records'. In PDS attached labels, the number of rows is equivalent to the number of file_records minus the number of label_records, as indicated in the file_object definition. ROW_BYTES The row_bytes element represents the number of bytes in each data object row. Note: In the PDS, in labels for tables, the value of row_bytes includes terminators, separators, and delimiters unless spares are used. For spares at the beginning of a row, the keyword row_prefix_bytes may be used. For spares at the end of a row, row_suffix_bytes may be used. See the Standards Reference, TABLE object for more information. ROW_SUFFIX_BYTES The row_suffix_bytes element indicates the number of bytes following the data at the end of each row. The value must be an integral number of bytes. SPACECRAFT_NAME The spacecraft_name element provides the full, unabbreviated name of a spacecraft. See also: spacecraft_id, instrument_host_id. START_BYTE The start_byte element in a data object identifies the location of the first byte of the object, counting from 1. For nested objects, the start_byte value is relative to the start of the enclosing object. START_TIME The start_time element provides the date and time of the beginning of an event or observation (whether it be a spacecraft, ground-based, or system event) in UTC system format. Formation rule: YYYY-MM-DDThh:mm:ss[.fff] STOP_TIME The stop_time element provides the date and time of the end of an observation or event (whether it be a spacecraft, ground-based, or system event) in UTC system format. Formation rule: YYYY-MM-DDThh:mm:ss[.fff] TARGET_NAME The target_name element identifies a target. The target may be a planet, satellite,ring,region, feature, asteroid or comet. See target_type. TELEPHONE_NUMBER The telephone_number element provides the area code, telephone number and extension (if any) of an individual or node. See also: fts_number. UNIT The unit element provides the full name or standard abbreviation of a unit of measurement in which a value is expressed. Example values: square meter, meter per second. Note: A table of standard units representing those published by the Systeme Internationale appears in the 'Units of Measurement' section of the PSDD. (Please refer to the table of contents for its location.) The values in this table's 'Unit Name' column constitute the standard values for the data element UNIT. VOLUMES The volumes element provides the number of physical data volumes contained in a volume set. Note: In the PDS, volumes represents the total number of related data volumes that comprise a single orderable unit, as represented by the volume_set_id. For Example, the volume set VOYAGER IMAGES OF URANUS has the volume_set_id of USA_NASA_PDS_VG_0001_TO_VG_0003 and the value for volumes would be 3. VOLUME_FORMAT The volume_format element identifies the logical format used in writing a data volume, such as ANSI, TAR, or BACKUP for tape volumes and ISO-9660, HIGH-SIERRA, for CD-ROM volumes. VOLUME_ID The volume_id element provides a unique identifier for a data volume. Example: MG_1001. VOLUME_NAME The volume_name element contains the name of a data volume. In most cases the volume_name is more specific than the volume_set_name. For example, the volume_name for the first volume in the VOYAGER IMAGES OF URANUS volume set is: Volume 1: Compressed Images 24476.54 - 26439.58 VOLUME_SERIES_NAME The volume_series_name element provides a full, formal name that describes a broad categorization of data products or data sets related to a planetary body or a research campaign (e.g. International Halley Watch). A volume series consists of one or more volume sets that represent data from one or more missions or campaigns. For example, the volume series MISSION TO VENUS consists of the following three volume sets: MAGELLAN: THE MOSAIC IMAGE DATA RECORD MAGELLAN: THE ALTIMETRY AND RADIOMETRY DATA RECORD PRE-MAGELLAN RADAR AND GRAVITY DATA SET COLLECTION VOLUME_SET_ID The volume_set_id element identifies a data volume or a set of volumes. Volume sets are normally considered as a single orderable entity. Examples: USA_NASA_PDS_MG_1001, USA_NASA_PDS_GR_0001_TO_GR_0009 VOLUME_SET_NAME The volume_set_name element provides the full, formal name of one or more data volumes containing a single data set or a collection of related data sets. Volume sets are normally considered as a single orderable entity. For example, the volume series MISSION TO VENUS consists of the following three volume sets: MAGELLAN: THE MOSAIC IMAGE DATA RECORD MAGELLAN: THE ALTIMETRY AND RADIOMETRY DATA RECORD PRE-MAGELLAN RADAR AND GRAVITY DATA SET COLLECTION In certain cases, the volume_set_name can be the same as the volume_name, such as when the volume_set consists of only one volume. VOLUME_VERSION_ID The volume_version_id element indentifies the version of a data volume. All original volumes should use a volume_version_id of 'Version 1'. Versions are used when data products are remade due to errors or limitations in the original volumes (test volumes, for example), and the new version makes the previous volume obsolete. Enhancements or revisions to data products which constitute alternate data products should be assigned a unique volume id, not a new version id. Examples: Version 1, Version 2.