Page tree
Skip to end of metadata
Go to start of metadata

Element Description

The Access Constraints element describes any restrictions imposed on data access. Access Constraints can be described in a free text field with 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, and limitations and/or warnings on obtaining the data. Examples of values include: Public, In-house, Limited, and None. 
  • Value: Providers have the option to use the AccessConstraints/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)

ModelElementTypeConstraintsRequired?CardinalityNotes
UMM-CAccessConstraints/DescriptionString1 - 4000 charactersYes, if applicable1Free-text description of the constraint. In DIF, this field is called Access_Constraints. In ECHO, this field is called RestrictionComment.
UMM-CAccessConstraints/ValueNumbern/aNo0..1Numeric value (ACL) used to restrict (or not restrict) access to this collection. In DIF, this field is called Access_Control. In ECHO, this field is called RestrictionFlag. 

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).

Loading...

Please see the expandable sections below for flowchart details.


  • Manual Review
    • Confirm that the 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 4,000 characters.
    • Check for potential broken links.
  • If this element is used, the description sub element is required
  • The description must have 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:

  • The information provided is not related to the element.
  • The Access Constraints Description is inaccurate for the dataset.
  • The Access Constraints Description include major spelling or grammatical errors.

Yellow = Medium Priority Finding

This element is categorized as medium priority when:

  • The information provided is not related to access constraint information (i.e. incorrect or non-optimal usage of the metadata element).

Blue = Low Priority Finding

This element is categorized as low priority when:

  • The Access Constraints Description includes a re-direct link.

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 (Note: DIF-9 is being phased out and will no longer be supported after 2018)


DIF 10

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

UMM-C ElementDIF 10 PathTypeConstraintsRequired in DIF 10?CardinalityNotes
AccessConstraints/DescriptionAccess_Constraints/DescriptionString1 - 4000 charactersYes, if applicable1A free-text description that details access constraints of the collection.
AccessConstraints/Value
Access_Constraints/Access_ControlIntegernumber from 0 - 255No0..1ACL value

Access_Constraints/Access_Control_DescriptionString1 - 4000 charactersNo0..1
The definition of the ACL value. This is defined by the provider. This element does not map to UMM.


Example Mapping

DIF 10

<Access_Constraints>
  <Description>None. This dataset is free and available to the public.</Description>
  <Access_Control>0</Access_Control>
  <Access_Control_Description>No restriction</Access_Control_Description>
</Access_Constraints>

UMM

"AccessConstraints" : {
  "Description": "None. This dataset is free and available to the public.",
  "Value": "0"
  }

ECHO 10

Providing a Restriction Comment and/or Restriction Flag is optional (Cardinality 0..1)

UMM-C ElementECHO 10 PathTypeConstraintsRequired in ECHO10?CardinalityNotes
AccessConstraints/DescriptionRestrictionCommentString1 - 1024 charactersNo0..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.

AccessConstraints/Value
RestrictionFlagDecimaln/aNo0..1

A numerical value that indicates the type of restriction that applies on this collection (i.e. an ACL value).


Example
Mapping

ECHO 10

<RestrictionComment>None. This dataset is free and available to the public.</RestrictionComment>
<RestrictionFlag>0</RestrictionFlag>

UMM

"AccessConstraints" : {
  "Description": "None. This dataset is free and available to the public.",
  "Value": "0"
  }

ISO 19115-2 MENDS

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

UMM-C ElementISO PathTypeNotes
AccessConstraints/Description

/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:resourceConstraints/gmd:MD_LegalConstraints/gmd:useLimitation/gco:CharacterString = Restriction Comment:

String

The value of "Restriction Comment:" must be provided at the beginning of the string so that CMR can properly parse out the restriction text.

AccessConstraints/Value
/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:resourceConstraints/gmd:MD_LegalConstraints/gmd:otherConstraints/gco:CharacterString = Restriction Flag:StringThe value of "Restriction Flag:" must be provided at the beginning of the string so that CMR can properly parse out the restriction value.


Example Mapping

ISO 19115-2 MENDS

