Manage Model Versions

In some cases, one may wish to use the Repository to maintain a version history for each harvest or import 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, the UI only shows one version of a model. The technical user may use the MANAGE > Repository function to view a multi-version user interface (Tree) mode at any time. Also, a particular version may be designated to be the default version. It is the default version of a model which is used when the metadata manager UI is in single-version mode.

In addition, when including a model in a configuration, one is really including a specific version of that model in the configuration. This means that one may control which versions of which models are to be published at any point in time. E.g., one 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).

Otherwise, users are restricted to a single configuration at a time, and thus in those cases the UI only shows one version of a model.