06-15-2020, 01:36 PM
(This post was last modified: 06-15-2020, 03:40 PM by remkonoteboom.)
Although my definition is flexible, the general rule is that "type" is a strict field limited to a small number of options which can be presented in a search filter as a drop down and represents the property of an sType. Category has been used to be more of an organizing field and is usually more freeform.
An example:
Type: vehicle, prop, character
Categories: Industrial, Military, Scientific, etc
Note that any of the types can fit in any of the categories.
Sometimes, in certain large libraries, we have used sub-categories separate by "/"
ie: Industrial/Vehicle
However, much of that has been replace by collections which has this built-in, so we don't really use category all that much anymore. However, I don't think collections have ever been set up in the VFX data model.
An example:
Type: vehicle, prop, character
Categories: Industrial, Military, Scientific, etc
Note that any of the types can fit in any of the categories.
Sometimes, in certain large libraries, we have used sub-categories separate by "/"
ie: Industrial/Vehicle
However, much of that has been replace by collections which has this built-in, so we don't really use category all that much anymore. However, I don't think collections have ever been set up in the VFX data model.