<gmi:MI_Metadata>
  ...
  <gmd:identificationInfo>
  <gmd:MD_DataIdentification>
    ...
    <gmd:resourceConstraints>
      <gmd:MD_LegalConstraints>
        <gmd:useLimitation>
          <gco:CharacterString>Restriction Comment: None. This dataset is free and available to the public.</gco:CharacterString>
        </gmd:useLimitation>
        <gmd:otherConstraints>
          <gco:CharacterString>Restriction Flag: 0</gco:CharacterString>
        </gmd:otherConstraints>
      </gmd:MD_LegalConstraints>
    </gmd:resourceConstraints>
    ...
  </gmd:MD_DataIdentification>
  </gmd:identificationInfo>
  ...
</gmi:MI_Metadata>

UMM

"AccessConstraints" : {
  "Description": "None. This dataset is free and available to the public.",
  "Value": "0"
  }

ISO 19115-2 SMAP

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

UMM-C ElementISO PathTypeNotes
AccessConstraints/Description

/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:resourceConstraints/ gmd:MD_LegalConstraints/gmd:useLimitation/gco:CharacterString = Restriction Comment:

String

The value of "Restriction Comment:" must be provided at the beginning of the string so that CMR can properly parse out the restriction text.

AccessConstraints/Value
/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:resourceConstraints/ gmd:MD_LegalConstraints/gmd:otherConstraints/gco:CharacterString = Restriction Flag:StringThe value of "Restriction Flag:" must be provided at the beginning of the string so that CMR can properly parse out the restriction value.


Example Mapping

ISO 19115-2 SMAP

<gmd:DS_Series>
  <gmd:seriesMetadata>
    <gmi:MI_Metadata>
      ...
      <gmd:identificationInfo>
        <gmd:MD_DataIdentification>
          ...
          <gmd:resourceConstraints>
            <gmd:MD_LegalConstraints>
              <gmd:useLimitation>
                <gco:CharacterString>Restriction Comment: None. This dataset is free and available to the public.</gco:CharacterString>
              </gmd:useLimitation>
              <gmd:otherConstraints>
                <gco:CharacterString>Restriction Flag: 0</gco:CharacterString>
              </gmd:otherConstraints>
            </gmd:MD_LegalConstraints>
          </gmd:resourceConstraints>
        ...
        </gmd:MD_DataIdentification>
      </gmd:identificationInfo>
    </gmi:MI_Metadata>
  </gmd:seriesMetadata>
</gmd:DS_Series>

UMM

"AccessConstraints" : {
  "Description": "None. This dataset is free and available to the public.",
  "Value": "0"
  }

UMM Migration

None



History

UMM Versioning

VersionDateWhat Changed
1.15.512/3/2020No changes were made for Access Constraints during the transition from version 1.15.4 to 1.15.5
1.15.49/18/2020No changes were made for Access Constraints during the transition from version 1.15.3 to 1.15.4
1.15.37/1/2020No changes were made for Access Constraints during the transition from version 1.15.2 to 1.15.3
1.15.25/20/2020No changes were made for Access Constraints during the transition from version 1.15.1 to 1.15.2
1.15.13/25/2020No changes were made for Access Constraints during the transition from version 1.15.0 to 1.15.1
1.15.02/26/2020No changes were made for Access Constraints during the transition from version 1.14.0 to 1.15.0
1.14.010/21/2019No changes were made for Access Constraints during the transition from version 1.13.0 to 1.14.0
1.13.0

04/11/2019

No changes were made for Access Constraints during the transition from version 1.12.0 to 1.13.0
1.12.001/22/2019No changes were made for Access Constraints during the transition from version 1.11.0 to 1.12.0.
1.11.011/28/2018No changes were made for Access Constraints during the transition from version 1.10.0 to 1.11.0.
1.10.0

05/02/2018 

No changes were made for Access Constraints during the transition from version 1.9.0 to 1.10.0.

ARC Documentation

VersionDateWhat ChangedAuthor
1.009/28/18Recommendations/priority matrix transferred from internal ARC documentation to wiki space
  • No labels