You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

Element Description

The Directory Name element is an element that was used historically by the GCMD internally to identify association, responsibility and/or ownership of a data set, service or supplemental information. Note that the use of this element is discouraged as it will be deprecated sometime in the future. 

Best Practices

Directory Name controlled vocabulary: http://gcmdservices.gsfc.nasa.gov/kms/concepts/concept_scheme/idnnode

Examples:

DirectoryName: "AMD/AU"

DirectoryName: "SOOS"



Element Specification

ModelElementTypeConstraintsRequired?Cardinality
UMM-C

DirectoryName

StringKMS controlledNo0..*


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
    • Identify errors, discrepancies or omissions
    • Proof 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

<>

ARC Priority Matrix

Priority CategorizationJustification

This element is categorized as highest priority when:

  • The element is not included at all.
  • The element is included but is empty.
  • The value in the element is identical to the Entry Title.
  • The value in the element is identical to the DOI.
  • The value in the element is incorrect for the data set.

Not applicable


Not applicable

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

ARC Automated Checks


Dialect Mappings

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

DIF 10


SpecificationPathTypeConstraintsRequired in DIF 10?CardinalityNotes
DIF 10/DIF/IDN_NodeStringKMS ControlledNo0..*


Enumeration Mapping

N/A

Example Mapping

DIF 10

<IDN_Node>
<Short_Name>USA/NSF</Short_Name>
</IDN_Node>
 

UMM

"DirectoryName" : "USA/NSF",

ECHO 10

SpecificationPathTypeConstraintsRequired in ECHO10?CardinalityNotes
ECHO 10N/AN/AN/AN/AN/A

This field only occurs in the DIF. When a DIF record is retrieved in the ECHO10 or ISO 19115 formats, this element will not be translated.


Enumeration Mapping

N/A

Example Mapping

ECHO 10

N/A

UMM

N/A



ISO 19115-2 MENDS

SpecificationPathTypeNotes
ISO 19115-2 MENDS

N/A

N/A

This field only occurs in the DIF. When a DIF record is retrieved in the ECHO10 or ISO 19115 formats, this element will not be translated.

Enumeration/Code List Mapping

N/A

Example Mapping

ISO 19115-2 MENDS

N/A

UMM

N/A



ISO 19115-2 SMAP

SpecificationPathTypeNotes
ISO 19115-2 SMAP

N/A

N/A

This field only occurs in the DIF. When a DIF record is retrieved in the ECHO10 or ISO 19115 formats, this element will not be translated.

Enumeration/Code List Mapping

N/A

Example Mapping

ISO 19115-2 SMAP

N/A

UMM

N/A



UMM Migration

N/A

Future Mappings

SpecificationPathTypeNotes
ISO 19115-1

N/A

N/A

N/A




History

UMM Versioning

VersionDateWhat Changed
1.10.0
No changes were made for DirectoryName during the transition from version 1.9.0 to 1.10.0
1.9.0

ARC Documentation

VersionDateWhat ChangedAuthor
1.08/29/18Recommendations/priority matrix transferred from internal ARC documentation to wiki space



  • No labels