Some use cases may include the desire for the sample(s) that are being scanned into capture to be the “designated” sample for use in tagging metadata for a shot. This means that the sample(s) used for a shot would place the relevant one at the top of the metadata “list” so that downstream systems can reliably extract attributes of that particular sample for metadata.
REAL-WORLD SCENARIO
Client A has multiple samples tied to a shot, but only one is being used for the actual capture session. They want sample attributes such as Size to be extracted from metadata in post, but only for the sample actually used in the shot. Right now, samples are ordered randomly in metadata.
If a sample ID is used in Shot Retrieval, that sample becomes first in the sort to the shot(s) retrieved, assuming the sort is enabled in platform for that relationship. The samples are then displayed in the scanned order in capture as well as the metadata (the sidecar file and the XMP panels).
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