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

Compare with Current View Page History

« Previous Version 29 Next »

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

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

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.


ARC Priority Matrix

Priority CategorizationJustification

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

SpecificationPathTypeConstraintsRequired in DIF 10?CardinalityNotes
DIF 10Access_Constraints/DescriptionString1 - 4000 charactersYes, if applicable1A free-text description that details access constraints of the collection.
DIF 10Access_Constraints/Access_ControlIntegernumber from 0 - 255No0..1ACL value
DIF 10Access_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 data set 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 data set is free and available to the public.",
  "Value": "0"
  }

ECHO 10

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

SpecificationPathTypeConstraintsRequired in ECHO10?CardinalityNotes
ECHO 10RestrictionCommentString1 - 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.

ECHO 10RestrictionFlagDecimaln/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 data set is free and available to the public.</RestrictionComment>
<RestrictionFlag>0</RestrictionFlag>

UMM

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

ISO 19115-2 MENDS

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

SpecificationPathTypeNotes
ISO 19115-2 MENDS

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

String

Maps to the UMM element AccessConstraints/Description. The value of "Restriction Comment:" must be provided at the beginning of the string so that CMR can properly parse out the restriction text.

ISO 19115-2 MENDS/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:resourceConstraints/gmd:MD_LegalConstraints/gmd:otherConstraints/gco:CharacterString = Restriction Flag:StringMaps to the UMM element AccessConstraints/Value. The 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 data set 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 data set is free and available to the public.",
  "Value": "0"
  }

ISO 19115-2 SMAP

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

SpecificationPathTypeNotes
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:

String

Maps to the UMM element AccessConstraints/Description. The value of "Restriction Comment:" must be provided at the beginning of the string so that CMR can properly parse out the restriction text.

ISO 19115-2 SMAP/gmd:DS_Series/gmd:seriesMetadata/gmi:MI_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:resourceConstraints/ gmd:MD_LegalConstraints/gmd:otherConstraints/gco:CharacterString = Restriction Flag:StringMaps to the UMM element AccessConstraints/Value. The 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 data set 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 data set is free and available to the public.",
  "Value": "0"
  }

UMM Migration

None

Future Mappings

ISO 19115-1

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

SpecificationPathTypeNotes
ISO 19115-1/mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:resourceConstraints /mco:MD_LegalConstraints/mco:useLimitation/gco:CharacterString (prefix:'Restriction Comment: ')StringMaps to the UMM element AccessConstraints/Description. The value of "Restriction Comment:" must be provided at the beginning of the string so that CMR can properly parse out the restriction text.
ISO 19115-1/mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:resourceConstraints/mco:MD_LegalConstraints/mco:otherConstraints/gco:CharacterString (prefix:'Restriction Flag: ')StringMaps to the UMM element AccessConstraints/Value. The value of "Restriction Flag:" must be provided at the beginning of the string so that CMR can properly parse out the restriction value.

ISO 19115-1

ADD EXAMPLE

UMM

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


History

UMM Versioning

VersionDateWhat Changed
1.10.0

 

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

ARC Documentation

VersionDateWhat ChangedAuthor
1.09/28/18Recommendations/priority matrix transferred from internal ARC documentation to wiki space

Jeanne' le Roux
















  • No labels