Element Description
The File Naming Convention refers to the naming convention of the data set's (Collection's) data files along with a description of the granule file construction.
Best Practices
Convention should be a representation of what "fields" may make up the composite parts of a file name, such as dates and IDs.
Description should be used to describe the meaning of what is in the Convention field.
Examples:
FileNamingConvention/Convention: "ESDT.AYYYYDDD.HHMM.VID.YYYYDDDHHMMSS.Format"
FileNamingConvention/Description: "An example file name is VNP01.A2016202.2200.001.2016203071541.nc"
Element Specification
FileNamingConvention is not required. Only one FileNamingConvention may be provided (Cardinality: 0..1)
Model | Element | Type | Constraints | Required? | Cardinality | Notes |
---|---|---|---|---|---|---|
UMM-C | FileNamingConvention | Object | No | 0..1 | ||
UMM-C | FileNamingConvention/Convention | String | 1 to 4,000 characters | Yes | 1 | |
UMM-C | FileNamingConvention/Description | String | 1 to 4,000 characters | No | 0..1 | Required if OtherIdentifiers/Type is 'Other' |
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
None
History
UMM Versioning
Version | Date | What Changed |
---|---|---|
1.18.0 | 2024-03-18 | Added in version 1.18.0 |
ARC Documentation
Version | Date | What Changed | Author |
---|