...
Please see the expandable sections below for flowchart details.
| Expand |
|---|
|
Manual Review - Identify errors, discrepancies or omissions.
- Verify that all pertinent keywords have been applied.
- Verify that existing facets and other controlled keyword values are consistent and suitable for the data.
- Automated Review
- Check that the field has been populated.
- Check that the field is populated with a valid value from KMS.
- Check that the field value is not a duplicate.
- Check that the field length is not greater than the maximum characters allowed for each sub-element.
- Check that the Date format is valid.
|
| Expand |
|---|
|
- If a granule has a project short name in it, it must match to one that is defined in the collection.
- If removing a project from a collection, none of its granules can reference that project's short name.
|
| Expand |
|---|
|
ARC Priority Matrix
| Priority Categorization | Justification |
|---|
| Red = Hight Priority Finding | This element is categorized as highest priority when: - The Project Short Name does not comply with or exist within the KMS.
- The Project/Campaign listed is incorrect for the dataset
| | Yellow = Medium Priority Finding | Not Applicable | | Blue = Low Priority Finding | This element is provided as lowest priority when: - There is no Project/Campaign listed. While not required, providing a Project is highly recommended.
| | Green = No Findings/Issues | The element is provided and follows all applicable criteria specified in the best practices section above. |
|
UMM Versioning
| Version | Date | What Changed |
|---|
| 1.6.6 | | Initial version for WIKI entry. |
