Blender homepage link
header graphic
 

Asset Management

When dealing with multiple users working on large data sets with many nodes, it can be good to manage these assets by tagging the nodes with various meta data. Here is a set of recommended tags. It is recommended that tools set as many of thees tags as possible automatically.

All the following tags should be in a tag group named "asset".

"sections"
Used for grouping content in to multiple layers. What is commonly referred to as "layers" in 3D applications. For instance characters, landscape, and trees. This is used to allow users to hide parts of the data set that is not of interest.

"tool"
Text tag indicating the main tool used for the creation and modification of the node.

"author"
Text tag indicating the artist responsible for the creation of the node.

"assigned"
Text tag with the name of the person assigned to work on the data.

"approved"
This text tag is set on any data that is final and approved, and the text string indicate who approved the data.

"version"
Version number of the data indicated as a string tag. The format should be: an integer number, optionally followed by more integer numbers, separated by single periods. There might be an optional alpha-numeric suffix string.

This means the following are all valid version strings: "2", "2.1", "0.0.1", "12alpha", "2.42a", "2.6.16mm".

"status"
Free text that describes the status of the node for instance: "model complete, missing UV".

"placeholder"
A tag set on quick mockup data used before the final data is constructed.

"library"
Library is used for grouping assets, not parts of scenes (like sections) For instance a library called "wood" can contain all wood material and textures.

"source"
A text or link tag that contains the file path, or link to text node containing the source data that was used for generating the data. Can be application specific files from a editing application.

"generated"
A tag set on all data that is generated by a specific tool and not by human hand, this can be a object that has a dependency associated with it that keeps it dependent on other data.

"alternative"
Same as "Source" but rather pointing to data that can be used as a a alternative representation of the node. It is recommended not to use this tag unless absolutely necessary since the data may easily become out of sync with the verse data. It is also worth remembering that no other tools will be able to parse this alternative representation. If used it is recommended to have a service that updates the alternative representation always to be in sync with the verse representation.

"file"
Once a asset has been exported to a file this tag indicates the path to that file. a node may have multiple file tags if the node is exported in to multiple versions.

"comment"
Free-form text commenting on the data.