Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
stylecircle

Element Description

The PGE Version Class element stores basic descriptive characteristics related to the Product Generation Executable (PGE) associated with a granule. PGE refers to software used to produce a standard data product. 


Best Practices

There are two sub-elements that comprise the PGE Version Class:

  • PGE Name:  Name The name of the product generation executable.
  • PGE Version: Version of the product generation executable that produced used to produce the granule.

Providing the PGE Version Class is optional. If provided, the Version number must be included - providing the PGE Name remains optional. 


Examples:

PGE Name: "

A PGE Name

MOD_PR10A2_8day_snow_cover_tile"

PGE Version: "6.0.27"

PGE Name: "OMCLDO2 Level 2"

PGE Version: "

6

2.0.0.

27

9"


Element Specification

The PGE Version Class element is not required optional. Only one PGE Version Class may be provided (Cardinality: 0..1)

ModelElementTypeConstraintsRequired?Cardinality
UMM-GPGEVersionClass/PGENameString

1 - 1024 characters

No0..1
UMM-GPGEVersionClass/PGEVersionString1 - 10 charactersYes, if applicable1



Metadata Validation and QA/QC

All metadata entering the CMR goes through the below process to ensure metadata quality requirements are met. All records undergo CMR validation before entering the system. The process of QA/QC is slightly different for NASA and non-NASA data providers. Non-NASA providers include interagency and international data providers and are referred to as the International Directory Network (IDN).

Lucidchart
rich-viewerfalse
autofittrue
nameCopy of Wiki Page Metadata Evaluation Workflow-1939-51df84
width1102
pages-to-display
id98e5dc28-3252-4209-953f-66f1378e1cf4
alignLeft
height299

Please see the expandable sections below for flowchart details. 


Expand
titleCMR Validation

<>

Expand
titleARC Metadata QA/QC

ARC Priority Matrix

Priority CategorizationJustification

Red = High Priority Finding

This element is categorized as highest priority when:

    • The information provided is incorrect for the granule
    • The information contains a spelling or grammatical error
Not Applicable
    • .
    • A PGE Name is provided without an accompanying PGE Version.

Yellow = Medium Priority Finding

Not Applicable

Blue = Low Priority Finding

Not Applicable

Green = No Findings/Issues

The element is provided and follows all applicable criteria specified in the best practices section above.

