Page History

Table of Contents

style	circle

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)

Model	Element	Type	Constraints	Required?	Cardinality
UMM-G	DataGranule/ReprocessingActual	String	1 - 80 characters	No	0..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-viewer	false

autofit	true
name	Copy of Wiki Page Metadata Evaluation Workflow-1939-51df84
width	1102
pages-to-display
id	98e5dc28-3252-4209-953f-66f1378e1cf4
align	Left
height	299

Please see the expandable sections below for flowchart details.

Expand

title	GCMD 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

title	CMR 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.

<>

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

Expand

title	ARC Metadata QA/QC

ARC Priority Matrix

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/issues	Metadata elements flagged green are free of issues and require no action on behalf of the data provider

Priority Categorization

Justification

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

.

ARC Automated Rules

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

Dialect Mappings

Expand

title	ECHO 10

ECHO 10

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

Specification	Path	Type	Constraints	Required in ECHO10?	Cardinality
ECHO 10	DataGranule/ReprocessingActual	String	1 - 80 characters	No	0..1

Example Mapping

Section

Column

width	50%

ECHO 10

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

Column

width	50%

UMM

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

Expand

title	ISO 19115-2 MENDS

ISO 19115-2 MENDS

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

Specification

Path

Type

Notes

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

Section

Column

width	50%

ISO 19115-2 MENDS

No Format

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

Column

width	50%

UMM

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

Expand

title	ISO 19115-2 SMAP

ISO 19115-2 SMAP

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

Specification	Path	Type	Notes
ISO 19115-2 SMAP	N/A	N/A	There is currently no mapping between UMM-G and ISO 19115-2 SMAP forReprocessing Actual.

Example Mapping

Section

Column

width	50%

ISO 19115-2 SMAP

No Format
N/A

Column

width	50%

UMM

No Format
N/A

UMM Migration

UMM Version 1.4.0	Translation Direction	UMM Version 1.5.0

Excerpt

hidden	true

Future Mappings

Expand

title	ISO 19115-1

ISO 19115-1

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

Specification	Path	Type	Notes
ISO 19115-1	N/A	N/A	N/A

Example Mapping

Section

Column

width	50%

ISO 19115-1

No Format
N/A

Column

width	50%

UMM

No Format
N/A

History

UMM Versioning

Version	Date	What Changed
1.6.0	11/4/2019	No changes were made for Reprocessing Actual during the transition from version 1.5.0 to 1.6.0.
1.5.0	01/30/2019	No changes were made for Reprocessing Actual during the transition from version 1.4.0 to 1.5.0.
1.4.0	08/01/2018	No changes were made for Reprocessing Actual during the transition from version 1.3.0 to 1.4.0.

ARC Documentation

Version	Date	What Changed	Author
1.0	02/15/2019	Recommendations/priority matrix transferred from internal ARC documentation to wiki space	Ingrid Garcia-Solera

Page tree

Versions Compared

Old Version 11

New Version 12

Key

Element Description

Best Practices

Element Specification

Metadata Validation and QA/QC

Dialect Mappings

ECHO 10

ISO 19115-2 MENDS

ISO 19115-2 SMAP

UMM Migration

Future Mappings

ISO 19115-1

History

UMM Versioning

ARC Documentation