In short, collections are the main organizational units in CELUM Content. You put assets into collections (i. e. link assets to collections) in order to structure them. Each collection can also have an icon and metadata of its own. Its metadata is determined by its collection type.
As already mentioned in The CELUM Content permission system, some collections determine the permissions for all assets within them, while others don't. These two kinds are:
Permission-defining collections define local permissions for themselves and also for all assets within.
Non-permission-defining collections only define local permissions for themselves.
For both kinds of collections, role-based local permissions can be set. For the former kind, the asset permissions defined in the role will be applied to the assets inside the collection. For the latter kind, only the collection role permissions will be applied to the collection itself.
The metadata validation describes the way in which the metadata of a collection or the assets within are validated. There are two validation levels for collections:
Strict: You can only link assets to a collection with this metadata validation if all required asset information fields are filled. So, the assets must have an asset type and no empty required fields. Equally, you can only save a strict collection if all required information fields for the collection are filled.
Tolerant: The asset's metadata status doesn't matter for collections with this metadata validation, you can even link assets without an asset type. Equally, you can save tolerant collections with empty required information fields as well.
By default, the validation level is inherited from the current collections's parent.
Get more information