Many brands have moved beyond just tracking a single “hero” product in a Shot, to working with product Groupings. These may also be referred to as Looks, Families, or other terms to indicate more than one product featured in a Shot. By associating more than one product with a shot, the shot metadata can reflect all of the products featured, and empower experiences such as “Shopping the Look” in downstream platforms.
Many groupings can also be related to many shots, enabling metadata tagging of multiple groupings so that a DAM and other downstream systems can ingest the data for multiple featured Groupings.
Real World Scenario:
Two models are wearing two outfits and are pictured together for an editorial shoot. The capture of both models is a grouping that is represented by one or more shots (Shot A), and each of the model's outfits are also individual groupings represented by one or more shots (Shot B and Shot C).
To address this challenge, Capture has a pane within the Product Interaction Section of the Detail panel for interacting with the Products related to a Shot, called “Related Products.”
Interaction with the Related Products pane is enabled at the Shot List level through an option called “Products - Mode - Manage from Set.” The choices for this field are:
Disabled - no interaction is permitted with the related Product Child or Grouping(s).
New Grouping Record - the on-Set team can add (+) , remove (-) and/or re-order (via drag and drop of the Product Child identifiers) products in any related Grouping. Any changes to a Grouping creates a new Grouping record that is linked to the Shot, without modifying the original Grouping record that was previously related to the Shot. This new Grouping record does not contain any of the attributes of the original Grouping (e.g. any field attributes such as Description or ID that were true of the original Grouping record)
Update Grouping Record - the on-Set team can add (+) , remove (-) and/or re-order (via drag and drop of Product Child identifiers) products in any related Grouping. All changes to the Grouping are reflected in that original Grouping record (the on-Set team is updating the Grouping).
Clone Grouping Record- - the on-Set team can add (+) , remove (-) and/or re-order (via drag and drop of the Product Child identifiers) products in any related Grouping. Any changes to a Grouping create a new Grouping record that is linked to the Shot, without modifying the original Grouping record that was previously related to the Shot. This new Grouping record is a clone of the original Grouping (e.g. it will copy all the field attributes such as Description or ID that were true of the original Grouping record)
Removing a Product relationship consists of highlighting the Product ID in the pane, selecting the Remove Product icon, and confirming you wish to remove the relationship between the Product and this Shot.
Adding Products consists of selecting the Add Product icon, and typing or scanning unique Product or Sample identifiers such as the barcode, label or SKU, or by navigating to the Samples or Product table in the Cloud.
Multiple Products can be added by separating each value with a comma and submitting the products for addition. The current recommended limit is submitting no more than 10 products at one time. The order of the products as they were listed in the Add Product dialog will be the default order in the Related Products pane.
You can also easily reorder products by selecting and dragging a product to a different position in the list. This order will be reflected in the XMP metadata for this shot, enabling the capture team to pass the correct order of products in the asset to ensure accurate product ordering in any downstream systems such as the web CMS that are utilizing product data for merchandising on site.
To learn more about how to view Style Guides related to Groupings, Products or Shots, click the link below:
Style Guides in Product Centric View
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article