Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Clean up metadata side panel for datasets

See original GitHub issue

There’s several small niggles I’ve always had with the metadata panel for datasets. image

  1. 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.
  2. 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)
  3. Similarly (though more debatable) for File Path.
  4. Why do we need Pipeline field? Is it just the same as the registered pipeline selected?

Issue Analytics

  • State:closed
  • Created a year ago
  • Reactions:1
  • Comments:9 (9 by maintainers)

github_iconTop GitHub Comments

AntonyMilneQBcommented, Jul 28, 2022

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.

AntonyMilneQBcommented, Jul 6, 2022

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.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Dataset + File Management —
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 >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found