Element Description
The Provider Dates element presents dates associated with changes made to the granule in the database where it is stored. The Provider Dates include the date the granule was created, inserted or updated in its database, and the date the granule metadata will be deleted from the CMR.
Best Practices
There are 2 sub-elements which comprise Provider Dates. This includes the Date, which is the date that an event associated with the granule occurred; and the Provider Date Type, which specifies the type of event. The Provider Date Type must be selected from the following controlled vocabulary options:
- Create: This signifies the date that the granule file was created. The Create Date should always be in the past. This date should also be identical to the date provided in the DataGranule/ProductionDateTime field.
- Insert: The date the granule file was entered into the database. The Insert Date should always be in the past.
- Update: The date the granule file was last updated. The Update Date should always be in the past.
- Delete: The date that the granule metadata record should be deleted from the CMR. By this logic, the delete date should always be in the future - however, this is not enforced by the schema.
The Date should be provided in a date-time format, and comply with the ISO 8601 Standard, which is an International Standard for the representation of dates and times. Typically, the date is provided in YYYY-MM-DD format and the time is provided in Coordinated Universal Time (UTC).
At least 1 Provider Date is required. If only 1 Provider Date is supplied, then it is highly recommended that the Create Date be provided. This element can be repeated up to 4 times to include each of the different Provider Date Types (Create, Insert, Update, Delete). The same type cannot be repeated (i.e. there can only be 1 Update Date, 1 Insert Date, etc.). Both the Date and Type sub-elements must be provided for each.
Examples:
Type: "Insert"
Date: "2016-12-23T13:46:12Z"
Type: "Update"
Date: "2018-11-13T22:23:00Z"
Element Specification
At least 1 Provider Date is required (Cardinality 1..4). For each Provider Date, the Date and Type must be provided.
Model | Element | Type | Constraints | Required? | Cardinality | Notes |
---|---|---|---|---|---|---|
UMM-G | ProviderDates/Type | Enumeration | Create Insert Update Delete | Yes | 1..4 | At least 1 provider date type is required with it being suggested that "Create" is provided. |
UMM-G | ProviderDates/Date | Date-Time | N/A | Yes | 1..4 | The provider date must also be given for each provider type provided. |
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.
Dialect Mappings
UMM Migration
UMM Version 1.4.0 | Translation Direction | UMM Version 1.5.0 |
---|---|---|
History
UMM Versioning
Version | Date | What Changed |
---|---|---|
1.6.0 | 11/4/2019 | No changes were made for Provider Dates during the transition from version 1.5.0 to 1.6.0. |
1.5.0 | 01/30/2019 | No changes were made for Provider Dates during the transition from version 1.4.0 to 1.5.0. |
1.4.0 | 08/01/2018 |
ARC Documentation
Version | Date | What Changed | Author |
---|---|---|---|
1.0 | 02/15/2019 | Recommendations/priority matrix transferred from internal ARC documentation to wiki space |