Git Product home page Git Product logo

p02-biological-terms-review's Introduction

P02-Biological-terms-review

A collaborative project to review and streamline biological codes in the SDN Parameter Discovery Vocab P02.

Rationale

The list of P02 discovery parameter terms linked (via P03) to the P08 category “Biological oceanography” is cluttered with terms specifying some degree of “taxonomic dependency”. For example: {BNUC for Bacteria generic abundance in sediment} and {BAUC for Bacteria taxonomic abundance in sediment}. This distinction between taxonomic/non-taxonomic or generic criteria was made when BODC started mapping its biological codes to the ITIS species registry and before P02 became a key vocabulary for data discovery as adopted by SeaDataNet/SeaDataCloud in Europe. The need for this distinction at the P02 level has become obsolete and confusing. It is proposed to address this as part of our review the P02 Parameter Discovery vocabulary.

First step: Rationalise abundance and biomass codes

Option #1 (see and edit XL file abundance_and_biomass) - this proposal assumes that we will keep some degree of distinction between broad organisms' type (prokaryotes, phytopankton, zooplankton etc.) at the P02 level at least for the abundance and biomass codes. These have been kept close to what was already in place but the distinction taxonomic/non-taxonomic has been removed. Also I have tended to group abundance and counts and kept biomass separate. Abundance and/or counts or densities are typically associated with field surveys while biomass would be more often associated with environmental modelling and ecological budgeting.

Feedback needed and ideas and alternative approaches welcome.

Option #2 would be going completely generic with, for example, codes for: Biota abundance in water bodies, Biota abundance on the bed or in sediments, Biota biomass in water bodies, Biota biomass on the bed or in sediments, Biota counts in water bodies, Biota counts on the bed or in sediments, etc.

All would map to P03 B070. However with option#2 users would no longer be able to target specific groups of organisms via the P02 marking unless we allow P01 to P02 to move from a many-2-1 to a many-2-many relationship. If we stay with the many-2-1 then dataset markup via CDIs or dataset discovery via EDMED would no longer be able to target specific group of organisms using P02. If we allow many P02 for one P01 the management of the relationships becomes more complexe.

Second step: look at other P02 codes linked to P03 codes under P08 "Biological Oceanography"

List candidates for deprecation, broadening and new terms. I propose to start working on this once we've reached a consensus on the abundance and biomass codes.

p02-biological-terms-review's People

Contributors

gwemon avatar

Watchers

 avatar  avatar  avatar  avatar

p02-biological-terms-review's Issues

Rationalise abundance and biomass codes

Looking at option1 and option 2 on https://github.com/gwemon/P02-Biological-terms-review:

For option 1: it's unclear to me under which P02 how generic terms such as "Abundance of biological entity specified elsewhere per unit volume of the water body " http://vocab.nerc.ac.uk/collection/P01/current/SDBIOL01/" could be included. As the term is generic, it can be used for most of the functional groups which would have a dedicated P02. Would this term then be included under all relevant P02's? I do not see how we can make sure that a sure looking for all phytoplankton abundances will get all phytoplankton abundances and only phytoplankton abundances.

Option 2 seems as better fit for the generic terms, but may be less suited for to discover the non-generic terms. I don't understand how we would still be able to target specific groups using option 2, even with a one to many relationship.

I do not know if we want to continue with the non-generic terms? Are people still using them and if so whether they can be persuaded to switch to the generic ones? Perhaps we would need 2 separate systems and the non-generic one could in time be deprecated?

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.