OpenMetadata
OpenMetadata copied to clipboard
open-metadata
Data Glossary Tags: order Tag suggestions by Level and Alphabet
Is your feature request related to a problem? Please describe. Example. I have a Data Glossary Term Earth. It has 7 Children (continents) and each of them have Country children. Use cases:
- I only want to tag continent Europe to a table. I type in Europe. I get the list of 45 suggestions. As Europe is part of FQN name for Continent and Countries. And it doesn't seem that is ordered in any specific order.
This is a real case example, where I need to tag a parent term, but suggestion lists all the children, and children of children. And I have maybe 50 of them. What's worse - I only see the beginning of FQN, but I think there is a bug for that already.
Describe the solution you'd like If I type Europe in the Tag, I first get parent terms that contain Europe. And only then Children Terms.
Describe alternatives you've considered I tried typing in Geo.Continent.Europe but it didn't work.
Additional context Add any other context or screenshots about the feature request here.
@harshach and @chirag-madlani, we should have tag suggestions that include the hierarchy as we do in the Create Policy page as shown below:
There is another similar example for setting Team in the Add User page.
Yes. the tree hierarchy - would make the discovery of tags so much easier!
Hi @pmbrull @DovileKr
Can you confirm if current design for Tag Selection will be good here? I will add Alphabet sorting to this. My view for not going to hiearachy approach is:
- It will add indentation which will consume some space and we are already at crunch of space there
- To avoid long fqn as a line, We separate actual term and FQN with two different lines
- Search results will be more clear instead it will be hard in case of hierarchy view (May have horizontal scroll in case of n level of nesting)
Hierarchy view fits better if we have full width to use
cc: @sureshms @harshach
@chirag-madlani we don't need to expand by default right? only when the user searches for it the term needs to be expanded. The goal here is to make it easy for users to understand the hierarchy and making sure the term is selected from the right glossary.
