Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SEPIO use cases related to globalbioticinteractions.org / GloBI #4

Open
jhpoelen opened this issue Jan 26, 2017 · 0 comments
Open

SEPIO use cases related to globalbioticinteractions.org / GloBI #4

jhpoelen opened this issue Jan 26, 2017 · 0 comments
Assignees

Comments

@jhpoelen
Copy link
Contributor

Hi!

I was pretty excited to stumble across SEPIO and I was hoping to get some guidance on adopting SEPIO by sharing the following use cases:

  1. modeling evidence supporting, refuting or capturing "reasonable doubt" related to species interaction statements: an example of a past discussion about a claim that Sea Otters (Enhydra) eat American Beavers (Castor canadensis) can be found here: Do Sea Otters really eat American Beavers? globalbioticinteractions/globalbioticinteractions#118. Rather than describing the statements made in free-form text in an issue or encoded in some java code, I'd like to be able allow for modeling the statements and their relationships as part of our data model.
  2. capturing taxonomic name correction and linking process: a big chunk of GloBI concerns taxonomic name / term matching. Currently, a rudimentary model exists in GloBI to record how a taxonomic name was originally described in a data publication and how the name was eventually linked to external name sources like itis.gov or ncbi's taxonomy. Rather than implicitly documenting the name matching, correction and linking process in source code and wiki page (e.g. https://github.com/jhpoelen/eol-globi-data/wiki/Taxonomy-Matching), I was hoping to explicitly encode the process and its outcome as part of the data model.

Please let me know if these use cases make sense whether they are suitable to help drive the ongoing development of SEPIO. I'd be happy to try and adopt the ontology, but will probably need some guidance in getting started.

Curious to hear your thoughts on possible next steps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants