Here, I will go over each of the settings in the Editing clients.
Samples pooling means that you can share samples for different products across different jobs and you can even narrow it down by sharing samples between clients. The idea is that you may create 2 different jobs at separate times but have the same products or different products with the same samples associated, then you can just use this feature to avoid checking the samples in the system again.
Delivery options (Asset delivery)
This is where your final assets will be delivered to a particular client. You can set this up by clicking on "Add". We currently support FTP, Google Cloud Storage, Amazon S3, Cloudinary, Box.com, and Bynder.
Then, fill in the information about the delivery option(s) you want to use. This includes Protocol - Host - User - Password.
After that, you can set up:
Folder pattern: Where the assets will be stored. By separating words or tokens with a slash ‘/’ you will create a subfolder.
Variant folder: Where the variants will be stored. You can choose between 3 options: The same folder as the main output - In a subfolder (you will then have to name the folder) - In a folder using the preset variant code
Non-select folder pattern: Where the non-selects will be stored. It is the same as creating a folder pattern above. You can choose words and tokens, then separate them with a slash ‘/’.
When file exist: You can choose to Keep both or Replace the existing file.
Once that is done, you can see in the list if the connection is working or not, allowing you to verify that Creative Force has the correct access to the method you have chosen.
We have a separate article regarding this. Please click here to read it.
This is an additional step that allows you to customize your metadata. And it then can be utilized within the metadata rules in presets. Here, you can create your own metadata schema’s name and add your own dedicated properties. Note that this is available in XMP only.
When you set the metadata rules for the presets, it will look something like the example below. The schema is ‘XMP Demo Metadata (Demo)’ and the properties are ‘Agency’, ‘Modelname’, ‘Model_size’... accordingly.
The combination of the expanded property system and custom metadata schemas will significantly increase your capability to automate metadata creation.
You can read more about metadata rules in the presets article above.