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
Beginning May is a deadline to have a very very very good data landing page.
we need to ensure that all the ro-crates we want listed, are listed, in a way that is easy to navigate (there are so many of them)
we want to ensure that all the ro-crates have a ro-crate-metadata.json file in them, otherwise they cannot be viewed -> if a new harvest/qc does not work, it should not delete the previous content and ro-crate file!
we want to have the ro-crate viewer organised in a way that is nice for humans to navigate
we want summary-of-event and summary-of-samples and summary-of-sequences and summary-of-results tables that can be easily found and read
This is a placeholder issue to make sure we do not forget this. Probably should arrange for a meeting in Feb - because VLIZ does need guidance from EMOBON as to what you want on the page - after all, it is not just for us, it is for y'all! @isanti can you timetable such a meeting, or should I?
The text was updated successfully, but these errors were encountered:
I think we could create a new tab and split the existing "Data" tab into several ones.
For example, if we had one tab/section for the "Sampling Logsheets", one for the "MetaGOflow run outputs" and another one for the "Other RO-crates" for all the rest, it could work.
There would be at least divided somehow.
Especially if we could have different colour in the backgrounds, i.e. if not all of them were blue.
Beginning May is a deadline to have a very very very good data landing page.
This is a placeholder issue to make sure we do not forget this. Probably should arrange for a meeting in Feb - because VLIZ does need guidance from EMOBON as to what you want on the page - after all, it is not just for us, it is for y'all!
@isanti can you timetable such a meeting, or should I?
The text was updated successfully, but these errors were encountered: