Giter Site home page Giter Site logo

carrineblank / micro Goto Github PK

View Code? Open in Web Editor NEW
5.0 7.0 3.0 11.28 MB

A Microbial Ontology of Phenotypic and Metabolic Characters, Assays, and Culture Media Found in Prokaryotic Taxonomic Descriptions

License: Other

ontology phenomic prokaryotic-taxonomic-descriptions microbiology bioinformatics-databases

micro's Introduction

MicrO

An Ontology of Prokaryotic Phenotypic and Metabolic Characters, version 1.5.1b (released Jun 14, 2018) .

Created by Carrine E. Blank, University of Montana, fall 2013 through spring 2016. Co-contributors and advisors: Hong Cui (University of Arizona), Lisa Moore (University of Southern Maine), and Ramona Walls (University of Arizona).

Includes terms and term synonyms extracted from > 3,000 prokaryotic taxonomic descriptions, collected from a large number of taxonomic descriptions from Archaea, Cyanobacteria, Bacteroidetes, Firmicutes, and Mollicutes.

The ontology and the synonym lists were developed to facilitate the automated extraction of phenotypic data and character states from prokaryotic taxonomic descriptions using a natural language processing algorithm (MicroPIE). MicroPIE was developed by Hong Cui, Elvis Hsin-Hui Wu, and Jin Mao (University of Arizona) in collaboration with Carrine E. Blank (University of Montana) and Lisa R. Moore (Macquarie University).

Contains ~ 3,660 terms and term definitions, along with thousands of term synonyms. Constructed in OWL Protégé; following OBO Foundry principles. Imports over 13,600 terms from 20 other external ontologies, including Phenotype Quality (PATO), the Gene Ontology (GO), and Chemical Entities of Biological Interest (ChEBI) using import modules. Contains over 29,600 logical axioms connecting entities and processes across multiple ontologies to facilitate inference of higher-order phenotypic traits.

Please cite: Blank CE, Cui H, Moore LR, Walls RL. 2016. MicrO: An Ontology of Phenotypic and Metabolic Characters, Assays, and Culture Media Found in Prokaryotic Taxonomic Descriptions, Journal of Biomedical Semantics 7:18. DOI:10.1186/s13326-016-0060-6. https://jbiomedsem.biomedcentral.com/articles/10.1186/s13326-016-0060-6

Thanks to Chris Mungall (LBNL), Elvis Hsin-Hui Wu (University of Arizona), Gail Gasparich (Towson University), and Gordon Burleigh (University of Florida) for comments and/or assistance with ontology construction and compilation of taxonomic descriptions.Many thanks to Oliver He (University of Michigan) for technical assistance with OntoBee and OntoFox, and Gareth Owen (ChEBI project leader, head curator) and other curators at ChEBI for assistance in the incorporation of microbial-specific chemical terms and synonyms into ChEBI.Thanks also to the instructors (Melissa Haendel, Matt Yoder, Jim Baihoff) and students of the 2013 NESCent Ontologies for Evolutionary Biology workshop, and to Karen Cranston (NESCent director) and the support staff at NESCent.

This work was supported by a grant from the National Science Foundation Assembling the Tree of Life Program (DBI-1208534), and by a travel grant to attend the 2013 NESCent Ontologies for Evolutionary Biology workshop.

TO DOWLOAD

  1. Download the MicrO.owl file in the folder "MicrOandImportModules"

  2. Execute MicrO.owl using Protege v. 4.3 or Protege v. 5.0.0 (runs in beta 17).

  3. Once executed you can then run the reasoner.

  4. You must have a live internet connection when you open MicrO.owl in order to properly download and access all the ontology import modules.

micro's People

Contributors

carrineblank avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

micro's Issues

Adopt release procedures

Suggestion: separate the "edit" version of the ontology from the currently released production file. Additionally give each release an owl:versionIRI value which is resolvable and remains permanently available. The framework in @cmungall's ontology-starter-kit may be useful.

replace # in term IRIs with /

I can change the prefix for all IRIs at once in Protege, but cannot switch from # to /. This will have to be done in text editor and then check, unless there is a way to do it with owlapi

Duplication of 'environmental material'

Hello!
Looks like you have a duplication of environmental material
capture

The one asserted under environmental feature should be removed along with its subclasses.

colont as a PCO term

I was going to file an issue saying colony should be a term in PCO (and I think it should be), but now I see it is imported from IDO. Therefore, we will need to coordinate this with IDO. I am just recording this here so I don't forget.

MICRO using some malformed IDs

MicrO in FAIRsharing

Dear Dr Blank and the MicrO Team,

I’m contacting you on behalf of FAIRsharing[1], the online registry of scientific data standards, databases and policies. Our aim is to make your resource as visible as possible to as large an audience as possible. We have emailed you a few times since July via [email protected] but have not yet had a response.

