Skip to main content

Metadata Overview

How to configure metadata in assets, including: metadata rules, schemas, & custom namespaces.

Creative Force supports embedding metadata into delivered images, providing flexibility to include various properties such as production type, copyright information, or custom fields. This capability ensures that important information is retained within the image file itself, making it accessible for downstream workflows or external systems.


Feature Overview

In Creative Force, Metadata is set up at the Preset level. If a position on the Style Guide is associated with a particular Preset, all assets pushed through the system and mapped to that position will receive the same Metadata configuration.

Types of Schema

When creating a new Preset, you’ll need to decide if you would like to use a Standard Schema, or a Custom Schema. We will cover setup for both in the next sections.

Schema

Supported Types

Standard

  • Dublin Core

  • IPTC

  • XMP

  • EXIF

Custom

  • XMP

Custom Namespace

With a Custom Namespace, all data written to that namespace will group together under the defined name when viewing the metadata. Additionally, a Custom Namespace allows you to select from the custom Properties you have created within Creative Force.

To create a custom namespace, first, head to Studio Settings → Workspaces → Edit → Metadata Namespace

Fill in the fields with the name of the Schema, and then add the properties you would like to write Metadata for:

📝 The maximum number of characters in the Properties field is 4096. If the value you enter in the Properties field exceeds that, the data cant be saved.

When done assigning properties, click Save. The custom Schema you created, along with the properties you added, will now be available from the Schema and Properties fields, outlined in the next section.

Standard Schema

Creating standard schema required no additional setup or pre-configuration.

Build Metadata

After having decided on your schema type and completing any necessary pre-configuration, you’ll head back to the Presets Tab. Within the Preset, select Edit → Image Metadata: Next, click Image Metadata in the top right corner, then Add.

In the Metadata Rule screen, you will have the option to configure metadata line by line. The builder is split into three sections, with various configuration options.

Metadata Option

Function

Schema

Select any of the available types from the drop-down.

Property

Available properties will change depending on the Schema type selected. Choose any available property option from the drop-down.

Value

Assign a Creative Force property to be written in as the value in the metadata.

For example, when selecting the IPTC Schema, you could have the Product Code of the Product related to the asset written in as the ProductID.

If you are writing the creation date of an asset, the Property you would select is CreateDate, while the value would be the date value itself, 5/23/2023.

Metadata Tokens

The available token options in the value picker contain both system default properties and custom properties you have created for your studio. Of the Creative Force provided tokens, there are a few specific types and options worth calling out.

AI Provenance

Metadata Fields for AI Content are merge fields that capture AI processing details associated with an asset. Compatible with both XMP and IPTC metadata schemas.

Merge Field

Value

Connector

The software agent recorded on the AI action (for example, Bria, Photoroom, Gemini, Creative Force AI, Dreem)

Subfunction

The name of the subfunction that performed the action (for example, Image to Video, Background Removal)

AI System Used

The AI model name only, with the version removed — for a recorded model of Kling 3.5, the value is Kling

AI System Version Used

The AI model version only, with the name removed — for a recorded model of Kling 3.5, the value is 3.5.

Empty when the recorded model carries no version (for example, Bria, Photoroom, Cutout Pro, Cloudinary)

AI Prompt Information

The prompt configured for the subfunction

Digital Source Type

A readable label derived from the recorded action

💭 For more information on Metadata for AI Content, please see our dedicated article on the subject by following the link here.

Shop the Look

Metadata Fields for Outfit & User Properties help to support Shop the Look when you need to pass along information for your Ecom PDPs.

Merge Field

Value

Outfit ID

If an Outfit is associated with the Product being shot, you can retain the ID within the metadata for reference.

Primary Product Code

Inserts the product code for the main 'hero' component of the Outfit.

Secondary Product Code [N]

[1] holds the first secondary product's code, [2] the second, and so on.

Sample Code of Secondary Product [N]

[1] holds the first secondary product's sample code, [2] the second, and so on. It always chooses the selected Sample on set.

All Product Codes

Holds an array or string of all the product codes used as components in the Outfit.

Model Properties

Use Tokens like [Model Name], [Model Size], etc to map information about the model directly to metadata.

💭 For more information on building and working with Outfits, please see our dedicated article on the subject by following the link here.

