Git Product home page Git Product logo

emo-bon.github.io's Introduction

A long-term omics observatory of marine biodiversity

Launched in summer 2021, EMBRC’s European Marine Omics Biodiversity Observation Network (EMO BON), aims to enhance the European contribution to global genomic observation efforts. EMO BON will fill current gaps in biological observation, while offering insights into the genetic composition of marine biodiversity.

Its primary aim is to ensure steady, continuous generation of ‘baseline’ data on biodiversity at EMBRC sites following FAIR (Findable, Accessible, Interoperable, and Reusable) data principles. EMO BON will ultimately provide Europe with a means to monitor and understand its marine biodiversity. This in turn will facilitate the development of new products and services for society.

Participating stations and sampling

EMO BON collects samples from the water column, soft substrates, and hard substrates, aiming to allow researchers to explore marine diversity in different habitats. It will be based around a network of currently 16 sites from Northern Norway to the tropical Red Sea in Israel. Standard operating procedures have been developed with the participating EMBRC partners and can be found in the EMO BON Handbook.

Samples are collected at the participating observatories every two months (water and soft substrates) to a year (hard substrates) and processed according to the SOPs. Four replicas are collected, two for immediate use, and two are biobanked for future exploration. Samples are collected centrally in Paris every four-to-six months and shipped for DNA extraction and sequencing at a centralised facility.

EMO BON data

EMO BON data are managed and published via the EMO BON GitHub space, which sits behind this webpage. The sampling logsheets from each station are harvested into GH, undergo a quality control, and then are combined, semantically annotated, and published in CSV and RDF formats. Each repository is described and wrapped up as a Ro-Crate. All logsheet data are open access.

As the sequences are produced by the sequencing facility, they will be archived in ENA under project PRJEB51688, after an embargo period of 6 months. The ENA accession numbers will be made available on the EMO BON GH also.

EMO BON bioinformatics

Currently, all metagenomics from EMO BON are to be processed through the MetaGOflow pipeline. The outputs from this processing are also stored in our EMO-BON GH.

Navigating this EMO BON space

As you scroll down this webpage you will see Our Data Packages. The table lists the selected repositories which are of the most interest to users, including

  • The repositories holding the logsheet (meta)data for the observatories, listed by observatory name
  • Governance metadata, use to control the data management workflows and actions in this GH space
  • Sequencing data, containing all the ENA-related metadata

You can browse these either as a GitHub reposotory (click on the GH icon) or via our Ro-Crate viewer (click on the filing box icon). For the full set of repositories, you can also navigate directly to the GitHub space.

emo-bon.github.io's People

Contributors

kmexter avatar cedricdcc avatar laurianvm avatar marc-portier avatar bulricht avatar

Watchers

 avatar Ioulia Santi avatar  avatar

emo-bon.github.io's Issues

improve listing of crates

would it be possible to list our crates in an automated way? i.e. by scanning the emo-bon repos for a ro-crate-metadata.json file and grabbing the description from the repo description?

Idem for the profile crates.

Produce rdf description of space

Based on _data/space.yaml
should contain :
@Prefix schema: https://schema.org/
@Prefix dm: https://open-vocabularies.vliz.be/dmbonassistant#

  • schema:name
  • schema:hasPart => list of all members being crates and profiles
  • dm:governanceCrate
  • rdfs:type dm:Space

use @id = https://data.emobon.embrc.eu/dmbon-space.json => will be the href link to the space definition being a jsonld file
Note : inject domain from _config

output should be in application/ld+json => in gh-pages

And consider including the jsonld with a script tag embedded in the index.html

general site navigation

titles in the navbar (about, publications, data, ro-profiles, team) do not correspond with the titles of each section (about us, publications, our data packages, profiles, contact), nor with the fragment identifiers (aboutsection, publications, crates, profiles, team)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.