We have a FAIRsharing record for your resource[2]. To ensure our information is as correct and up to date as possible, would you or someone from your team quickly scan the record[2] and ‘claim’ it? (To claim, see link [3] below.) In addition, if the resource is no longer in use and should be deprecated, then we can represent that information as well. If we don't hear back from you in the next couple of weeks, we will mark the resource as Uncertain within FAIRsharing.

Claiming a record as either a group/institution or an individual also gives you the opportunity to make changes to the record yourself, allowing you complete control over how your resource is displayed in FAIRsharing. In addition, if you claim a record(s) as an individual, you can link the record to your ORCID.

FAIRsharing is about making your resource discoverable to a variety of users, such as journals and publishers, researchers and service providers, research and infrastructure projects and programmes, as well as curators, librarians, funders and other policy makers and data scientists[4]. A contact is essential should they have any questions about your resource.

Best wishes,
Allyson

[1] https://fairsharing.org, https://doi.org/10.1038/s41587-019-0080-8
[2] https://doi.org/10.25504/FAIRsharing.brhpb0
[3] https://fairsharing.org/own/standard/claim/bsg-s000784
[4] https://fairsharing.org/communities

Update deprecated ENVO terms.

MicrO needs to do a refresh of its ENVO imports as it is currently listing outdated/deprecated ENVO terms on services like OLS as if they are not deprecated. This is not limited to the example term below, as most if not all of this "food product" branch was deprecated in ENVO for FOODON terms >= 4 years ago. This can create confusion for users looking up terms to tag their metadata.

MicrO version of "pork chop" [ENVO_00003079] via OLS look-up

image

ENVO version of "pork chop" [ENVO_00003079] via Ontobee look-up

image

Use of CHEBI role

Are you sure you want to assert that things like IDO:symbiont role are subclasses of CHEBI:role?
capture

In IDO, it (and other IDO roles) are subclasses of BFO:role

capture

Incorrect use of xsd:int datatype for string label

    <!-- http://purl.obolibrary.org/obo/MICRO_0001179 -->

    <owl:DatatypeProperty rdf:about="&obo;MICRO_0001179">
        <rdfs:label rdf:datatype="&xsd;int">has cell width</rdfs:label>
    </owl:DatatypeProperty>

I am surprised the OWLAPI even parses this. This may be the reason MICRO is empty on OntoBee

Known Issues

  1. Logical axioms for three classes of microbiological culture media are not functioning.
  2. There are a number of new terms that are being requested for entry into ChEBI. Temporary terms are located under the class "ChEBI terms to be added and processed"
  3. External ontologies are currently being imported using temporary owl files (created by OntoFox) in the "MicrO and Import Modules" folder. Once the domain name request has been approved and purl addresses assigned, these will be replaced.

Environment classes in MICRO

Preventing domain creep may be useful when possible. The definitions of planktonic environment and periphytic environment look like they could be problematic.

capture

Please feel free to post new term requests on the ENVO tracker. Even if you decide you want the term to live in MICRO, we can perhaps offer some interesting discussion.

egg, egg yolk

Are these correct in the context of microbes?
Are egg and 'egg yolk' 'embryonic structure' for microbes?
Is 'blood clot' 'organism substance'? Microbes don't have blood.
We should review anatomical entity branch.

Fix IRIs of imported ontology subsets

The imported ontologies still have ontofox IRIs, so they don't resolve when the ontology is opened in Protege. They should either use obo foundry purls or direct links to the github location.

Nesting incorrect for measurement of pH growth assay

'pH growth assay'
 and ('uses chemical reagent' some 
    ((hydron
     or hydroxide)
     and ('has quality' some 
        (acidity
         and (
              ('has measurement' some ('has unit' value pH))
         and  ('has magnitude' value 5.0))))))

I believe the intent is that the magnitude is a property of the measurement, not the quality. Consider reaching out to the OBI people for descign patterns here.

Morphology

Need to add:
Ring-like, or ring-shaped

Use of ENVO:habitat as a superclass for MICRO:'subaerial prokaryote habitat'

ENVO differentiates habitats from environments in that the former are environmental systems that can support the life of and allow the growth of a population of some (usually species-level or OTU-level) taxon. For this to work here, one would have to assert that 'subaerial prokaryotes' have such a quality. I'm not sure that's wise, as many of them would just happen to be there in the long tail of the abundance distributions.

capture

Also, the exact synonyms seem a little strange in that they sound more like qualities or dispositions:
capture

Use PURLs for imported files

Currently imports are referenced via GitHub-specific URLs such as https://raw.githubusercontent.com/carrineblank/MicrO/master/MicrOandImportModules/BFO_imports.owl. It would be good to create PURLs for these such as http://purl.obolibrary.org/obo/micro/imports/BFO_imports.owl

develop a set of editing and release SOPs

You can look at what BCO does (https://github.com/tucotuco/bco/wiki), but that is only partially worked out and still has lots of manual steps. Probably better for us to look at what ENVO is doing and try to emulate some of that. We don't have to do it all at once, but we will at least need a basic release policy for the publication submission.

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.