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.
There are two sub-elements that comprise Access Constraints: Description and Value.
Examples:
AccessConstraints/Description: None
AccessConstraints/Value: 15
AccessConstraints/Description: Limited
AccessConstraints/Value: 4
AccessConstraints/Description: This product has full public access.
AccessConstraints/Value: 0
Providing Access Constraints is optional (Cardinality 0..1)
Model | Element | Type | Constraints | Required? | Cardinality | Notes |
---|---|---|---|---|---|---|
UMM-C | AccessConstraints/Description | String | 1 - 4000 characters | Yes, if applicable | 1 | Free-text description of the constraint. In DIF, this field is called Access_Constraints. In ECHO, this field is called RestrictionComment. |
UMM-C | AccessConstraints/Value | Number | n/a | No | 0..1 | Numeric 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. |
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.
|
|
ARC Automated Checks ARC uses the pyQuARC library for automated metadata checks. Please see the pyQuARC GitHub for more information. |
DIF 9 (Note: DIF-9 is being phased out and will no longer be supported after 2018) |
DIF 10Providing Access Constraints is optional (Cardinality 0..1)
|
ECHO 10Providing a Restriction Comment and/or Restriction Flag is optional (Cardinality 0..1)
|
ISO 19115-2 MENDSProviding Access Constraints is optional (Cardinality 0..1)
|
ISO 19115-2 SMAPProviding Access Constraints is optional (Cardinality 0..1)
|
None
Future Mappings
|
Version | Date | What Changed |
---|---|---|
1.15.5 | 12/3/2020 | No changes were made for Access Constraints during the transition from version 1.15.4 to 1.15.5 |
1.15.4 | 9/18/2020 | No changes were made for Access Constraints during the transition from version 1.15.3 to 1.15.4 |
1.15.3 | 7/1/2020 | No changes were made for Access Constraints during the transition from version 1.15.2 to 1.15.3 |
1.15.2 | 5/20/2020 | No changes were made for Access Constraints during the transition from version 1.15.1 to 1.15.2 |
1.15.1 | 3/25/2020 | No changes were made for Access Constraints during the transition from version 1.15.0 to 1.15.1 |
1.15.0 | 2/26/2020 | No changes were made for Access Constraints during the transition from version 1.14.0 to 1.15.0 |
1.14.0 | 10/21/2019 | No 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.0 | 01/22/2019 | No changes were made for Access Constraints during the transition from version 1.11.0 to 1.12.0. |
1.11.0 | 11/28/2018 | No 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. |
Version | Date | What Changed | Author |
---|---|---|---|
1.0 | 09/28/18 | Recommendations/priority matrix transferred from internal ARC documentation to wiki space |