Your pipeline flowchart has entities that have properties, including fields for storing data values. These fields need to be configured to match fields in your Digital Asset Manager (DAM). This is how the DAM data is synchronized with the entities in SimpleCloud.
However, SimpleCloud is not a DAM, and so only needs those data fields that are essential to the success of your workflow. For example, if you have an animation discipline with a camera shot that needs the time start and end range, the "cut in" and "cut out" data properties are essential. The shot cannot be completed without that information. And so you have to map that data from your DAM to SimpleCloud by creating those fields for the "shot" entity.
Your DAM is likely to contain many more fields, and not all of those are necessary in SimpleCloud. So when you are adding properties to your entities in SimpleCloud, it is important that you understand the details of your work flow and what components are needed for each task. With this information, you can then judge which data fields need to be included for each entity, and which ones are not useful in SimpleCloud.
To set the entity data fields:
- What is always mandatory to synchronize is the entity identifier. In some DAMs it is a name and in others it is a number. In case it is a name, when synchronized, simplecloud converts it into a unique and human readable code. It transforms uppercase to lowercase, removes symbols and converts spaces to underscores. For example "My new Chäracter 45" would be "my_new_character_45". This is done to avoid errors in 3d software like Maya, which only accept ascii alphanumeric names without spaces.
As an addition, I personally always prefer non-numeric identifiers for entities, since it is much easier to identify those entities in a directory structure of publications, work or metadata packages.
It is also advisable to synchronize the numeric id of the DAM, in order to make the relationship between the entities in Simplecloud and the DAM.