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)

ModelElementTypeConstraintsRequired?CardinalityNotes
UMM-CFileNamingConventionObject


No0..1
UMM-CFileNamingConvention/ConventionString

1 to 4,000 characters

Yes1
UMM-CFileNamingConvention/DescriptionString

1 to 4,000 characters

No0..1Required if OtherIdentifiers/Type is 'Other'
The element is provided and follows all applicable criteria specified in the best practices section above

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. 

 

  • Manual Review
    • Check that there is at least a brief summary of the data.
    • Confirm that other URLs link to the appropriate web pages.
    • Identify errors, discrepancies or omissions.
    • Proof all content for conciseness and readability.
  • Automated Review
    • Check that the field length is not greater than 40,000 characters.
    • Check that the field length is at least 1 character.
    • Check that the convention field has been populated.
  • Must contain at least 1 character and be no longer than 4000 characters in length

ARC Priority Matrix

Priority CategorizationJustification

Red = High Priority Finding

This element is categorized as highest priority when:

  • Any File Naming Convention element contains a major spelling or grammatical error
  • A File Naming Convention element is not provided when it is applicable

Yellow = Medium Priority Finding

Not Applicable

Blue = Low Priority Finding

This element is categorized as low priority when:

  • Any minor suggestion

Green = No Findings/Issues

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

ARC Automated Checks

ARC uses the pyQuARC library for automated metadata checks. Please see the pyQuARC GitHub for more information.  

Dialect Mappings

DIF 9

DIF 9 (Note: DIF-9 has being phased out and is no longer supported since 2018)


DIF 10

Other_Identifiers is not required. Many Other_Identifiers may be provided (Cardinality: 0..1)

UMM-C ElementDIF 10 PathTypeConstraintsRequired in DIF 10?Cardinality
FileNamingConventionFile_Naming_ConventionObject
Yes0..1
FileNamingConvention/ConventionFile_Naming_Convention/IdentifierString1-4,000 charactersYes1
FileNamingConvention/DescriptionFile_Naming_Convention/DescriptionString1-4,000 charactersNo0..1


Example Mapping

DIF 10

<File_Naming_Convention>
    <Convention>ESDT.AYYYYDDD.HHMM.VID.YYYYDDDHHMMSS.Format</Convention>
    <Description>An example is VNP01.A2016202.2200.001.2016203071541.nc</Description>
</File_Naming_Convention>

UMM

"FileNamingConvention" {
  "Convention": "ESDT.AYYYYDDD.HHMM.VID.YYYYDDDHHMMSS.Format",
  "Description": "An example is VNP01.A2016202.2200.001.2016203071541.nc"
}

ECHO 10

OtherIdentifiers is not required. Many OtherIdentifier nodes may be provided (Cardinality: 0..1)

UMM-C ElementECHO 10 PathTypeConstraintsRequired in ECHO10?Cardinality
FileNamingConventionFileNamingConventionList
No0..1

FileNamingConvention/Convention

FileNamingConvention/ConventionString1-4,000 charactersYes1
FileNamingConvention/DescriptionFileNamingConvention//DescriptionString1-4,000 charactersNo0..1


Example Mapping


ECHO 10

<FileNamingConvention>
	<Convention>ESDT.AYYYYDDD.HHMM.VID.YYYYDDDHHMMSS.Format</Convention>
	<Description>An example is VNP01.A2016202.2200.001.2016203071541.nc</Description>
</FileNamingConvention>

UMM

"FileNamingConvention" {
  "Convention": "ESDT.AYYYYDDD.HHMM.VID.YYYYDDDHHMMSS.Format",
  "Description": "An example is VNP01.A2016202.2200.001.2016203071541.nc"
}



ISO 19115-2 MENDS

Abstract is required is ISO. Only one Abstract may be provided (Cardinality: 1)

UMM-C ElementISO PathTypeNotes
FileNamingConvention

/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:resourceFormat/gmd:MD_Format [=>

[=> /name "FileNamingConvention"

[=>/version :gco:nilReason "inapplicable"

Label
FileNamingConvention/Convention

[=>/specification "FileNameConvention: <value>

StringShares a Character String with ConventionDescription
FileNamingConvention/Description

[=>/specification "ConventionDescription: <value>

StringShares a Character String with FileNameConvention


Example Mapping

ISO 19115-2 MENDS

<gmd:identificationInfo>
    <gmd:MD_DataIdentification>
        <!-- File Naming Convention -->
        <gmd:resourceFormat>
            <gmd:MD_Format>
                <gmd:name>
                    <gco:CharacterString>FileNamingConvention</gco:CharacterString>
                </gmd:name>
                <gmd:version gco:nilReason="unknown"/>
                <gmd:specification>
                    <gco:CharacterString>
                        FileNameConvention: ESDT.AYYYYDDD.HHMM.VID.YYYYDDDHHMMSS.Format
                        ConventionDescription: An example is VNP01.A2016202.2200.001.2016203071541.nc
                    </gco:CharacterString>
                </gmd:specification>
            </gmd:MD_Format>
        </gmd:resourceFormat>
    </gmd:MD_DataIdentification>
</gmd:identificationInfo>

UMM

"FileNamingConvention" {
  "Convention": "ESDT.AYYYYDDD.HHMM.VID.YYYYDDDHHMMSS.Format",
  "Description": "An example is VNP01.A2016202.2200.001.2016203071541.nc"
}

ISO 19115-2 SMAP

No Mappings to this format

UMM-C ElementISO PathTypeNotes
FileNamingConvention

None


No mappings have been defined


Example Mapping

ISO 19115-2 SMAP

N/A

UMM

N/A

UMM Migration

None

History

UMM Versioning

VersionDateWhat Changed
1.18.02024-03-18Added in version 1.18.0

ARC Documentation

VersionDateWhat ChangedAuthor

  • No labels