Special cases for CELUM Content

Due to CELUM Content's permission system and metadata validation levels for collections, you may not always be able to synchronise new assets or new asset versions from your local file system to the server. This topic gives you an overview of possible restrictions due to these CELUM Content-specific features.

Impact of the collection validation level

CELUM Content collections can have one of several metadata validation levels, which impact whether you can synchronise new assets to a collection:

Tolerant: Assets within tolerant collections do not need to have an asset type and do not need to have all their required information fields filled. You can freely synchronise new assets from your local file system to such collections without worrying about metadata.
Strict: Assets within strict collections must have an asset type assigned and must have all required information fields filled.

If you try to synchronise a new asset to a strict collection from your local file system, the asset won't be synchronized. The activity stream will show a status message that the asset could not be created, and the asset will get an error icon overlay in the Windows^® Explorer or Finder®.

Impact of the permission system

Whether you can upload new assets or asset versions to CELUM Content depends on your CELUM Content user's permissions. These permissions can differ between collections. For example, you may be able to upload a new asset into one of your subscribed scope collections (and its child collections), but not to a different scope collection.

If you have the following permissions on your scopes in CELUM Content, you will be able to fully use CELUM Drive:

Add collections (to the collection on which the permission is granted)
Add assets (to the collection on which the permission is granted)
Delete collections (from the collection on which the permission is granted)
Delete assets (from the collection on which the permission is granted)
Move collections (inside the collection on which the permission is granted)
Move assets (inside the collection on which the permission is granted)
Add new version (to assets within the collection on which the permission is granted)

For each child collection, the permissions can either be inherited from its parent collection, or they can be set individually. Therefore, you may be able to perform actions inside a child collection even though you can't perform the same action in its parent collection.