You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The frontend has a very convenient method for navigating from a derived dataset to one or more of its related raw datasets, by providing urls in the "Input Datasets" field.
But is there a similar mechanism to go the other direction? If I'm looking at a Raw Dataset I'd like to easily see the various related Derived Datasets. Is there any mechanism that I'm not seeing for this?
The text was updated successfully, but these errors were encountered:
This is actually kind of implemented but it's connected to the reduce/analyze workflow. In the "Reduce" tab of the dataset details view there's a table of datasets derived from that particular dataset. The problem is that the reduce workflow isn't finished and the development of it has kind of stalled. I propose we move the existing table out of the reduce workflow into it's own entity as this is a useful feature to have.
The frontend has a very convenient method for navigating from a derived dataset to one or more of its related raw datasets, by providing urls in the "Input Datasets" field.
But is there a similar mechanism to go the other direction? If I'm looking at a Raw Dataset I'd like to easily see the various related Derived Datasets. Is there any mechanism that I'm not seeing for this?
The text was updated successfully, but these errors were encountered: