In short, nodes are the main organizational units in CELUM Content. You assign assets to nodes in order to structure them. Each node can also have an icon and metadata of its own. Its metadata is determined by its node type.
As already mentioned in The CELUM Content permission system, some nodes determine the permissions for all assets within them, while others don't. These two kinds are:
Permission-defining nodes define local permissions for themselves and also for all assets within.
Non-permission-defining nodes only define local permissions for themselves.
For both kinds of nodes, 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 node. For the latter kind, only the node role permissions will be applied to the node itself.
The validation level describes the way in which the metadata of a node or the assets within are validated. There are two validation levels for nodes:
Strict: You can only assign assets to a node with this validation level 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 node if all required node information fields for the node are filled.
Tolerant : The asset's metadata status doesn't matter for nodes with this validation level, you can even add assets without an asset type. Equally, you can save tolerant nodes with empty required information fields as well.
By default, the validation level is inherited from the current node's parent node.
Get more information