Clean up metadata side panel for datasets
See original GitHub issueThere’s several small niggles I’ve always had with the metadata panel for datasets.
- Why do we show
Type: dataset
at all (also applies to nodes)? It’s obvious from the icon and information provided that’s what it is. - Dataset Type is always too long to fit in, when really all that people care about is the last part after the final
.
. Can we make it so that we only show that part but then on mouseover it shows the whole path? (The full path currently shows on mouseover) - Similarly (though more debatable) for File Path.
- Why do we need
Pipeline
field? Is it just the same as the registered pipeline selected?
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Dataset + File Management — Dataverse.org
A dataset in a Dataverse installation is a container for your data, documentation, code, and the metadata describing this Dataset.
Read more >View and edit metadata—ArcGIS Pro | Documentation
Only metadata in ArcGIS format is visible in the details panel in the catalog view, on the browse dialog box, in the Catalog...
Read more >Managing dataset metadata ‒ Qlik Cloud
Filtering on metatags · Open the Catalog tab if it is not open. Under the Types dropdown, select Data. · Select All filters...
Read more >Export metadata and annotations from a dataset | Vertex AI
If you want to export metadata and annotations for all of the Dataset 's annotation sets, then click View more more_vert and then...
Read more >Cleaning Noisy and Heterogeneous Metadata for Record ...
One common way of cleaning metadata is to use a bibliographic reference dataset. The challenge is to match records between corpora with high...
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 FreeTop 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
Top GitHub Comments
I think it’s fine to shorten in exactly the same way as a built in dataset type (so long as the full path is available on mouseover still). No need to put in custom logic to detect whether it’s the dataset type belongs to kedro or not.
Dataset icon and
Type
field: fair point - you’re right that there are multiple possible icons for a kedro dataset, that’s not a bug. Let’s not do this then.Shortening the path: Yeah, this is trickier because you might have some other sort of filepath like on windows or something on the cloud. It’s probably easiest to extract the relevant “last part” on the backend side since it might need fsspec to handle the general case correctly. This would then mean sending both the “last part” and the full path to the frontend in two different fields. I’m also not sure whether this is such a good idea because the earlier part of a filepath might be useful to discriminate between two different files with same filename but in different directories. So possibly we shouldn’t make this shortening right away - just the dataset type shortening.
One thing I forgot to mention before that would be nice to fix though is the trailing
/
on the file path. I’m not sure why that appears on kedro viz for lots (all?) datasets.