Best Practices
The version description should be brief and provide meaningful information about the version (i.e. beyond the version number itself). This could include what separates the current version of the dataset from the previous version. If it is the first version of a dataset, then the description can convey this. It may also include the date that the version of the dataset was released. If there are multiple versions of a dataset available at the same time, or there is a more recent version of the dataset available, then it is recommended that this be explained in the version description so that the user can determine whether they are accessing the most appropriate version of the dataset for their applications.
Examples:
<insert examples here>
Element Specification
Model | Element | Type | Constraints | Required? | Cardinality |
---|---|---|---|---|---|
UMM-C | VersionDescription | String | ? maximum number of characters | No | 1 |
ARC Priority Matrix
Priority Categorization | Justification |
---|---|
This element is categorized as highest priority when:
| |
Not applicable | |
Not applicable | |
The element is provided, and follows all applicable criteria specified in the best practices section above. |
Dialect Mappings
UMM Migration
None
Future Mappings
History
UMM Versioning
Version | Date | What Changed |
---|---|---|
1.0.0 | Initial Release |
ARC Documentation
Version | Date | What Changed | Author |
---|---|---|---|
1.0 | 4/19/18 | Recommendations/priority matrix transferred from internal ARC documentation to wiki space | Jeanne' le Roux |