Version number

From Wiki

Jump to: navigation, search

The Version number of an Admin Item allows the history of changes made to an Admin Item to be recorded.

A Listpoint Version number is a string composed of between one and four numeric segments separated by a dot for example:


Each numeric segment must be no longer than 9 digits and overall the version number must be no longer than 20 characters including the dots. Leading zeroes are removed from each segment so 1.03 will be stored as 1.3

In lists of Admin Items the version numbers are usually sorted in reverse numerical order by segment e.g.

  • 1.11, 1.10. 1.9, 1.8, 1.7, 1.3
  • 1.9, 1.8, 1.7, 1.3, 1.11, 1.10 as would be the case if sorted alphabetically

There is no support for alphabetic characters in version numbers.

Generally a version number is appended to an Admin Item name following a space and a 'v' character e.g.

  • My Code List v2.3.4 or My Application Context v1.7

When a new draft of an Admin Item is created the version number is set by incrementing the least significant segment of the existing version number until one is found that has not already been used in combination with the Admin Item's Name. So:

  • DEF v17.3 would become DEF v17.4 unless there was already a DEF v17.4 in which case DEF v17.5 would be allocated.
  • GHI v1.2.3 would become GHI v1.2.4 etc

Although version numbers tend to be allocated in increasing numerical order they do not affect how an Admin Item's Lineage is structured. So, DEF v2 could be made to supersede DEF v7.3.

As version numbers are strings rather than numbers "1.0" is not the same as "1" or "1.0.0".

If an Item's history is incorrectly ordered this must be corrected by editing the relationships between Lineage members rather than by editing version numbers (which is impossible after Publication anyway).

Personal tools