Modifiers

Next to relevant added metadata fields, a number of modifiers will be available and can be freely toggled on and off depending on the desired functionality.

Modifier Types

In the table below, review the available metadata field modifiers, their purpose, and where to learn more.

Modifier

Function

Conditional Rules

Metadata will only be written when the criteria match the configured rule.

Only Write with Value

Metadata will only be written when the related property has a value. If empty, nothing is written.

Array Data Type

When enabled, the system will automatically split comma-separated values into distinct array items.


This setting is only available for metadata fields that inherently support arrays.

Remove Field

Removes the field, its related metadata properties and values, from the configuration.

Variant Specific

Create separate pages of metadata fields to allow individual metadata for each variant or spec.

Conditional Rules

There may be circumstances where you only want certain values written to the metadata if the product meets certain criteria.

Clicking the cubes icon to the right of the metadata rule will allow you to set conditional rules that allow you to customize when and how a value is written.

Metadata conditional rules can be created based on Production, Property, and Source-level rules.

Rule Type

Description

Production Rule

The value can be set to trigger, either:

  • When producing an Outfit

  • When not producing an Outfit

Source Rule

The value can be set to trigger, either:

  • If the source is Photo Production

  • If the source is Vendor Provided

Property Rule

Select from various object-level properties and set logical operators to define the rule.

Variant Specific

In the lower-left corner of the Metadata Rules screen, there is a toggle for “Variant Specific”. Toggling the switch on adds a dropdown so you can select and write specific Metadata Rules for each variant you’ve created for the Preset separately.

Location Metaproperties

If you are using Bynder, Amplience, or Akeneo as your Asset delivery location, you will be able to define the mapping rules between metaproperties and Creative Force merge field values at both the Preset and variant-specific levels.

This is particularly helpful if different asset variants have different metadata relevant to where the asset is sent or how it will be utilized in the DAM.

Next Steps

After the metadata has been configured to your Preset, there are a number of actions that can be taken to verify and interact with it.

Metadata Toolbox

In the upper right corner, you’ll notice a small toolbox icon. The Metadata Toolbox gives you two options to assist you as you set up your rules:

Toolbox Option

Function

Download Example

Download an example of your configured metadata to verify it is configured properly.

The download will contain an example for each variant in your Preset.

Detect from File

This tool lets you upload an image file containing Metadata the way you want it– and easily translate that into Metadata Rules in Creative Force.

Extracting Metadata

If you are looking to double-check the Metadata of an asset downloaded from Creative Force, we recommend using a tool called Exiftool. This free tool can be downloaded here.

Once installed, open a terminal on your machine, type in exiftool, then add a space and drag and drop your image. Click 'Enter,' and the Metadata will populate on the screen.

Corrupted Metadata

In some instances, you may occasionally encounter corrupted metadata as files move through production. This can cause issues where Creative Force cannot write the required metadata on the files and cannot push them forward to post-production.

In order to prevent potential bottlenecks during production caused by corrupted metadata, a configuration in the Studio Settings can be enabled.
​
Head to Studio Settings → External Post Settings → Then, enable the option for “Reset metadata before External Post in case of corrupted metadata."

With this setting enabled, the system will utilize Exiftool to check the metadata of all files imported to our server. By selecting this option, you will allow Creative Force to:

  • Check the metadata of all the files on all clients in your account

  • Clear the corrupt metadata fields if Exiftool alerts that there is corrupted data.

  • Rewrite all of the metadata, including PhysicalFileID and other metadata, according to your setup.

Metadata FAQ

Updating Metadata for Product Requests with 'Done' Status

If you’ve already begun or completed production for a set of images and realize you need to update or change a Metadata Rule, simply head to Presets > Metadata Rules and make the update.
​
Once complete, you can simply reset the Production to Asset Delivery, and the system will redeliver the assets with the changes applied as long as the value for the rules you created or changed is available in Creative Force.

When Does Creative Force Write Metadata?

The system will write Metadata in two steps during the production process. The first is during delivery to the External Post step, where all Metadata values applicable so far are written.
​
Creative Force then again writes additional available Metadata at Asset Delivery; at this point, all Metadata will be available and written to the assets.

Did this answer your question?