Overview so users can know where to go?

[kmexter]

If all our emo bon data are in one set of crates, and different metagoflows in others, don't we need to provide a way for users (human and machine) to know what is where? I was in particular thinking of this when I had to describe "the"emo bon data for FAIR EASE WP5

[kmexter]

Discussed during the FE GA 2024: we will have a CSV that will contain an overview of the emobon data collected, and on the data landing page this will be viewable, via a filterable table viewer, via the top menu.
@cymon and @cpavloud I would appreciate your comments on what should be in this CSV. Not everything, please! My initial ideas are:
observatory name (country?), date, a bunch of selected sample info (HERE is where you can especially advise), ENA sample and run accession numbers, genoscope ref code, material sample id, event id...anything else?

[cpavloud]

But, if the EMO BON data are in ENA (where they will be eventually), we will not have them in RO-crates, right?
So there will be no need to link the EMO BON data RO-Crate with the metaGOflow RO-crates.

[kmexter]

this is about having one overview table, accessible from the data landing page (and hopefully some future EMBRC-based web page) so people can see what sampling has happened, what samples are already in ENA, etc.
The ENA data themselves are not in ro-crates, no, as they are too big and are in ENA, indeed. But the accession numbers should be linked to material sample ids in an overview table somewhere.

[cpavloud]

Ok, I have talked with the communications team in EMBRC about the website and what are our needs.
At the moment, they told me that it's easier to have static files and images (so, not interactive ones).
So I don't know if (currently) we can have a table with a filter.

But anyhow, what we probably want is a table with the following?

| EMBRC Node (Country) | EMO BON Observatory | ENA project accession number | Sample collection date | Habitat | Target Gene | Number of samples | Date of sample shipment to the Secretariat | Date of sample shipment to Genoscope | Date of sequence data delivery from Genoscope | Date of sequence data embargo termination | Data paper submission date | Data paper acceptance date | Data paper doi |

Habitat should be water column OR soft substrate (microbes) OR soft substrate (meiofauna) OR soft substrate (marcofauna) OR hard substrate
Target Gene could be NA (for metagenomics) OR 18S rRNA (for metabarcoding) or COI (for metabarcoding)
If we use Number of samples as a column, then we will be working with the total number of samples. It could be enough? If we want more detail, then we will have to include one row per sample.

[kmexter]

Great that you have talked to them! I thought it was all forgotten about
Static is fine - in that, if we have a table viewer visible from our data landing page, readers can be redirected to there. and/or we can regularly update their static table based on ours. Maybe we should talk about this when you visit VLIZ, we can mock something up? If comms tell you more about what they can do (e.g. wrt menus, sidebars, images, how many pages they can make (as e.g. if we want bios on the stations, that would be separate pages) then we can design around that? And then pass that by the opco?