Version Control (Check Out/In)

Cumulus Core-enabled applications can offer asset check-in/out and version control. Catalog administrators determine the number of versions that are stored by the system, and older versions can be made "current" at any time.

Cumulus offers a version control feature that enables you check files out for editing, keep older versions of files, and enter notes about changes made to each revision. Here, the version history of a file is shown, indicating it has been udated twice since it was originally cataloged. Older versions can be made current at any time, and you can choose how many older versions you want Cumulus to maintain. File check out/in and version histories are also available using the Web Access Clients.

A system feature called "Vault" is used to manage the storage of version controlled assets. The Vault stores assets using a naming convention meaningful only to the Cumulus Core application, which offers an added layer of security. (In the unlikely event of a Cumulus Core system failure, the assets can be manually renamed and moved to standard file system storage.)

The Vault provides an additional layer of asset security and also enables you to maintain older versions of your assets, thanks to its check-in/out feature.

Check-in/out ensures that only one user a time can edit the cataloged asset. Others can continue to access checked out assets (permissions permitting), but they will have no way of overwriting the cataloged master. The user who checks out an asset can modify the asset, and check it back in again at any time, thereby adding a new version to the Vault.

When checking a file back in, users can enter comments that alert others to what was changed in the file.

Cumulus Core check-in/out and version control features are available to both operating system-native and Web-based applications.