ARC Automated Rules

  • If no value is provided, return is "np."
  • Otherwise, return is "OK."

    Checks

    ARC uses the pyQuARC library for automated metadata checks. Please see the pyQuARC GitHub for more information. 

    Dialect Mappings

    Expand
    titleECHO 10

    ECHO 10

    Granule UR is required for The PGE Version Class element is optional in ECHO 10.
    Only one PGE Version Class may be provided (Cardinality: 0..1)

    UMM-G ElementSpecificationECHO 10 PathTypeConstraintsRequired in ECHO10?Cardinality
    ECHO-10PGEVersionClass/PGENamePGEVersionClass/PGENameString

    1 - 1024 characters

    No0..1
    ECHO-10PGEVersionClass/PGEVersion
    PGEVersionClass/PGEVersionString1 - 10 charactersYes, if applicable1


    Example Mapping

    Section
    Column
    width50%

    ECHO 10

    No Format
    <PGEVersionClass>
      <PGEName>OMCLDO2 <PGEName>PGELevel Name<2</PGEName>
      <PGEVersion>6<PGEVersion>2.0.0.27<9</PGEVersion>
    </PGEVersionClass>
    Column
    width50%

    UMM

    No Format
    "PGEVersionClass": {
          "PGEName": "PGEOMCLDO2 Level Name2",
          "PGEVersion": "62.0.0.279"
      },
    Expand
    titleISO 19115-2 MENDS

    ISO 19115-2 MENDS

    The path where Granule UR is provided in ISO is optional, however, a Granule UR is required for all granule metadata submitted below table specifies where the CMR looks for PGE Version Class information in ISO. Only one PGE Version Class will be translated from ISO to the CMR (Cardinality: 0..1). Providing PGE Version class is optional, but if provided, should at a minimum include the PGE Version.

    UMM-G ElementISO PathTypeNotes

    PGEVersionClass/PGEName

    PGEVersionClass/PGEVersion

    (CMR read and write - use this ISO path to insure that the PGE Version Class will be translated from ISO to other CMR supported metadata dialects)*

    /gmi:MI_Metadata/gmd:dataQualityInfo/gmd:DQ_DataQuality/gmd:lineage/gmd:LI_Lineage/gmd:processStep/gmi:LE_ProcessStep [=>

    [=>/gmd:description/gco:CharacterString = PGEVersionClass
    [=>/gmi:processingInformation/eos:EOS_Processing/gmi:identifier/gmd:MD_Identifier/gmd:code/gco:CharacterString =

    "

    PGEName:

    "

    {the actual PGEName}

    "

    PGEVersion:

    "

    {the actual PGEVersion}
    [=>/gmi:processingInformation/eos:EOS_Processing/gmi:identifier/gmd:MD_Identifier/gmd:codeSpace/gco:CharacterString = gov.nasa.esdis.umm.pgeversionclass
    [=>/gmi:processingInformation/eos:EOS_Processing/gmi:identifier/gmd:MD_Identifier/gmd:description/gco:CharacterString = PGEVersionClass

    (The below x-path is CMR write only. This means that metadata records that gets translated from another metadata format to ISO will have the PGE Version Class written to this location in ISO in addition to the read & write path specified above)

    /gmi:MI_Metadata/gmd:dataQualityInfo/gmd:DQ_DataQuality/gmd:lineage/gmd:LI_Lineage/gmd:processStep/gmi:LE_ProcessStep [=>

    [=>/gmi:processingInformation/eos:EOS_Processing/gmi:softwareReference/gmd:CI_Citation/gmd:title/gco:CharacterString {PGEName}
    [=>/gmi:processingInformation/eos:EOS_Processing/gmi:softwareReference/gmd:CI_Citation/gmd:date gco:nilReason="unknown"
    [=>/gmi:processingInformation/eos:EOS_Processing/gmi:softwareReference/gmd:CI_Citation/gmd:edition/gco:CharacterString {PGEVersion}

    String

    For read & write:

    Both the PGE Name and PGE Version should be provided in the gmd:code field. The PGE Name should be preceded by the prefix "PGEName: " and the PGE Version should be preceded by the prefix "PGEVersion: ". It is not necessary to use any symbols to separate the PGE Version and PGE Class - all that is needed is the prefix.

    For write only:

    Provide the PGE Name

    Maps to the UMM-G element PGEVersionClass

    Provide the PGEName and PGEVersion value in the gmd:code field.title field. Provide the PGE Version in the gmd:edition field. The "gmd:date gco:nilReason="unknown" path is present because it is required by ISO, but is not needed by the CMR.


    Example Mapping

    Section
    Column
    width50%

    ISO 19115-2 MENDS

    No Format
    Example 1: CMR read & write
    <gmi:MI_Metadata>
       <gmd:dataQualityInfo>
          <gmd:DQ_DataQuality>
             <gmd:lineage>
                <gmd:LI_Lineage>
                   <gmd:processStep>
                      <gmi:LE_ProcessStep>
                         <gmd:description>
                            <gco:CharacterString>PGEVersionClass</gco:CharacterString>
                         </gmd:description>
                       <gmi:processingInformation>
                         <eos:EOS_Processing>
                            <gmi:identifier>
                                <gmd:MD_Identifier>
                                   <gmd:code>
                                      <gco:CharacterString>PGEName</gco:CharacterString>
                                      <gco:CharacterString>6.0.27<CharacterString>PGEName:OMCLDO2 Level 2 PGEVersion:2.0.0.9</gco:CharacterString>
                                   </gmd:code>
                                </gmd:MD_Identifier><gmd:codeSpace>
                            </gmi:identifier><gco:CharacterString>gov.nasa.esdis.umm.pgeversionclass</gco:CharacterString>
                         </eosgmd:EOS_Processing>codeSpace>
                       </gmi:processingInformation>  <gmd:description>
                       <gmi:processingInformation>
                         <eos:EOS_Processing><gco:CharacterString>PGEVersionClass</gco:CharacterString>
                             <gmi:identifier> </gmd:description>
                                <gmd</gmd:MD_Identifier>
                     </gmi:identifier> 
                   <gmd:codeSpace></eos:EOS_Processing>
                 </gmi:processingInformation>
               </gmi:LE_ProcessStep>
              <gco:CharacterString>gov.nasa.esdis.umm.pgeversionclass</gco:CharacterString></gmd:processStep>
           </gmd:LI_Lineage>
         </gmd:lineage>
       </gmd:DQ_DataQuality>
     </gmd:dataQualityInfo>
    </gmi:MI_Metadata>
    
    Example 2: CMR write only
    <gmi:MI_Metadata>
      <gmd:dataQualityInfo>
             </gmd:codeSpace><gmd:DQ_DataQuality>
          <gmd:lineage>
            <gmd:LI_Lineage>
                  </gmd:MD_Identifier><gmd:processStep>
                <gmi:LE_ProcessStep>
    
                 </gmi:identifier>  <gmi:processingInformation>
                         </eos<eos:EOS_Processing>
                       </gmi:processingInformation><gmi:softwareReference>
                       <gmi:processingInformation> <gmd:CI_Citation>
                         <eos:EOS_Processing> <gmd:title>
                             <gmi:identifier> <gco:CharacterString>OMCLDO2 Level 2</gco:CharacterString>
                          </gmd:title>
          <gmd:MD_Identifier>
                    <gmd:date gco:nilReason="unknown"/>
                 <gmd:description>
             <gmd:edition>
                             <gco:CharacterString> PGEVersionClass <CharacterString>2.0.0.9</gco:CharacterString>
                                  </gmd:description>
          edition>
                          </gmd:MDCI_Identifier>Citation>
                             </gmi:identifier> 
         softwareReference>
                    </eos:EOS_Processing>
                       </gmi:processingInformation>
                      </gmi:LE_ProcessStep>
                   </gmd:processStep>
                </gmd:LI_Lineage>
             </gmd:lineage>
          </gmd:DQ_DataQuality>
       </gmd:dataQualityInfo>
    </gmi:MI_Metadata>
    
    
    
    Column
    width50%

    UMM

    No Format
    "PGEVersionClass": {
          "PGEName": "PGEOMCLDO2 Level Name2",
          "PGEVersion": "62.0.0.279"
      },
    Expand
    titleISO 19115-2 SMAP

    ISO 19115-2 SMAP

    PGEVersionClass PGE Version Class currently does not map to ISO 19115-2 SMAP.

    UMM-G ElementISO PathTypeNotes
    PGEVersionClass

    N/A

    N/A

    N/A


    Example Mapping

    Section
    Column
    width50%

    ISO 19115-2 SMAP

    No Format
    N/A
    Column
    width50%

    UMM

    No Format
    N/A

    UMM Migration

    UMM Version 1.4.0Translation DirectionUMM Version 1.5.0
    Future Mappings




    History

    expand

    UMM Versioning

    titleISO 19115-1

    ISO 19115-1

    SpecificationPathTypeNotesISO 19115-1
    N/A

    N/A

    N/A

    Example Mapping
    VersionDateWhat Changed
    1.6.011/4/2019No changes were made for PGE Version Class during the transition from version 1.5.0 to 1.6.0.
    Section
    Column
    width50%

    ISO 19115-1

    No Format
    N/A
    Column
    width50%

    UMM

    No Format
    N/A

    History

    UMM Versioning

    VersionDateWhat Changed
    1.5.001/30/2019No changes were made for Granule UR PGE Version Class during the transition from version 1.4.0 to 1.5.0.
    1.4.008/01/2018No changes were made for Granule UR PGE Version Class during the transition from version 1.3.0 to 1.4.0.

    ARC Documentation

    VersionDateWhat ChangedAuthor
    1.00204/1511/2019Recommendations/priority matrix transferred from internal ARC documentation to wiki space