Relational metadata can be added in the collection hierarchy to define the relation between an asset (content/collection) and the folder to which it is linked. It is important to note that Relational metadata attributes have no correlation to the attributes of the asset (content/collection) being linked to the collection unit.
Existing properties defined in schema are
relName
...
relTrackable
...
mandatoryQuestion
...
relScore
...
keywords.
However, these properties behaviour is not defined as part of service. These fields properties are used as information storage purpose only in service. Behaviour of the application based on values of these fields properties is to be defined in the front-end(editors/players). Required attributes/ properties can be defined in relational_metadata schema.json file. An adopter can modify/completely replace the schema with their necessary properties. Any references of these properties in front-end (editors/players), has to be looked into for behavioural modifications.
...
Update Hierarchy API request sample:
...