Configuring ShotFlow to Pass Metadata to Downstream Systems

ShotFlow can be configured to pass values from various fields into the metadata that populates downstream systems such as Digital Asset Management (DAM) systems. If there is an existing standard set in the DAM, ShotFlow will ensure compatibility by matching the expected fields. For example, if the DAM expects values from a field named "Angle," ShotFlow will ensure the "Angle" field is properly mapped.

Excluded Fields

Certain fields are internal to ShotFlow and should not be included in the metadata passed to downstream systems:

• Title: This is an internal field used by the Photo Studio to identify the shot during capture.
• Naming Convention: This internal field passes the naming structure to Capture One Pro.
• UUID Fields: These are typically used as internal identifiers for records. Some UUID fields may be needed for asset automation, such as Capture UUID, but generally, they are not included in the metadata passed to downstream systems.

Included Fields

The following fields should be included in the metadata passed to downstream systems:

• FileName: The actual name of the Shot at the point of capture. This field is included automatically and cannot be excluded.
• ShotName: The title of the Shot. This field is included automatically and cannot be excluded.
• Product Identifiers: Fields such as SKU/UPC, Description, Category/Dept, etc.
• Shot Details: Fields such as Angle, Type, etc.

By ensuring the correct fields are included and excluded, ShotFlow maintains compatibility with downstream systems, ensuring seamless integration and accurate metadata transfer.