Element Description

The Reprocessing Planned element states what reprocessing may be performed on the granule in the future.


Best Practices

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

Examples:

Reprocessing Planned: "Further updates are anticipated."

Reprocessing Planned: "True"

Reprocessing Planned: "Data will be reprocessed in March 2022 as part of the next version update."


Element Specification

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

ModelElementTypeConstraintsRequired?Cardinality
UMM-GDataGranule/ReprocessingPlannedString

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

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

Priority CategorizationJustification

Red = High Priority Finding

This element is categorized as highest priority when:

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

This element is categorized as medium priority when:

  • Evidence indicates that the Reprocessing Planned 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/Issues

The 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 Planned element is optional in ECHO 10 (Cardinality: 0..1)

SpecificationPathTypeConstraintsRequired in ECHO10?Cardinality
ECHO 10DataGranule/ReprocessingPlannedString

1 - 80 characters

No0..1


Example Mapping

ECHO 10

<DataGranule>
  <ReprocessingPlanned>Further updates are anticipated.</ReprocessingPlanned>
</DataGranule>

UMM

"DataGranule": {
  "ReprocessingPlanned": "Further updates are anticipated."
}

ISO 19115-2 MENDS

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

SpecificationPathTypeNotes
ISO 19115-2 MENDS

/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:resourceMaintenance/gmd:MD_MaintenanceInformation/gmd:maintenanceAndUpdateFrequency/gmd:MD_MaintenanceFrequencyCode codeList="https://cdn.earthdata.nasa.gov/iso/resources/Codelist/gmxCodelists.xml#MD_MaintenanceFrequencyCode" codeListValue="asNeeded" = asNeeded

with

/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:resourceMaintenance/gmd:MD_MaintenanceInformation/gmd:maintenanceNote/gco:CharacterString = ReprocessingPlanned: {the actual value}

String

Maps to the UMM-G element "DataGranule/ReprocessingPlanned"

Include the prefix 'ReprocessingPlanned: " 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:identificationInfo>
    <gmd:MD_DataIdentification>
      <gmd:resourceMaintenance>
        <gmd:MD_MaintenanceInformation>
          <gmd:maintenanceAndUpdateFrequency>
            <gmd:MD_MaintenanceFrequencyCode codeList="https://cdn.earthdata.nasa.gov/iso/resources/Codelist/gmxCodelists.xml#MD_MaintenanceFrequencyCode" codeListValue="asNeeded">asNeeded</gmd:MD_MaintenanceFrequencyCode>            
          </gmd:maintenanceAndUpdateFrequency>
          <gmd:maintenanceNote>
            <gco:CharacterString>ReprocessingPlanned: Further updates are anticipated.</gco:CharacterString>
          </gmd:maintenanceNote>
        </gmd:MD_MaintenanceInformation>
      </gmd:resourceMaintenance>
    </gmd:MD_DataIdentification>
  </gmd:identificationInfo>
</gmi:MI_Metadata>

UMM

"DataGranule": {
  "ReprocessingPlanned": "Further updates are anticipated."
}

ISO 19115-2 SMAP

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

SpecificationPathTypeNotes
ISO 19115-2 SMAP

N/A

N/A

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


Example Mapping

ISO 19115-2 SMAP

N/A

UMM

"DataGranule": {
  "ReprocessingPlanned": "Further updates are anticipated."
}

UMM Migration

N/A

History

UMM Versioning

VersionDateWhat Changed
1.6.011/4/2019No changes were made for Reprocessing Planned during the transition from version 1.5.0 to 1.6.0.
1.5.001/30/2019No changes were made for Reprocessing Planned during the transition from version 1.4.0 to 1.5.0.
1.4.008/01/2018No changes were made for Reprocessing Planned 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

  • No labels