ShotFlow can now embed metadata for assets that originate outside of a ShotFlow Capture workflow - think Orbitvu, Looklet, Profoto (StyleShoots), vendor supplied assets, and more!
Smarter Asset Automation, ShotFlow’s Post-Production module, can now populate a brand's XMP metadata schema once an Asset is matched to a Shot based on configurable logic tied to a strict file naming convention.
The population of this XMP can be incorporated into your Smarter Approval Post-Production workflow to automate the processing and reviewing more of your assets.
Use Cases:
Editorial Assets: As long as ShotFlow has the shot record to be fulfilled, we can identify the Asset based on a matching expected file name and process the file - even if it wasn't created with ShotFlow Capture and Capture One.
(This is often a use case for assets from location or other non-PDP editorial marketing shoots.)
Vendor Supplied Images: As a starting point for extending ShotFlow for managing vendor images, asset files with expected names can be identified and processed in post-production.
If Vendors submit the images with the correct file names, ShotFlow can pick them up and incorporate into your post production review and approval workflows enabled through Smarter Approval.
Orbitvu, Profoto E-Commerce (formerly StyleShoots), Looklet: Assets coming from other capture systems with expected file names (or even other pre-defined fields!) in ShotFlow can be identified programmatically and can then embed the metadata through post-production processing.
Requirements:
- Smarter Assets license for enabling the configuration of your Post-Production Asset Automation.
- Images to be consumed from external sources with defined file name matching logic.
- Optional: Smarter Approval license for review and approval of assets before final delivery to DAM or other system.
If you’re interested in trying this out, reach out to your TAM to see how it can fit into your Smarter Post Production workflow.
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