Element Description

The Reprocessing Actual element states what reprocessing has been performed on the granule.

Best Practices

The Reprocessing Actual element describes whether reprocessing has been performed on the granule. It can also be used to provide details on when the reprocessing occurred or the type of reprocessing that occurred. Note that this field is intended to describe past reprocessing. To describe plans for future reprocessing, please use the Reprocessing Planned element. Information provided should be kept brief as there is an 80 character limit for this field.  

Examples:

Reprocessing Actual: "Reprocessed"

Reprocessing Actual: "Processed once"

Reprocessing Actual: "Reprocessed in 2008 and 2016 to include new variables."

Element Specification

The Reprocessing Actual element is optional for UMM-G (Cardinality: 0..1)

ModelElementTypeConstraintsRequired?Cardinality
UMM-GDataGranule/ReprocessingActualString

1 - 80 characters

No0..1



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).

<div style="width: 960px; height: 504px; margin: 10px; position: relative;"><iframe allowfullscreen frameborder="0" style="width:960px; height:504px" src="https://lucid.app/documents/embedded/98e5dc28-3252-4209-953f-66f1378e1cf4" id="aOKsQ0i2SArm"></iframe></div>


Please see the expandable sections below for flowchart details.


  • Manual Review
    • Identify errors, discrepancies, or omissions.
    • Proof read all content for conciseness and readability.
  • Automated Review
    • Check that the field has been populated.
    • Check that the field length is not greater than 1,030 characters.
    • Check that the field value does not match the Entry ID.
  • If this element is used, the description sub element is required.
  • The description must have at least 1 character and be no longer than 4000 characters in length.

ARC Priority Matrix

Red = High Priority Finding

This element is categorized as highest priority when:

  • Reprocessing Actual contains major spelling or grammatical errors.
Yellow = Medium Priority Finding

This element is categorized as medium priority when:

  • Evidence indicates that the Reprocessing Actual information provided is incorrect.
Blue = Low Priority Finding

This element is categorized as low priority when:

  • Any minor error or inconsistency is noted.
Green = No Findings/IssuesThe element is provided and follows all applicable criteria specified in the best practices section above.

ARC Automated Checks

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

Dialect Mappings

ECHO 10

The Reprocessing Actual element is optional in ECHO 10 (Cardinality: 0..1)

SpecificationPathTypeConstraintsRequired in ECHO10?Cardinality
ECHO 10DataGranule/ReprocessingActualString

1 - 80 characters

No0..1


Example Mapping

ECHO 10

<DataGranule>
  <ReprocessingActual>Reprocessed in 2008 and 2016 to include new variables.</ReprocessingActual>
</DataGranule>

UMM

"DataGranule": {
  "ReprocessingActual": "Reprocessed in 2008 and 2016 to include new variables."
}

ISO 19115-2 MENDS

The Reprocessing Actual element is optional in ISO-19115-2 (Cardinality: )

SpecificationPathTypeNotes
ISO 19115-2 MENDS/gmi:MI_Metadata/gmd:dataQualityInfo/gmd:DQ_DataQuality/gmd:lineage/gmd:LI_Lineage/gmd:processStep/gmi:LE_ProcessStep/gmd:description/gco:CharacterString = ReprocessingActual: {The actual value}

String

Maps to the UMM-G element "Reprocessed Actual"

Include the prefix 'ReprocessingActual: " before the value to ensure the information is mapped to the correct UMM-G field.


Example Mapping

ISO 19115-2 MENDS

<gmi:MI_Metadata>
  <gmd:dataQualityInfo>
    <gmd:DQ_DataQuality>
      <gmd:lineage>
        <gmd:LI_Lineage>
          <gmd:processStep>
            <gmi:LE_ProcessStep>
              </gmd:description>
                <gco:CharacterString>ReprocessingActual: Reprocessed in 2008 and 2016 to include new variables.</gco:CharacterString>
              </gmd:description>
            </gmi:LE_ProcessStep>
          </gmd:processStep>
        </gmd:LI_Lineage>
      </gmd:lineage>
    </gmd:DQ_DataQuality>
  </gmd:dataQualityInfo>
</gmi:MI_Metadata>

UMM

"DataGranule": {
  "ReprocessingActual": "Reprocessed in 2008 and 2016 to include new variables."
}

ISO 19115-2 SMAP

There is currently no mapping between UMM-G and ISO 19115-2 SMAP for Reprocessing Actual.

SpecificationPathTypeNotes
ISO 19115-2 SMAP

N/A

N/A

There is currently no mapping between UMM-G and ISO 19115-2 SMAP for Reprocessing Actual.


Example Mapping

ISO 19115-2 SMAP

N/A

UMM

N/A

UMM Migration

N/A

Future Mappings

ISO 19115-1

There is currently no mapping between UMM-G and ISO 19115-1 for Reprocessing Actual.

SpecificationPathTypeNotes
ISO 19115-1

N/A

N/A

N/A


Example Mapping

ISO 19115-1

N/A

UMM

N/A

History

UMM Versioning

VersionDateWhat Changed
1.6.011/4/2019No changes were made for Reprocessing Actual during the transition from version 1.5.0 to 1.6.0.
1.5.001/30/2019No changes were made for Reprocessing Actual during the transition from version 1.4.0 to 1.5.0.
1.4.008/01/2018No changes were made for Reprocessing Actual during the transition from version 1.3.0 to 1.4.0.

ARC Documentation

VersionDateWhat ChangedAuthor
1.002/15/2019Recommendations/priority matrix transferred from internal ARC documentation to wiki space

Ingrid Garcia-Solera