Terminology

Work

Per asset, per task.

Synonyms: development.

shots/
  1000/
    work/
      animation/

assets/
  HeroCharacter/
    work/
      rigging/

Publish

Shared or otherwise finalised content.

Synonyms: public, shared, final. E.g. shot1/publish/Character01, HeroCharacter/publish/model

shots/
  1000/
    publish/
      Character01/
        v001
        v002

assets/
  HeroCharacter/
    publish/
      animRig/
        v001
        v002

Project

The project is the highest level overview. A project is also depicted as the "root" since it will hold all it encompasses, any content whatsoever. Such content is described below.

Types of Items

Each Type of Item has a predefined levels of hierarchy for its contained Items. By default we differentiate between two different item types: "Shots" and "Assets". For example Assets have one level whereas Shots have two:

assets/ben
assets/table
assets/chair

film/seq01/1000
film/seq01/2000
film/seq01/3000

It's the leaf item that is considered to be the Item. eg. asset ben or shot 1000.

A project can have any amount of Item types defined. By default we use the two described above.

Asset

Anything that can be worked within is considered and item, so in practice you say "I'm working on item X". It's the leaf element in the hierarchy.

For example it's name of the asset or shot, like our asset ben or the shot 1000.

Family

The type of output data coming from the artist working in the task. These can range from model, rig, lookdev to pointcache or even review. This is the Family used to define the content within the Pyblish plug-ins. A single Task can have any type of Family as output.

Subset

The subset is the output data the artist is generating. In most scenarios there would be a "default" expected output so we recommend calling it just "default". Other subsets then could be: "hires" or "proxy" for.

Version

This would the be automatically incrementing version number of the output data. Each family/instance combination would have its own versioning since it is its own version of the output data that it represents. It's the output components that are versioned.