AY-6666_Shotgrid: sequence and shot folder grouping

[ynbot]

Please describe the enhancement you have in mind and explain what the current shortcomings are?

For the Assets, the Flow->Ayon sync creates them into folders based on the Asset type ("sg_asset_type").
Which is a good thing and leads to a hierarchy in ayon like that:
<project_name>/<asset_type>/<asset_name>

But for the sequences (and I guess it will be the same for the shots at some point), Ayon creates them directly into the root, which leads to:
<project_name>/<sequence_name>

And we want:
<project_name>/sequence/<sequence_name>
And for the shots we'll want:
<project_name>/shot/<shot_name>

Is there a way to do that by setting things into Ayon ?

IMOO, the default behaviour in the code should be:
Take the entity's Type in Flow (Asset, Sequence, Shot...) and use it as main folder
For the Assets, use the sg_asset_type value with/instead (leading to <project_name>/asset/<asset_type>/<asset_name>, or <project_name>/<asset_type>/<asset_name> like it does now).

How would you imagine the implementation of the enhancemenet?

No response

Describe alternatives you've considered:

No response

Additional context:

link to discussion on Discord
(might be a private channel)

This issue was automatically created from Clickup ticket AY-6666

[BigRoy]

Also came up on Community Discord here - where it was mentioned that this may already be possible with a slight configuration tweak on Shotgrid side itself.

[fabiaserra]

Sorry I misread this issue yesterday on my phone thinking that this referred to a common config issue where your Shotgrid projects Tracking settings don't have the right parent/child relationships set up and thus the entities appear flat on the hierarchy:

Reading this now in the morning instead (with a coffee in my hands) I'm realizing this issue is indeed related to what @BigRoy linked in Discord at https://discord.com/channels/517362899170230292/1280666097976213545

However, this is requesting an even more granular control on the hierarchy and I'm not sure I understand the use case you are suggesting.

On the example given you are saying that you would want each entity type on a separate parent folder on disk, regardless if those entities are children of others? I believe the parent/child hierarchy wouldn't be that easy to break, although if you don't care about the parent/child hierarchy in ShotGrid either... you could probably change the Tracking settings so shots aren't childs of sequences, although that kind of beats the purpose of using a hierarchy?

In our AYON setup, what I have done is create an anatomy field called {assets_or_shots} that basically holds the value of "shots" or "assets" string depending on whether it's an asset entity or shot based (episode, sequence, shot...). Our Publish template then looks like this so all of our shots and all of our assets live on individual parent folders:

Directory template:

• {root[work]}/{project[code]}/{assets_or_shots}{folder[path]}/publish/{product[type]}/{product[name]}/{@version}</{representation}>
  File name template:
• {project[code]}<_{episode}><_{seq}><_{shotnum}>_{product[name]}_{@version}<_{output}><.{@frame}><_{udim}>.{ext}

Having said this... you could use a template like this one and I think it would do what you are after:

{root[work]}/{project[name]}/{folder[type]}/publish

This way each folder should be independent of their hierarchy