The role of the repository administrator

The role of the repository administrator is to ensure repository consistency and prevent the loss of valuable data.

The repository administrator should be the only person to have the teamwork administration MDAC selected, since this MDAC provides special rights. When you have selected the teamwork administration MDAC, the associated teamwork MDAC considers you to be the repository administrator.

It is the repository administrator's responsibility to:

· create and configure the repository and define directory access rights

· define which MDACs must, can or cannot be selected in order to work on the repository. This is carried out when the repository is created, or by using the "Mandatory and allowed modules" command.

· define which versions of these mandatory MDACs must be used, in order to avoid the following problem: a developer updates an MDAC to a more recent version, which defines new note types and/or tagged value types. These new elements will not be imported when check-out operations are run on databases using the earlier version of the module. The following check-in operation deletes these notes from the repository.

· define which version of teamwork MDACs must be used. Some versions are not compatible (for example, the 4.2.d and 4.3 versions must not be used on the same repository). Teamwork MDACs in version 4.3 or later are now able to detect version conflicts between the repository and the project. Where a version conflict is detected, no teamwork commands can be run by regular users, but the repository administrator has the possibility of migrating the repository.