|The name of the service.
|The long name of the service. It provides a human readable name for the service.
The type of the service. The valid values will come from the Keyword Management System (KMS), which is a controlled list.
The edition or version of the service. The version should be defined in the form x, y, and z. where 'x.y.z' means 'major.minor.incremental' version numbers. Typically, 'x' and 'y' are numbers (0 through 9) and 'z' is a number (0 through 99).
Information on what changes were included in the most recent version.
|The latest date when the service was most recently pushed to production for support and maintenance
A brief description of the service. For example, a description might contain information about what is the service, the purpose of the service, and the parameters (or variables) being invoked, and what are the sources of these data.
|The Specific URL to the back-end service.
Any resource-related URLs that include a project home pages, resource information pages, how-to documentation, example code snippets, thumbnail image, or other relevant information about the service.
Allows for the specification of Earth Science Service keywords that are representative of the service being described. The controlled vocabulary for Service Keywords is maintained in the KMS.
|Used to identify the list of supported data transformations. The term "data transformations" is a general term to describe a variety of ways data can be transformed by the service.
|Used to identify the list of supported methods of variable aggregation
The service provider, or organization, or institution responsible for developing, archiving, and/or distributing the service. Please note that ShortName and LongName values come from KMS which is a controlled list.
A contact to get information about that service, and how they may contact that person.
|A contact group to get information about that service, including how a user may contact that group.
Information about the quality of the service, or any quality assurance procedures followed in development.
Information about any constraints for accessing the service.
Information on how the service may or may not be used after access is granted. This includes any special restrictions, legal prerequisites, terms and conditions, and/or limitations on using the item. Providers may request acknowledgement of the item from users and claim no responsibility for quality and completeness. Use Constraints describes how the service may be used once access has been granted, and is distinct from Access Constraints, which refers to any constraints in accessing the service.
Words or phrases to further describe the service.
|Represents the UMM-S schema used to create the record. It records the schema name, version, and the location of where it lives on the web.