In some cases, you may wish to use the repository to maintain a version history for each harvest or upload of a model. These versions are individual objects within the repository and represent the object’s contents at a specific point in time.
The administrator may manage any number of versions. By default, however, Metadata Manager only shows one version of a model. The technical user may change to a multi-version user interface mode at any time. In addition, a particular version may be designated to be the default version. It is the default version of a model which is used when Metadata Manager is in single-version mode.
When including a model in a configuration, one is actually including a specific version of that model in the configuration. This means that you may control which versions of which models are to be published at any point in time. For example, you may place the approved version of a model in a published configuration while data modelers continue to edit and upload newer version as work in progress (unpublished).