Skip to content

PDS3 Supplemental Metadata Requirements and Design

Jordan Padams edited this page Apr 29, 2022 · 4 revisions

PDS3 Supplemental Metadata Design

General Requirements

  1. Each PDS3 Product Metadata Supplemental must be associated with 1 instrument only.

Metadata Requirements

  1. Reference_List must contain reference to PDS3 Data Set in registry, e.g.
<Reference_List>
    …
    <Internal_Reference>
        <lidvid_reference>urn:nasa:pds:context_pds3:data_set:data_set.msl-m-hazcam-2-edr-v1.0</lidvid_reference>
        <reference_type>is_member_of_pds3_data_set</reference_type>
    </Internal_Reference>
</Reference_List>
  1. As much as possible, we should use the Product_Metadata_Supplemental metadata to provide the following information:
  • Investigation_Area
  • Observing_System (Instrument and Spacecraft)
  • Science_Facets.facet1
  • Science_Facets.facet2
  • Science_Facets.domain
  • Science_Facets.wavelength_range
  • Primary_Result_Summary.purpose=Science
  • To be continued...
  1. New generic "PDS3 to PDS4 Mapper" LDD within the label providing the following information
<Table_Mappings>
  <unique_id_reference>PRODUCT_ID</>
  <Field_Mapping>
    <source_table_field_reference>TARGET_NAME_1</>
    <destination_pds4_metadata>Target_Indentification.target_name</>
    <!-- we will want to figure out how to get the identifier -->
  </Field_Mapping>
  <Field_Mapping>
    <source_table_field_reference>TARGET_NAME_2</>
    <destination_pds4_metadata>Target_Indentification.target_name</>
    <!-- we will want to figure out how to get the identifier -->
  </Field_Mapping>
  <Field_Mapping>
    <source_table_field_reference>TARGET_NAME_3</>
    <destination_pds4_metadata>Target_Indentification.target_name</>
    <!-- we will want to figure out how to get the identifier -->
  </Field_Mapping>
  <Field_Mapping>
    <source_table_field_reference>INSTRUMENT_NAME</>
    <destination_pds4_metadata>Observing_System_Component.name</>
    <!-- we will want to figure out how to get the identifier and Observing_System_Component.type -->
  </Field_Mapping>
  <Field_Mapping>
    <source_table_field_reference>START_DATE_TIME</>
    <destination_pds4_metadata>Time_Coordinates.start_date_time</>
    <!-- will need to use time translation here -->
  </Field_Mapping>
  <Field_Mapping>
    <source_table_field_reference>STOP_DATE_TIME</>
    <destination_pds4_metadata>Time_Coordinates.stop_date_time</>
    <!-- will need to use time translation here -->
  </Field_Mapping>
  ...
</Table_Mappings>
  • <unique_id_reference> - Reference to the field in the table that is the unique identifier. To be combined with LID from data set from (1) to form the products LID, e.g. urn:nasa:pds:context_pds3:data_set:data_set.msl-m-hazcam-2-edr-v1.0:some-hazcam-product-id

Table Product Requirements

  1. Each row of the table must identify 1 unique identifier (e.g. PRODUCT_ID, FILE_PATH) and Where possible, rows should map to other parts of the PDS4 Information (e.g. Target_Identification.target_name

Minimum Metadata

Based upon the PDS Query Models defined a while back, here is the minimum metadata we want to be able to capture

  • Product_Collection.collection_type=Data (ignored in query parameters)
  • Primary_Result_Summary.processing_level
  • Investigation_Area.type=Mission (ignored in query parameters)
  • Science_Facets.domain
  • Identification_Area.product_class**=Product_Collection** (ignored in query parameters)
  • Science_Facets.wavelength_range
  • Primary_Result_Summary.purpose=Science (ignored in query parameters)
  • Science_Facets.discipline_name
  • Time_Coordinates.start_date_time
  • Collection.description
  • Time_Coordinates.stop_date_time
  • Product_Context.Instrument.type
  • Target_Identification.name
  • Identification_Area.logical_identifier
  • Target_Identification.type
  • Identification_Area.version_id
  • Investigation_Area.name
  • Science_Facets.facet1
  • Observing_System.name
  • Science_Facets.facet2
  • Observing_System_Component.name
  • Primary_Result_Summary.description
  • Observing_System_Component.type**=Instrument** (ignored in query parameters)
  • Target_Identification.description
  • Identification_Area.title
  • system.archive_status
  • Citation_Information.keyword
  • Citation_Information.description