Versions Compared

Old Version 15

changes.mady.by.user Erich Reiter

Saved on

compared with

New Version 16

changes.mady.by.user Samuel Ayers

Saved on

Key

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

Table of Contents
stylecircle

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

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
titleGCMD Metadata QA/QC
  • 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.
Expand
titleCMR Validation
  • 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.
<>
Expand
titleARC Metadata QA/QC

ARC Priority Matrix

Priority CategorizationJustification

This element is categorized as highest priority when:

  • The information provided is incorrect for the granule
  • The information contains a spelling or grammatical error.

This element is categorized as medium priority when:

  • N/A

This element is categorized as medium priority when:

  • N/A
Red = high priority finding

High priority findings emphasize several characteristics of metadata quality including completeness, accuracy, and accessibility. For high priority findings, completeness is measured by a metadata record's compliance with required UMM elements. Any UMM required elements that are missing or incorrect will be prioritized as red. Accuracy is assessed by comparing how well the metadata record describes the actual data. Incorrect or outdated information will be prioritized as red. Lastly, accessibility is evaluated by any barriers that may occur in accessing the described data. Therefore, broken URLs, broken services and incorrect persistent identifiers are prioritized as red.

In general, high priority findings include (but are not limited to):

  • Broken URLs
  • Spelling and grammatical errors
  • Incorrect usage of controlled vocabulary
  • Required fields which are left blank
  • Outdated/incorrect information

Findings flagged as red are required to be addressed by the data provider.

Yellow = medium priority finding

Medium priority findings emphasize consistency and completeness. Consistency is assessed by ensuring that similar information is presented the same way across collections. Consistency makes searching for data easier and more reliable for the user. For yellow findings, the idea of completeness is expanded to include information beyond what is required by the UMM. In summary, information that makes the metadata more complete and facilitates discovery for the user beyond UMM requirements is prioritized as yellow.

In general, medium priority findings include (but are not limited to):

  • Highly recommended (but not required) content is missing from the metadata
  • Recommended revisions to existing content

Data providers are highly encouraged to address yellow findings and are encouraged to provide a rationale for unaddressed items.

Blue = low priority finding

Low priority findings also focus on completeness, consistency, and accuracy. Any additional information that may be provided to make the metadata more robust or complete is categorized as blue. Additionally, any minor inaccuracies or inconsistencies are categorized as blue. In general, low priority findings include (but are not limited to):

  • Minor errors and inconsistencies that are unlikely to have a significant impact on data discoverability 
  • Informational comments

Addressing blue findings are optional and up to the discretion of the data provider. Data providers are encouraged to provide a rationale for unaddressed blue items for the purposes of tracking updated quality metrics.

Green = no findings/issuesMetadata elements flagged green are free of issues and require no action on behalf of the data providerThe 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."


Dialect Mappings

Expand
titleECHO 10

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

Section
Column
width50%

ECHO 10

No Format
<DataGranule>
  <ReprocessingPlanned>Further updates are anticipated.</ReprocessingPlanned>
</DataGranule>
Column
width50%

UMM

No Format
"DataGranule": {
  "ReprocessingPlanned": "Further updates are anticipated."
}
Expand
titleISO 19115-2 MENDS

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

Section
Column
width50%

ISO 19115-2 MENDS

No Format
<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>
Column
width50%

UMM

No Format
"DataGranule": {
  "ReprocessingPlanned": "Further updates are anticipated."
}
Expand
titleISO 19115-2 SMAP

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 forReprocessing Planned.


Example Mapping

Section
Column
width50%

ISO 19115-2 SMAP

No Format
N/A
Column
width50%

UMM

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

UMM Migration

UMM Version 1.4.0Translation DirectionUMM Version 1.5.0



Excerpt
hiddentrue

Future Mappings

Expand
titleISO 19115-1

ISO 19115-1

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

SpecificationPathTypeNotes
ISO 19115-1

N/A

N/A

N/A


Example Mapping

Section
Column
width50%

ISO 19115-1

No Format
N/A
Column
width50%

UMM

No Format
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