PRECONDITIONS: You need to be logged in as the Cumulus Administrator to configure File System Versioning.
File system based versioning of assets can be configured via the Server Console.
Configuration
The following settings can be configured:
• Create new version when record is updated (and asset was modified): This takes effect both with manual and automatic updates of the record. If this option is not activated, new versions must be explicitly created via the Asset > Check In menu command.
• Reduce creation of new versions. Minimal time gap between versions: If activated, at least the specified number of minutes must go by before a new version is created, even if the asset has been changed in the meantime. – Depending on the system load, the length of the task queue, etc, the effective gap may exceed the specified value. This is useful to avoid clutter whenever an application creates frequent updates of a file.
NOTE: This setting only affects the creation of versions via an update record process. It does not affect the creation of new versions via checking in assets!
• Restrict numbers of versions to be kept to: If activated, only the specified number of versions are kept.
• Always keep oldest version: If activated, the oldest version – the “original” file – is never deleted.
Versioning Locations
Basically, any central asset location defined in any catalog can be configured for versioning. As a prerequisite, the location – that is, the server and/or the path – must be available on the machine on which the Server Console runs or – if the Web Server Console is used – on the machine on which the Cumulus Web Solutions are running.
To configure a central asset location for asset versioning:
1. Click Add Location.
A window appears displaying any central asset location defined in any catalog that is not yet configured for versioning, and that is currently accessible.
2. Select the desired location, then click OK.
A window appears asking whether all not yet versionable assets in the selected location shall be made versionable: Yes: Existing assets in the central asset location are made versionable. No: Existing assets are not made versionable; but new assets are always created as versionable. – You may transform not versionable assets to versionable ones anytime later via the Prepare Assets in Location button
3. Select the desired option. The location and the catalog to which the respective assets are cataloged are is displayed in the Versioning Locations list.
You may stop asset versioning for a location anytime via the Remove Location button. If you do so, you may also disable versioning for currently versioned assets (i.e. make them unversionable) and remove all existing versions.
SPECIAL TECH INFO: Autoversioning on Update
File system versioning checks the file modification date and the file size to decide whether it has to create a new version on update or check-in. Starting with Cumulus 9.2.4, the contents is no longer checked to increase the performance, especially on slow network shares. If you use a tool that does not change the file modification date and the file size and you need to employ the content check, contact Canto.