Access Constraints

Element Description

Note: this page is a draft/ work in progress

The Access Constraints element describes any restrictions imposed on data access. Access Constraints can be described in a free text field. There is also the option to provide an access control list (ACL) value.

Best Practices

There are two sub-elements that comprise Access Constraints: Description and Value.

Description: The Description sub-element allows the author to provide information concerning access constraints. This includes any special restrictions, legal prerequisites, limitations and/or warnings on obtaining the data. Examples of values include: Public, In-house, Limited, and None.

Value: Providers use the AccessConstraint/Value element to specify various restriction levels with access control lists (ACLs). The provider is responsible for defining their own ACL rules (http://en.wikipedia.org/wiki/Access_control_list). For example, a provider might specify a service level ACL that hides all items (collections for this example) with a value element set to '15.0' in order to hide metadata when it isn't ready for public consumption. There is no controlled mapping for what the values represent.

Examples:

AccessConstraints/Description: None

AccessConstraints/Value: 15

AccessConstraints/Description: Limited

AccessConstraints/Value: 4

AccessConstraints/Description: This product has full public access.

AccessConstraints/Value: 0

Element Specification

Providing Access Constraints is optional. (Cardinality 0..1*)

Model	Element	Type	Usable Valid Values	Constraints	Required?	Cardinality	Notes
UMM-Common	AccessConstraints/Description	String	n/a	1 - 4000 characters	Yes, if provided	1	Free-text description of the constraint. In DIF, this field is called Access_Constraint. In ECHO, this field is called RestrictionComment.
UMM-Common	AccessConstraints/Value	Number	n/a	n/a	No	0..1	Numeric value that is used with Access Control Language (ACLs) to restrict access to this collection. For example, a provider might specify a collection level ACL that hides all collections with a value element set to 15. In ECHO, this field is called RestrictionFlag. This field does not exist in DIF

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.

GCMD Metadata QA/QC

CMR Validation

ARC Metadata QA/QC

ARC Priority Matrix

Priority Categorization	Justification
	This element is categorized as highest priority when: The information provided is not related to the element The access constraints described are inaccurate for the data set The access constraints description includes spelling or grammatical errors
	Not applicable
	Not applicable
	The element is provided, and follows all applicable criteria specified in the best practices section above.

ARC Automated Checks

Description
- If no value is provided, return is: "np"
- Otherwise, return is "OK"
Value
- If no value is provided, return is: "np"
- Otherwise, return is "OK"

Dialect Mappings

DIF 9

DIF 9

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

DIF 10

DIF 10

Providing Access Constraints is optional. (Cardinality 0..1*)

Specification	Path	Type	Usable Valid Values	Constraints	Required in DIF 10?	Cardinality	Notes
DIF 10	Access_Constraints/Description	String	n/a	1 - 4000 characters	No	1	This sub-element is a free-text description that details access constraints of this collection
DIF 10	Access_Constraints/Access_Control	Integer	n/a	0 - 255 characters	Yes, if provided	0..1
DIF 10	Access_Constraints/Access_Control_Description	String	n/a	1 - 4000 characters	No	0..1	This sub-element is a free-text description that details the Access Control

Example Mapping

DIF 10

<Access_Constraints>
  <Description>None. The paper is open access</Description>
</Access_Constraints>

UMM

"AccessConstraints" : {
  "Description": "None"
  }

ECHO 10

ECHO 10

Providing a Campaign is optional. Multiple Campaigns may be provided if necessary (Cardinality 0..*)

Specification	Path	Type	Usable Valid Values	Constraints	Required in ECHO10?	Cardinality	Notes
ECHO 10	RestrictionComment	string	n/a	1 - 1024 characters	No	0..1	Restrictions and legal prerequisites for accessing the collection. These include any access constraints applied to assure the protection of privacy or intellectual property, and any special restrictions or limitations on obtaining the collection. These restrictions differ from Use Restrictions in that they only apply to access.
ECHO 10	RestrictionFlag	decimal	n/a	n/a	No	0..1	A numerical value indicates the type of restriction that applies on this collection

Example Mapping

ECHO 10

<RestrictionComment>None</RestrictionComment>
<RestrictionFlag>0</RestrictionFlag>

UMM

AccessConstraints/Description
 None

ISO 19115-2 MENDS

ISO 19115-2 MENDS

Providing a Project is optional. Multiple Projects may be provided if necessary (Cardinality 0..*)

Specification	Path	Type	Notes
ISO 19115-2 MENDS	/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:operation/gmi:MI_Operation/gmi:identifier/gmd:MD_Identifier/gmd:code/gco:CharacterString with /gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:operation/ gmi:MI_Operation/gmi:identifier/gmd:MD_Identifier/gmd:codeSpace/gco:CharacterString = gov.nasa.esdis.umm.projectshortname	String	Maps to the UMM element Project/ShortName. A list of valid project short names can be found in the KMS. For each project listed, a short name is required by CMR. The short name value goes in the gmd:code field. The value of "gov.nasa.esdis.umm.projectshortname" should be provided in the gmd:codeSpace field so that CMR can properly parse out the project short name from the ISO metadata.
ISO 19115-2 MENDS	/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:operation/gmi:MI_Operation/gmi:identifier/gmd:MD_Identifier/gmd:description/gco:CharacterString	String	Maps to the UMM element Project/LongName. A list of valid project long names can be found in the KMS. Providing a project long name is optional, but is highly recommended.
ISO 19115-2 MENDS	/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:operation/gmi:MI_Operation/ gmi:childOperation/gmi:MI_Operation/gmi:identifier/gmd:MD_Identifier/gmd:code/gco:CharacterString with /gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:operation/gmi:MI_Operation gmi:childOperation/gmi:MI_Operation/gmi:identifier/gmd:MD_Identifier/gmd:codeSpace/gco:CharacterString = gov.nasa.esdis.umm.campaignshortname	String	Maps to the UMM element Project/Campaign. The campaign value goes in the gmd:code field. Multiple Campaigns can be provided if necessary. The value of "gov.nasa.esdis.umm.campaignshortname" should be provided in the gmd:codeSpace field so that CMR can properly parse out the campaign name from the ISO metadata.
ISO 19115-2 MENDS	/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:operation/gmi:MI_Operation/gmi:description/gco:CharacterString = StartDate:	String	Maps to the UMM element Project/StartDate. The string "StartDate: " must be provided as part of the character string in order for CMR to properly parse out the project start date from the ISO metadata.
ISO 19115-2 MENDS	/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:operation/gmi:MI_Operation/gmi:description/gco:CharacterString = EndDate:	String	Maps to the UMM element Project/EndDate. The string "EndDate: " must be provided as part of the character string in order for CMR to properly parse out the project end date from the ISO metadata.

Example Mapping

ISO 19115-2 MENDS

<gmi:MI_Metadata>
...
  <gmi:acquisitionInformation>
    <gmi:MI_AcquisitionInformation>
      <gmi:operation>
        <gmi:MI_Operation>
          <gmi:identifier>
            <gmd:MD_Identifier>
              <gmd:code>
                <gco:CharacterString>GCPEx</gco:CharacterString>
              </gmd:code>
              <gmd:codeSpace>
                <gco:CharacterString>gov.nasa.esdis.umm.projectshortname</gco:CharacterString>
              </gmd:codeSpace>
              <gmd:description>
                <gco:CharacterString>GPM Cold Season Precipitation Experiment</gco:CharacterString>
              </gmd:description>
            </gmd:MD_Identifier>
          </gmi:identifier>
        </gmi:MI_Operation>
      </gmi:operation>
    </gmi:MI_AcquisitionInformation>
  </gmi:acquisitionInformation>
...
</gmi:MI_Metadata>

UMM

Projects: [
  {
    ShortName: "GCPEx",
    LongName: "GPM Cold Season Precipitation Experiment"
  }
]

ISO 19115-2 SMAP

ISO 19115-2 SMAP

Providing a Project is optional. Multiple Projects may be provided if necessary (Cardinality 0..*)

Specification	Path	Type	Notes
ISO 19115-2 SMAP	/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:operation/ gmi:MI_Operation/gmi:identifier/gmd:MD_Identifier/gmd:code/gco:CharacterString with /gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:operation/ gmi:MI_Operation/gmi:identifier/gmd:MD_Identifier/gmd:codeSpace/gco:CharacterString = gov.nasa.esdis.umm.projectshortname	String	Maps to the UMM element Project/ShortName. A list of valid project short names can be found in the KMS. For each project listed, a short name is required by CMR. The short name value goes in the gmd:code field. The value of "gov.nasa.esdis.umm.projectshortname" should be provided in the gmd:codeSpace field so that CMR can properly parse out the project short name from the ISO metadata.
ISO 19115-2 SMAP	/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:operation/ gmi:MI_Operation/gmi:identifier/gmd:MD_Identifier/gmd:description/gco:CharacterString	String	Maps to the UMM element Project/LongName. A list of valid project long names can be found in the KMS. Providing a project long name is optional, but is highly recommended.
ISO 19115-2 SMAP	/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:operation/gmi:MI_Operation/ gmi:childOperation/gmi:MI_Operation/gmi:identifier/gmd:MD_Identifier/gmd:code/gco:CharacterString with /gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:operation/gmi:MI_Operation gmi:childOperation/gmi:MI_Operation/gmi:identifier/gmd:MD_Identifier/gmd:codeSpace/gco:CharacterString = gov.nasa.esdis.umm.campaignshortname	String	Maps to the UMM element Project/Campaign. The campaign value goes in the gmd:code field. Multiple Campaigns can be provided if necessary. The value of "gov.nasa.esdis.umm.campaignshortname" should be provided in the gmd:codeSpace field so that CMR can properly parse out the campaign name from the ISO metadata.
ISO 19115-2 SMAP	/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:operation/ gmi:MI_Operation/gmi:description/gco:CharacterString = StartDate:	String	Maps to the UMM element Project/StartDate. The string "StartDate: " must be provided as part of the character string in order for CMR to properly parse out the project start date from the ISO metadata.
ISO 19115-2 SMAP	/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmi:acquisitionInformation/gmi:MI_AcquisitionInformation/gmi:operation/ gmi:MI_Operation/gmi:description/gco:CharacterString = EndDate:	String	Maps to the UMM element Project/EndDate. The string "EndDate: " must be provided as part of the character string in order for CMR to properly parse out the project end date from the ISO metadata.

Example Mapping

ISO 19115-2 SMAP

<gmd:DS_Series>
<gmd:seriesMetadata>
<gmi:MI_Metadata>
...
  <gmi:acquisitionInformation>
    <gmi:MI_AcquisitionInformation>
      <gmi:operation>
        <gmi:MI_Operation>
          <gmi:identifier>
            <gmd:MD_Identifier>
              <gmd:code>
                <gco:CharacterString>GCPEx</gco:CharacterString>
              </gmd:code>
              <gmd:codeSpace>
                <gco:CharacterString>gov.nasa.esdis.umm.projectshortname</gco:CharacterString>
              </gmd:codeSpace>
              <gmd:description>
                <gco:CharacterString>GPM Cold Season Precipitation Experiment</gco:CharacterString>
              </gmd:description>
            </gmd:MD_Identifier>
          </gmi:identifier>
        </gmi:MI_Operation>
      </gmi:operation>
    </gmi:MI_AcquisitionInformation>
  </gmi:acquisitionInformation>
...
</gmi:MI_Metadata>
</gmd:seriesMetadata>
</gmd:DS_Series>

UMM

Projects: [
  {
    ShortName: "GCPEx",
    LongName: "GPM Cold Season Precipitation Experiment"
  }
]

UMM Migration

UMM Version 1.9.0

Translation

Direction

UMM Version 1.10.0

Future Mappings

ISO 19115-1

ISO 19115-1

Providing a Project is optional. Multiple Projects may be provided if necessary (Cardinality 0..*)

Specification	Path	Type	Notes

ISO 19115-1

UMM

Projects: [
  {
    ShortName: "GCPEx",
    LongName: "GPM Cold Season Precipitation Experiment"
  }
]

History

UMM Versioning

Version	Date	What Changed
1.10.0	02 May 2018
1.9.0

ARC Documentation

Version	Date	What Changed	Author
1.0	8/24/18	Recommendations/priority matrix transferred from internal ARC documentation to wiki space	Kaylin Bugbee

Page tree

Access Constraints

Element Description

Note: this page is a draft/ work in progress

Best Practices

Element Specification

Metadata Validation and QA/QC

Dialect Mappings

UMM Migration

Future Mappings

History

UMM Versioning

ARC Documentation