Oh, I was more referring to having a clickable link for the dataset, rather than adding the dataset GUID to a search index.
Both fixes would improve things, but making the dataset clickable -- similar to how Input Model is clickable -- would be best.
Fixing that would make this feature great.
Hmm, I guess that is doable, this is a good point, search for the GUID is not always trivial (or maybe at least we can put in the description the project/dataset/version )
Hi AmiableFish73
Hi all - is there an easier way track the set of datasets used by a particular task?
I think the easiest is to give the Dataset an alias, it will automatically appear in the Configuration section:Dataset.get(..., alias="train dataset")wdyt?
Hi @<1523701205467926528:profile|AgitatedDove14> - yes, that's great! It's much cleaner. I was thinking of tracking the input datasets as artifacts, but the alias method is better.
The user interface still only displays a GUID - it would be much preferrable if it displayed a clickable link which took me to the dataset details page -- particularly since the GUID doesn't search properly.
Fixing that would make this feature great.