You can decide whether assets of a particular asset type can participate in relationships with other assets. When an asset has related assets, those assets will be displayed in groups at the bottom of the view asset page. Relationships can be configured using the following settings on the Admin > Asset Types > Relationships page.

Selecting this option means that assets of this type can participate in non-hierarchical relationships with other assets. When this box is checked you will be presented with a list of asset types that this type can have peer relationships with. 

For each type you select as a valid a peer relationship you can optionally specify a 'default relationship' category. See below for a description of default relationships and how they work.

Once you have selected the valid peer types you need to provide a term that describes the peers (singular and plural). These terms are used when displaying or referring to peer assets throughout the application for the type in question.

This option should be selected when the asset type will have child assets. Once selected you will be presented with a list of types to select valid child types from. As with peer relationships, default relationship categories can be specified for each relationship and child/children terms need to be provided.

Selecting this option will mean that assets of this type cannot be added through a standard single or bulk upload, but can only be added when selecting the option to 'Add a child asset' from an asset of a type that can have this type as a child. 

If this asset type is going to be the child of another asset type then you can option specify terms for the system to use to describe it's parent/s. If no terms are provided the system will default to 'parent' and 'parents' as the descriptors.

 

 

If you click the show advanced options link on the relationships page you will be given the following further options when setting up asset type relationships: 

 

When setting up relationships for asset type X and you select a default relationship category id for a relationship to another type (type Y) then when an instance of type X is created by a user the system will try to create relationships to all instances of type Y in the specified category. The user creating the new asset will be redirected to a page that enables them to optionally exclude assets from the relationships prior to default relationships being created.

 

When setting up relationships you can optionally provide a relationship description label for each type of relationship between two types. If this relationship label is provided then when a user adds a related asset to an instance of this type they will be prompted to enter extra information about the relationship into a text field prefixed with the label provided. So for instance, if you have a child relationship with type X as the parent and type Y as the child and you specify a relationship description label of 'extra information', then when a user adds a child of type Y to an instance of type X they will be prompted to enter 'extra information' into a text field. The relationship description that the user provides will be displayed above the display attributes for each related asset on a view asset page. The user will be able to edit individual relationship descriptions from the view asset page as well (via a link on the related assets). Please note, this functionality is only available if your Asset Bank isn't multi-lingual (defined by the supportMultiLanguage setting in ApplicationSettings.properties).