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
Realistically this means that we will end up with O(100) feedstocks which are all named CMIP6-modelabc, which is less than ideal from a UX experience.
Would it be possible to add a tag or a collection to these feedstock and then on the catalog end group these all together under one tab?
Id imagine that on the main page you would get a CMIP6 item.
The easy way would then be that this unfolds and reveals all the feedstocks that belong to the collection.
What might be even more nifty is if there was a possibility to group the files and logs together, so that the collection appears like a single feedstock from the catalog view. This way a user could make a request, which would be automatically dispatched to many feedstocks, but the Recipe Runs Tab would show all new runs from various feedstocks. I realize this is a lot more work, but just wanted to bring it up for discussion.
The text was updated successfully, but these errors were encountered:
Currently a feedstock represents the highest 'collection' or group on the catalog website.
For very large projects like CMIP6, it seems it will be necessary to split the recipes into multiple feedstocks.
Realistically this means that we will end up with O(100) feedstocks which are all named
CMIP6-modelabc
, which is less than ideal from a UX experience.Would it be possible to add a
tag
or acollection
to these feedstock and then on the catalog end group these all together under one tab?Id imagine that on the main page you would get a
CMIP6
item.The easy way would then be that this unfolds and reveals all the feedstocks that belong to the collection.
What might be even more nifty is if there was a possibility to group the files and logs together, so that the collection appears like a single feedstock from the catalog view. This way a user could make a request, which would be automatically dispatched to many feedstocks, but the
Recipe Runs
Tab would show all new runs from various feedstocks. I realize this is a lot more work, but just wanted to bring it up for discussion.The text was updated successfully, but these errors were encountered: