Asset Relation Types
Assets can be related to one another by relation types. This can describe a basic relationship such as parent child, duplicate or sibling or alternatively describe use-cases such as Component Of, Product Of, Promo for.
Relation Types can be directional - such as parent child, or bidirectional such as sibling.
In addition to this custom relationship types can be created to describe the relationships between your assets, if the standard ones do not cover the semantics of the relationships between your assets.
It is possible to create your own relationship types, though we suggest first looking to see whether the standard relationship types cover your use-case otherwise you might end up with a lot of extremely similar relationship types that only the author of the relation type understood the use-case for.
Standard relationship types are non-editable, non-deletable types in iconik. They intend to cover the majority of broad uses-cases.
This is a directional relationship between assets where one must be the parent, and one the child. An asset should not be both a child and a parent of the same asset at the same time (we suggest sibling for this use case).
An example is a master video (being the parent), and a short edit (being the child).
This is a bidirectional relationship between assets.
Example use cases are to describe the relationship between different Edits of a video.
This is a directional relationship that describes the creation of a promo.
An example of this is a trailer for a movie. The Trailer is the "promo for" the movie. The movie has a "promo of" the trailer.
This is a directional relationship that describes the use of one asset being used to create another asset.
An example of this is a movie that is a product of a video editing NLE's project file. The project file is the source for the movie.
This is a directional relationship that descibes that an asset is used within another asset.
Typical example of this is a video, image or audio asset that is used in an video editing NLE project as part of the edit process. The media asset is Used In the Project, the Project Uses the media asset.
This is a directional relationship that describes that an asset is used as a source to create another asset.
An example of this is a media file that is used in a video editing project. The video editing project is used to create a new asset, with a component of the media file.
Please note we don't usually use this to describe format/file component - such as a separate audio files of a video
This is a bidirectional to describe that one asset is a duplicate of another asset.
Typically this is used when the "content" of the asset is exactly the same as another asset. iconik will typically try and resolve exactly identical files as the same asset, so this is for use-cases where the asset might be different to iconik's eyes - but semantically the same thing in your intended uses case.
A collection can have any number of assets or other collections within it, and that in itself is a type of relation. The Assets and Sub-collections are members of the collection. Assets can be members of any number of collections. The membership is directional, in that a collection can not be a member of a parent collection and sub-collection at the same time.