In addition to the standard tables having a direct relationship with Shots (Products, Groupings, Samples, Talent), ShotFlow offers the metadata tagging of optional tables that have an indirect relationship to Shots.


Relationships supported in XMP: 

Shot -> Grouping -> Job/Channel

Shot -> Grouping -> Request

Shot -> Grouping -> Job/Channel -> Campaign/Project

Shot -> Product Child -> Job/Channel

Shot -> Product Child -> Request

Shot -> Product Child -> Job/Channel -> Campaign/Project

Shot -> Request

Shot -> Job Channel

Talent ->Booking


Booking

To include Bookings in the XMP, users will need to create a Talent XMP View and embed a Booking view within.


If a Booking View is nested in the Talent XMP View, pull in those fields and include them in XMP metadata as additional fields in the Talent panel


The Booking records that should be included in the XMP are any Bookings related to the Talent in the XMP. In other words, include the Bookings for the Talent that are currently active on the Shot List.