...
This might look a little bit weird at the beginning, but this system gives you the full control for how to assemble your naming convention. You will see the benefit of it in a second.
Example: resolution
Our source images is an image of a flame with the resolution of width 1920 and the height 1080.
We create a path pattern to define the naming convention of the resolution folder as followed:
...
If we create a library transcoding template that creates a thumbnail preview for our elements, we can overwrite the path value <colorspace> by another value. For example: srgb
The path pattern for this transcoding template gets now resolved to: abc_1920x1080_srgb
...
Example: category
Lets create an path pattern for defining the naming convention for folder of the element.
Create a new path pattern:
element_name : <category.base.name>_<element.number>
...
| Info |
|---|
Why should we use the base category? We want our library to be sustainable and be as static as possible for many years. Thats That is why you should decided to store the elements in the base category folder |
Path valuesv alues
...
Path values are used to resolve the values of the path patterns depending on the element that will be ingested or rendered. Some values are known once we actually know the data that we want to ingest, others values can be set by you (custom values). The custom values can be overwritten in the library and the transcoding templates.
...