Remove "Tags" from datasets
See original GitHub issueNote. Good starter task for anyone wanting to get more familiar with kedro-viz!
Along similar lines to https://github.com/kedro-org/kedro-viz/issues/962…
Currently every single graph node on kedro-viz has a Tags field:
In reality, however, only kedro nodes can have tags. Datasets, transcoded datasets and parameters should not have this field.
- Move
tags
from being a field in the base modelflowchart.GraphNode
to only in the kedro node modelflowchart.TaskNode
- Remove
tags
from instantiations of the non-TaskNode
models, e.g. calls toGraphNode.create_parameters_node
should no longer have atags
argument (you’ll see it’s currently just set toset()
anyway) - Remove tags field from the frontend for everything but a task node
Issue Analytics
- State:
- Created a year ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
How to delete a tag on dataset
I think you just have to go to the dataset(s) where that tag is stored and remove the tag from there. Then it...
Read more >Managing Dataset Tags
Navigate to the tab All Datasets . Select a dataset. Select Tag and then choose Manage. Select a tag, choose Delete, and confirm...
Read more >Deleting a Sequence
So Deleting a Sequence works well, get a reference to the sequence then Dataset.Remove(seq) no problem. Private sequence's get mangled to a single...
Read more >Deleting labels | BigQuery
Deleting a table or view label · In the Google Cloud console, select the dataset. · Click the Details tab, and then click...
Read more >TagCleaner: Identification and removal of tag sequences from ...
To our knowledge, TagCleaner is the first web application optimized to automatically detect and remove tag sequences from metagenomic datasets.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@AntonyMilneQB – had a brief discussion with @tynandebold on this. The above suggested implementation to move tags from flowchart.GraphNode to flowchart.TaskNode is affecting the filtering as it’s no longer showing any dependent datasets and maybe (subjective to users) showing an incomplete picture of the pipeline when u filter by tags.
We also realised tags are not linked to modular pipelines, so in a collapsed mode - if you click on a tag within a modular pipeline – it will say no data which is not expected behaviour. For the above 2, i think we need to create a separate ticket on how tag interactions work on FE and for this Tynan will also check on how much this feature is used.
The main goal of this ticket is to remove the unnecessary tag information from metadata panel for datasets, and parameters and only have for task node. This can be easily achieved in the front-end (via isTaskNode show Tag else don’t) without any change to BE. So maybe we just handle it that way for now.
please let me know if the above makes sense.
cc @Huongg
So it seems we’re not tracking clicks on tags right now (maybe because they’re dynamic?) but we are tracking filtering by the element types. Here’s that data for over the past 90 days in an aggregate count (not unique):
Safe to say that it isn’t used too much.
Rashida, I agree with this part:
If we only do that it seems we should be safe and still solve the original issue created by Antony.