Skip to content
Gallery
Soko documentation
Share
Explore
Project templates

Path naming convention

When using keys in directory or file name templates, you need to enclose the key in curly braces. For example, user becomes {user}.
Table 1
Soko key
Ayon key
Description
1
root[name]
root[name]
Path to root folder
2
studio[name]
studio[name]
Studio's full name
3
studio[code]
studio[code]
Studio's code
4
project[name]
project[name]
Project's full name
5
project[code]
project[code]
Project's code
6
parent[name]
folder[name]
Name of asset or shot
7
parent[type]
folder[type]
Folder type
8
parent[path]
folder[path]
Full folder path of asset or shot within a project
9
hierarchy
hierarchy
The folder path excluding the last folder name (you can use indexes in hierary e.g. hierarchy[0], hierarchy[1], hierarchy[-1] (like in python)
10
grandParent
parent
Name of hierarchical parent of the folder
11
task[name]
task[name]
Name of task
12
task[type]
task[type]
Type of task
13
task[short]
task[short]
Short name of task type (eg. Modelingmdl)
14
version
version
Version number
15
output[name]
product[name]
Product name
16
output[type]
product[type]
Product type
17
ext
ext
File extension
18
representation
Representation name
19
frame
frame
Frame number for sequence files.
20
app
app
Application Name
21
user
user
Username (can be overridden in settings-User Management
22
output
Extract review output profile name
23
comment
comment
Subversion string from workfiles tool (only relevant for workfiles template right now.)
24
colorspace
colorspace
Colorspace profile name
25
originalDirname
originalDirname
Original directory of published file
26
originalBasename
originalBasename
Original file name without extension
27
suffix
variant
28
There are no rows in this table


Publishing folder DD



Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.