Page History

Table of Contents

style	circle

Element Description

Note: This wiki page is a draft/ work in progress

Data Dates... Dates is comprised of dates for when the data or resource itself changed in some way. This element is made of two sub-elements, type and date. The type describes what the date represents: a future review, when the resource was created, last updated, or planned for deletion. The date describes when the resource had an action performed on it or when an action on it will occur as described by the type element.

Best Practices

The Creation, Last Revision, Future Review, and Planned Deletion dates exist in various places in the different standards.

All data dates have been consolidated under this element. They will be typed and will all be represented by the ISO 8601 date and time conventions as part of the reconciliation process. In DIF 10 both the metadata and data dates are located under the DIF/Metadata_Dates element. The difference is that the sub-elements of Metadata_Creation, Metadata_Last_Revision, Metadata_Future_Review, and Metadata_Delete describe the metadata dates and the sub-elements of Data_Creation, Data_Last_Revision, Data_Future_Review, Data_Delete describe the resource dates.

Best Practices

Examples:

Element Specification

Model	Element	Type	Constraints	Required?	Cardinality	Notes
UMM-C

DataDates/String

1 - 10000 characters

No0.

	DataDate/Type=CREATE	Array	n/a	No	At least 1 is required	Dates related to activities involving the collection data. For example, Creation date is the date that the collection data first entered the data archive system.
UMM-C	DataDate/Type=UPDATE	Array	n/a	No	At least 1 is required
UMM-C	DataDate/Type=REVIEW	Array	n/a	No	At least 1 is required

.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
- Check that the purpose description is appropriate for the data set
Automated Review
- Check that the field has been populated
- Check that the field length is not greater than 1000 characters

Expand

title	CMR Validation

<>

Expand

title	ARC Metadata QA/QC

ARC Priority Matrix

Priority Categorization	Justification
	This element is categorized as highest priority when: The purpose contains spelling or grammatical errors The purpose is incorrect for the data (for example, a copy + paste error could result in the purpose for a different data set to appear in this field) A broken URL is provided in the purpose element
	This element is categorized as medium priority when: The information provided in the purpose element is better suited for a different metadata field (i.e. incorrect usage of the purpose field)
	This element is categorized as low priority when: A link provided in the purpose element needs to be updated from 'http' to 'https'
	The element is provided, and follows all applicable criteria specified in the best practices section above.

ARC Automated Rules

If novalue is provided, return is "np"
Otherwise, return is "OK"

Dialect Mappings

Expand

title	DIF 9

DIF 9 ^{(Note: DIF-9 is being phased out and will no longer be supported after 2018)}

1 - 1000 characters

Expand

title	DIF 10

DIF 10

Specification	Path	Type	Constraints	Required in DIF 10?	Cardinality	Notes
DIF 10

Summary/Purpose

String

Metadata_Dates/Data_Creation		Yes	1	Granular data was inserted (Changed to optional in DIF 10.3)
DIF 10	Metadata_Dates/Data_Last_Revision		Yes	1	Granular data was updated
DIF 10	Metadata_Dates/Data_Future_Review		No	0..1	Granular data is to be updated
DIF 10	Metadata_Dates/Data_Delete		No	0..1	Granular data removed

Example Mapping

Section

Column

width	50%

DIF 10

No Format

<Summary><Metadata_Dates>
 <Purpose>To test the feasibility of creating a comparative index of national-level environmental sustainability.</Purpose>
</Summary> <Metadata_Creation>2012-12-12</Metadata_Creation>
  <Metadata_Last_Revision>2018-10-03</Metadata_Last_Revision>
  <Data_Creation>2000-01-01</Data_Creation>
  <Data_Last_Revision>2000-01-01</Data_Last_Revision>
</Metadata_Dates>

Column

width	50%

UMM

No Format
"Purpose": "To test the feasibility of creating a comparative index of national-level environmental sustainability."INSERT EXAMPLE

1 - 4000 characters

Expand

title	ECHO 10

ECHO 10

Specification	Path	Type	Constraints	Required in ECHO10?	Cardinality	Notes
ECHO 10

SuggestedUsage

String

InsertTime	Yes	1	The insert date/time the collection entered data provider's database. This date is provided by the data provider
LastUpdate	Yes	1	The most recent update occurred on the data provider's database. This date is provided by the data provider.
DeleteTime	No	0..1	The

ECHO 10 schema definition for Suggested Usage: "This attribute describes how this collection or granule may be best used to support Earth science/global change research."

date the collection is or is planned to be deleted from the data provider's database.This date is provided by the data provider. If this date is in the past, the collection will be deleted during the next automated cleanup.

Example Mapping

Section

Column

width	50%

ECHO 10

No Format

<SuggestedUsage>To serve a wide user community by providing composite Landsat images and raw data for urban areas that can be used in interdisciplinary studies of remote sensing and the environment.</SuggestedUsage> <InsertTime>2008-12-02T00:00:00.000Z</InsertTime>
<LastUpdate>2008-12-02T00:00:00.000Z</LastUpdate>

Column

width	50%

UMM

No Format

"Purpose": "To serve a wide user community by providing composite Landsat images and raw data for urban areas that can be used in interdisciplinary studies of remote sensing and the environment."INSERT EXAMPLE

Version	Date	What Changed
1.10.0	5/2/2018	No changes were made for Purpose during the transition from version 1.9.0 to 1.10.0
1.9.0

Page tree

Versions Compared

Old Version 1

New Version 2

Key

Element Description

Note: This wiki page is a draft/ work in progress

Best Practices

Best Practices

Element Specification

Metadata Validation and QA/QC

UMM Migration

History

UMM Versioning

ARC Documentation