Versioning
As mentioned earlier, importing or creating a new object creates the version 1.0 for that object. This object becomes the root of the version tree that will be created by checking out and checking in this object and the versions derived from this object. Each version is a separate object with its own content and metadata. The versions are as shown:
The Content Server applies an implicit version label to each object in the repository and the label is of the form Major.minor. Additional symbolic version labels can be added to an object's metadata, which are descriptive and more appropriate for the end user.
If the checkin operation increments the minor version, the major portion is left unchanged. For example, the version label changes from 2.3 to 2.4 when the object is checked in as minor version. If the checkin operation increments the major version, the minor portion is reset to 0. For example, the version label changes from 2.3 to 3.0. In general, the version labels of...
