Hi. Can someone please explain to me the logic behind 4 sub-tabs for relationships between Glossary Terms? I'm talking about Contain, Inherits, Contained by and Inherited by. Woudn't only 2 sub-tabs be enough? Let's say I have a term Address, and I add a relationship that it Contains the term Zip-code. But when I open term Zip-Code I have 4 types of relationships there, 3 of them are not opened and I don't see what's inside, so I have to click each to understand the connections with other terms. A users doesn't always know already the kinds of relationships terms have, so I chose the right tab right away - I have to go through all of them. To be honest this system seems overly complicated and not user-friendly to me. Not all users would think to click through each of many sub-tabs, so terms relationships would remain hidden from users, which kinda negates their whole point. Maybe if all 4 types of relation were visible on this screen it would solve this non-user-friendliness? But them again, I kinda don't understande the whole Inheritance thing. How is Inherits different from Contained by? Wouldn't it be enough to simply have 2 types of relation - Contains and Contained by?

Hey there 👋 I'm The DataHub Community Support bot. I'm here to help make sure the community can best support you with your request. Let's double check a few things first: ✅ There's a lot of good information on our docs site: www.datahubproject.io/docs, Have you searched there for a solution? ✅ button 2️⃣ It's not uncommon that someone has run into your exact problem before in the community. Have you searched Slack for similar issues? Yes button Did you find a solution to your issue?

@big-carpet-38439 can likely speak to the glossary structure- It’s set up to help group terms into organizational knowledgebases that can be easily traced to one another

to me it seems that such complicated structure makes if difficult to trace things, not easy. But let's see what John can tell about this.

Let's start with definitions of each type of relationship to see if that helps clarify a bit further: Contains is used to relate glossary terms when one may be a superset of another. For example: Address Term -> Contains -> Zip Code Term, Street Term, City Term Inherits Is used to relate glossary terms when one may be a subtype of another. For example: Email Term -> Inherits -> Pii Term Now whether this is user friendly is another story. I agree that it is not. What did you have in mind to simplify? A single screen with different sub-sections for each type of relationship?

@big-carpet-38439 thank you! a very fine line of terms relationship, I don't think I've seen it used in Glossaries like that. TBH I would still think that a listing of subtypes can be called a superset of subtypes, but that may be just my perspective. Ideally I think I'd like to see the section with related terms on the main term entity paige, on the panel on the right (screenshot 1 with the space marked by red pen). So when I open the term I can see right away if the terms related to this one exhist, and if yes what are they - the same way we see related terms for datasets (screenshot 2)

Ooo this makes a lot of sense

oh yes, Parent Terms and Child Terms are definitely more intuitively understandable for me! and hovering can detail the type of relationship further also I think calling the relatinship "subtype" instead of "inherits" also makes it much more clear :)