Delivery Directory Template Question

General
1

With our project folder structure set up like this:

/project
   /ep201
      /shots

When I use this path template:

{root[work]}/{project[name]}/{hierarchy}/delivery

…it creates the delivery folder inside the shots folder:

/project/ep201/shots/delivery

If I instead use:

{root[work]}/{project[name]}/delivery

…it creates the delivery folder directly under the project, but outside the episode folder:

/project/delivery

What I want is this:

I want the delivery folder to be created inside the same episode folder as the selected version, but outside the shots folder, like this:

/project/ep201/delivery

I tried using this path to go up one directory from shots:

{root[work]}/{project[name]}/{hierarchy}/../delivery

…but that didn’t work.

Question:
How can I define the path so that delivery becomes a sibling of shots and a child of the episode folder (e.g., ep201), based on the context of the selected version?

2

Try this one :
root[work]}/{project[name]}/<{folder[parents][0]}>/delivery

{folder[parents][0]} is the first folder under the project (you can experiment with 1, 2, 3, etc…)
The surrounding <> is the “Optional” syntax, that protects the universe from destruction in case its content cannot be evaluated (which can happen if an asset is placed directly under the project).

1 Like
3

Thanks @Yul
I knew there would be a way, but I did not see any example of {folder[parents]} in the documentation. This will be very helpful.

4

I have a question about version control for delivery files:

When we deliver files using a template (like for client review), is there any built-in versioning system for those deliveries?

For example:

If we have 100 shots, each might go through multiple internal versions (like v010, v011, etc.). But for delivery to the client, we might want to package and label them as a clean version, like v001.

Is there a way to control or manage this client-facing version separately from the internal version?

5

I do like the idea of this functionality.

There have been times when a deliverable version (Client Version) that differed from the in-house versions (Production Versions) would be helpful.

Some clients may appreciate that the first version they see is v01, not v04. Other clients may not mind.

However, the difficulty of tracking versions can become messy quite quickly.

Client v01 = Production v05
Client v02 = Production v07
…

If there were a simple and elegant way to manage these version references, I do like the idea.