Page History
Author(s): user-b4abf
| Section | |||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||
|
...
|
Background:
Origin of Version -- In the early days of EOSDIS, the priority was on defining systems to support large flagship missions such as Aqua and Terra. Since the data produced by these flagship missions was expected to be collected and supported for decades, it was recognized that the data products would be periodically reprocessed using new algorithms that incorporated the latest scientific understanding. The resultant data products could be significantly different from the previously created data products. To distinguish between the data produced by different processing algorithms, the ECS data model incorporated a Version that was meant to represent a specific version of the algorithms that were used to produce a new “version” of a Collection.
...
The following table demonstrates the mapping of some existing "Version" fields into the new definition of Version for UMM-C. Note that for existing versions that use alphabetic indicators, e.g., 1a, we map the alphabetic character to the index of the character within the alphabet. That is, a->1, b->2, etc. See section 4) below for further guidance on choosing good Version fields.
| Current Version definition | New UMM-C Version definition |
|---|---|
| 1.000 | /Version/ProcessingVersion/MajorVersion = 1 /Version/ProcessingVersion/MinorVersion = 0 |
| 0001 | /Version/ProcessingVersion/MajorVersion = 1 /Version/ProcessingVersion/MinorVersion= 0 |
| 1a | /Version/ProcessingVersion/MajorVersion = 1 /Version/ProcessingVersion/MinorVersion= 1 |
| 0.0.1.b | /Version/ProcessingVersion/MajorVersion = 1 /Version/ProcessingVersion/MinorVersion= 2 |
| 2_beta | /Version/ProcessingVersion/MajorVersion = 2 /Version/ProcessingVersion/MinorVersion= 0 |
| alpha1 | /Version/ProcessingVersion/MajorVersion = 1 /Version/ProcessingVersion/MinorVersion= 0 |
2) Provide a new field, ProducerVersionID,
...
A new major version number should represent a version of the algorithms that creates a new version of the data containing additional scientific insights. A minor version number should represent an incremental improvement in the algorithms that improve the quality of the data (e.g., new calibration tables) without altering the scientific models of the major version.
The sections below detail the proposed changes based on the analysis done by the ECSE team:
...
/DataIdentification/Version/ProcessingVersion/MinorVersion
2) A new field, ProducerVersionID, will be added to the DataIdentification section of UMM-C. The ProducerVersionID will be a free text field and will not be part of the unique identifier for a collection. The field path will be:
/DataIdentification/ProducerVersionID
...
Changes to UMM-Common fields
...
Interoperability Considerations
N/A
Changes to CMR
The translation of the legacy formats into UMM will to take into account the translation process described above.
...
Version should be presented as Major.MInor, such as 3.0, or 6.4
Overview
Content Tools