The Source Integrity Professional Edition User Guide - MKS

Metadata
About Labels
Metadata
The most important conversion step is the establishment of a
development path for the variant sandbox. This development path
will begin at a new checkpoint in the master project.
Note If a master project has other subprojects as members, then a
sandbox based on it will have subsandboxes, individual sandbox files
matching the same structure. cnvrnt72 converts the specified sandbox,
and recursively converts all subsandboxes as well.
Running cnvrnt72 on a subsandbox file will convert it and all of those
below it, but cnvrnt72 cannot convert any sandbox files above it in the
hierarchy. This will cause problems when using the sandbox, and when
later trying to finish the conversion. You should run cnvrnt72 on the
uppermost sandbox, that is, on the one that is not a subsandbox.
Source Integrity maintains a variety of information about your
development objects. This metadata can be used to monitor and
manage projects, identify and retrieve revisions, update working
files, and prepare activity reports on your development efforts.
An important part of any configuration management system is the
regular input of significant metadata, such as
archive descriptions when archives are created
revision descriptions and labels when objects are checked in, and
at project milestones
automatic records, such as timestamps and transaction logs
This section describes some of the ways you can take advantage of
the metadata Source Integrity maintains.
When you check in a file, Source Integrity lets you assign a revision
label to it. Labels serve as identifiers for revisions in an archive, and
make it easier to locate significant revisions of your objects. Many
Source Integrity functions use labels to specify the revision a
command will operate on. For instance, you can check out a revision
by specifying its label.
User Guide 29