Hi there,
We are looking for the best way to include custom data in Ayon for workflow purposes, and we were wondering how you would suggest to implement this.
Here is a use case of one of the things we want to achieve.
When we make an animation product, we want to track from what folder (or Asset in our case to be specific) this product comes from, to group them later by products coming from the same asset when importing them. By default Ayon does not give us this information, as the folder of the animation product we create is now the Shot, and has no data from the original asset anymore.
So what we came up with was to add a json representation to the animation product, that contains all the info we need. This works fine, but this means we have to load this json manually when we need it because it’s a different representation, so it does not feel very well integrated into the ‘Ayon workflow’.
We saw the recent addition of the Traits in representations, would that be a correct use case to modify directly the representation without doing a different one? Or maybe there is an even better way to handle this?
Thanks in advance for your help