Page Comparison

...

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

...

Another example for the element folder name

...

Lets create an path pattern for defining the naming convention for folder of the element.

Create a new path pattern:
element_name <category: <category.base.name>name>_<element.number>

In the ingest view we decide that the category of the element is ‚flame‘. flame
The base (top parent) category of flame is fire. Because a flame is a type of fire.

This means that
category.name -> flame (which be do not use here)
and
category.base.name -> fire <category.name> resolves to flame and <category.base.name> resolves to fire

Info
Why should we use the base category? We want our library to be sustainable and be as static as possible for many years. Once we ingest an element it should not move or be renamed. If we want to open up a project file from years ago all the media files should be found. Thats why you should decided to store the elements in the base category folder

Overwrite path pattern

In the settings section: library → transcoding templates
you can overwrite the path patterns and path values.

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

	overwrite pattern

values

Path values are used to resolve the values of the path patterns.

...