Link asset and versioning (relations)

For the case of materials, relational will not appear as an important aspect, as it is a series of materials that we stock as a library. Same for the color library.

In the case of product design prototyping, this can become an important part of the compounding process, as we can use various textures (materials), and they can already exist in the system. (we could also ask to save this material as a standalone material; if the system doesn't know this material).

• When I upload a file, parent or child, that already exists on my instance, the system recognizes the duplicate and allows me to link to the existing file instead of creating new assets
• As a user, if I have a child asset that is a link, I want to be able to choose the relevant version of that asset used 
• For a file that is linked in my compound doc, if the original is changed I can accept or refuse to change it in my compound doc  
• I can also display where the same binary appears on the instance, both in compounds, but also individually, to allow me to find everywhere this asset's binary file has been used. This is particularly relevant if I need to mass change the file, for example, if a license expires.
• When a change has been made to the original asset, that is linked to the compound, I need to be able to accept or refuse that newer version

For later:

• As a user, I need to add a child that is an asset already existing on an instance
• I would like to create a compound doc, all or in part, using files already on my system and for these to remain linked to my compound doc