All ideas are welcome. Just because the Idea doesn't make it into the product immediately does not make it a bad idea.
We have come up with two scenarios that could be addressed with different asset relationship values. Instead of this being a set list, it would be great if we could extend the options to include relationships that work for our organization. We specifically would like to have, "does not include", or some way to represent that a term is an exception to another term, and something like, "by", representing that a term is a dimension or 'slice' of another term, such as 'patients by arrival date'.
Guest
Thanks for registering the idea. The idea of being able to define custom relationships between terms makes sense as there will always be use cases that are specific to certain client i.e. your example of an analytics representation and dimension relationships. We will look into this idea and look to get it registered in our backlog for future improvement.
The custom relationship capability has been shipped in the product and is available in the SKT
Attachments Open full size