CL Inconsistencies / Errors - CL_VSTATUS
|Assignee:||Bob Jolliffe||% Done:||
|Target version:||v.Next (Postponed)|
CL_VSTATUS: why not recommend its use along with _VERSION in metadata?
Updated by Gary Patchen almost 3 years ago
- Assignee changed from Bob Jolliffe to Gary Patchen
Clarify requirement re VSTATUS
Updated by Gary Patchen over 2 years ago
- Assignee changed from Gary Patchen to Bob Jolliffe
- Target version changed from v1.0 to v.Next (Postponed)
The description for CL_VSTATUS is "This is the status of this version of the measurement." So this implies a version related to the Indicator Data. I was assuming the values in CL_VSTATUS could also be used to manage the version states life cycle of an Indicator definition and infact any other concept that require a version state. I suggest we simply make the description something like : "This is a life cycle state for the version represented by _VERSION". This will allow us to use the version state anywhere and customize it should it need expanding.
Note that version can change as long as the state is less than "Final" 1 - 5, but once we pass "Final" 6 - 8, the version remains fixed.
Here is a copy of CL_VSTATUS for reference:
8 Marked for Deletion