The Description sub-element allows the author to provide information concerning accessing 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. The Value sub-element is used for special access control list (ACL) rules (http://en.wikipedia.org/wiki/Access_control_list) - for example, to hide metadata when it isn't ready for public consumption.
Providers use the AccessConstraint/Value element to specify various restriction levels with ACLs. 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'. There is no controlled mapping for what the values represent. ECHO has the exact same feature and there are many ACLs built in off of these types of rules.
AccessConstraints/Description: None
AccessConstraints/Value: 15
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 |
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
|
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*)
Example Mapping
|
ECHO 10 Providing a Campaign is optional. Multiple Campaigns may be provided if necessary (Cardinality 0..*)
|
ISO 19115-2 MENDS Providing a Project is optional. Multiple Projects may be provided if necessary (Cardinality 0..*)
|
ISO 19115-2 SMAP Providing a Project is optional. Multiple Projects may be provided if necessary (Cardinality 0..*)
Example Mapping
|
UMM Version 1.9.0 | Translation Direction | UMM Version 1.10.0 |
---|
ISO 19115-1 Providing a Project is optional. Multiple Projects may be provided if necessary (Cardinality 0..*)
|
Version | Date | What Changed |
---|---|---|
1.10.0 |
| |
1.9.0 |
Version | Date | What Changed | Author |
---|---|---|---|
1.0 | 8/24/18 | Recommendations/priority matrix transferred from internal ARC documentation to wiki space |