Element Description
The Use Constraints element defines how data may or may not be used to assure the protection of privacy or intellectual property. This includes license information, or any special restrictions, legal prerequisites, terms and conditions, and/or limitations on using the data set.
Best Practices
There are two main uses for the Use Constraints elements. The first is to describe any specific purposes the data should not be used for. This information should be provided in the UseConstraints/Description field. The second is to provide license information about the data set. License information should be provided in either the UseConstraints/LicenseText or the UseConstraints/LicenseURL element. Along with the license information, users can explicitly state whether or not the data is free of charge and open for any use the user sees fit by using the FreeAndOpenData field.
Use Constraints/ Description
UseConstraints/Description is a free text field which should include information on any special restrictions, limitations, or terms and conditions for using the data. This should go beyond the terms laid out in the license. For example, a data set may be free and open to the public to use based on the license, but due to the quality of the data there may be limitations on the type of applications it should be used for. These types of special limitations should be stated in the description field. Providing a Use Constraints Description is optional.
Examples:
"Due to a sensor anomaly, data collected between October 4, 2007 and October 10, 2007 should not be used to conduct scientific research."
"Validation studies have shown significant error values in data collected over desert land cover types. Therefore, it is recommended that this data not be used to conduct analysis over areas of land containing desert."
License URL & License Text & Explicit notification of free and open data
License text can be provided directly in the metadata record, or as a URL that links to a web page which holds the license text. It is highly recommended that a License URL be provided if possible. With a License URL, the metadata remains unaffected by changes made to the license. License information can be provided in the License Text field OR as a License URL (you cannot provide both).
Note: Providing license information is required for all NASA EOSDIS data sets. It is recommended that the EOSDIS Data Use Policy (https://earthdata.nasa.gov/earth-observation-data/data-use-policy) be provided in the LicenseURL/Linkage field in order to meet this requirement.
License URL: The License URL field can be used to link to a web page which describes the license terms for the data set. License information is required for all NASA data sets. Use of the License URL field is strongly recommended. There are several sub-elements for License URL:
License URL/Linkage: The link to the license should be provided in this field. If providing a License URL, the Linkage element is required.
License URL/Protocol: The protocol is used to identify mechanisms/conventions for communication between different network devices (e.g. https, svn, ftp, etc.). Providing a protocol is optional.
License URL/Application Profile: The name of the application that can service the data. For example, if the URL points to a word document, then the application profile is MS-Word. If the URL points to a website, the application profile could be the name of a web browser (e.g. Chrome, Internet Explorer, etc.). Providing an application profile is optional.
License URL/Name: A name that identifies the URL, such as "License URL". Providing a name is completely optional.
License URL/Description: A description of the URL being provided. Providing a URL description is recommended but not required.
License URL/Function: "The function of the online resource. In ISO where this class originated the valid values are: download, information, offlineAccess, order, and search." Providing a function is optional.
License URL/Mime Type: MIME stands for "Multipurpose Internet Mail Extensions." Mime types are used to identify the nature and format of files provided on the Internet, and are typically used by internet browsers in order to determine how to properly process or display a document or file. Providing the Mime Type element in the metadata helps ensure that the URL contents will be properly displayed on the Web. Providing a Mime Type for License URL is optional. Mime Type is a controlled vocabulary field and should be chosen from the GCMD Mime Type keyword list.
Examples:
Linkage: https://earthdata.nasa.gov/earth-observation-data/data-use-policy
Protocol: https
Name: License URL
Description: The Earth Observing System Data and Information System (EOSDIS) data use policy for NASA data.
MimeType: text/html
Linkage: https://opendatacommons.org/licenses/pddl/1.0/
Description: Link to the full legal text of the license applied to this data set
MimeType: text/html
License Text: Use the License Text field to provide the license terms for the data set. The license text should be provided in full. A summary or plain english version of the license text does not count as the actual license text. As shown in the example below, license text is often lengthy and providing the full license text in the metadata should be avoided if possible. Use of the License Text field should be reserved for cases where it is not possible to provide a License URL.
Examples:
Free And Open Data: The free and open data field can be used to explicitly state whether or not the data is free of charge and open for any use the user sees fit. There are some assumptions that are made regarding the free and openness of a record if this element is not provided.
- For EOSDIS records that do not include a use constraint or contain a recognized license URL, the default assumption will be they are free and open.
- For EOSDIS records that include a non-recognized license URL or Text, the records will not be considered free and open.
- Only international data that have a recognized License URL or come from a "free and open designated" provider will be considered free and open.
EOSDIS providers can be designated as free and open by default if the provider so choses. Then all of their records will be assumed to be free and open unless the FreeAndOpenData element is used to state otherwise.
Element Specification
Model | Element | Type | Constraints | Required? | Cardinality |
---|---|---|---|---|---|
UMM-C | UseConstraints/Description | String | 1 - 4000 characters | No | 0..1 |
UMM-C | UseConstraints/FreeAndOpenData | Boolean | None | No | 0..1 |
Choice of:
Model | Element | Type | Constraints | Required? | Cardinality |
---|---|---|---|---|---|
UMM-C | UseConstraints/LicenseURL/Linkage | String | 1 - 1024 characters | Yes, if applicable | 1 |
UMM-C | UseConstraints/LicenseURL/Protocol | String | 1 - 80 characters | No | 0..1 |
UMM-C | UseConstraints/LicenseURL/ApplicationProfile | String | 1 - 1024 characters | No | 0..1 |
UMM-C | UseConstraints/LicenseURL/Name | String | 1 - 80 characters | No | 0..1 |
UMM-C | UseConstraints/LicenseURL/Description | String | 1 - 1024 characters | No | 0..1 |
UMM-C | UseConstraints/LicenseURL/Function | String | 1 - 1024 characters | No | 0..1 |
UMM-C | UseConstraints/LicenseURL/MimeType | String | No | 0..* |
or
Model | Element | Type | Constraints | Required? | Cardinality |
---|---|---|---|---|---|
UMM-C | UseConstraints/LicenseText | String | 1 - 20000 characters | Only required if LicenseURL is not provided | 0..1 |
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.
Dialect Mappings
UMM Migration
UMM Version 1.9.0 | Translation Direction | UMM Version 1.10.0 |
---|---|---|
UseConstraints | → | UseConstraints/Description |
n/a (new metadata element) | UseConstraints/LicenseURL/Linkage | |
n/a (new metadata element) | UseConstraints/LicenseURL/Protocol | |
n/a (new metadata element) | UseConstraints/LicenseURL/ApplicationProfile | |
n/a (new metadata element) | UseConstraints/LicenseURL/Name | |
n/a (new metadata element) | UseConstraints/LicenseURL/Description | |
n/a (new metadata element) | UseConstraints/LicenseURL/Function | |
n/a (new metadata element) | UseConstraints/LicenseURL/MimeType | |
n/a (new metadata element) | UseConstraints/LicenseText |
Future Mappings
History
UMM Versioning
1.16.2 is the current UMM-C version. No changes were made to this element since the last documented changes below.
Version | Date | What Changed |
---|---|---|
1.17.2 | 1/18/2023 | Added the EULAIdentifiers element under UseConstraints |
1.17.1 | 8/10/2022 | No changes were made for Use Constraints during the transition from version 1.17.0 to 1.17.1 |
1.17.0 | 5/11/2022 | No changes were made for Use Constraints during the transition from version 1.16.7 to 1.17.0 |
1.16.7 | 1/27/2022 | No changes were made for Use Constraints during the transition from version 1.16.6 to 1.16.7 |
1.16.6 | 12/1/2021 | FreeAndOpenData element was added. |
1.16.2 | 4/7/2021 | LicenseUrl was changed to LicenseURL. Description was change to a String. Use Constraints was added to ECHO 10, Use Constraints was changed in DIF 10 to allow for License_URL and License_Text. |
1.16.1 | 4/7/2021 | No changes were made for Use Constraints during the transition from version 1.16.0 to 1.16.1 |
1.16.0 | 3/24/2021 | No changes were made for Use Constraints during the transition from version 1.15.5 to 1.16.0 |
1.15.5 | 12/3/2020 | No changes were made for Use Constraints during the transition from version 1.15.4 to 1.15.5 |
1.15.4 | 9/18/2020 | No changes were made for Use Constraints during the transition from version 1.15.3 to 1.15.4 |
1.15.3 | 7/1/2020 | No changes were made for Use Constraints during the transition from version 1.15.2 to 1.15.3 |
1.15.2 | 5/20/2020 | No changes were made for Use Constraints during the transition from version 1.15.1 to 1.15.2 |
1.15.1 | 3/25/2020 | No changes were made for Use Constraints during the transition from version 1.15.0 to 1.15.1 |
1.15.0 | 2/26/2020 | No changes were made for Use Constraints during the transition from version 1.14.0 to 1.15.0 |
1.14.0 | 10/21/2019 | No changes were made for Use Constraints during the transition from version 1.13.0 to 1.14.0 |
1.13.0 | 04/11/2019 | No changes were made for Use Constraints during the transition from version 1.12.0 to 1.13.0 |
1.12.0 | 01/22/2019 | No changes were made for Use Constraints during the transition from version 1.11.0 to 1.12.0. |
1.11.0 | 11/28/2018 | No changes were made for Use Constraints during the transition from version 1.10.0 to 1.11.0. |
1.10.0 | 05/02/2018 |
|
1.0 - 1.9 | 2015 | Initial version |
ARC Documentation
Version | Date | What Changed | Author |
---|---|---|---|
1.0 | 09/28/2018 | Recommendations/priority matrix transferred from internal ARC documentation to wiki space | Jeanne' le Roux |