GithubHelp home page GithubHelp logo

planteome / plant-stress-ontology Goto Github PK

View Code? Open in Web Editor NEW
14.0 9.0 9.0 52.42 MB

An ontology containing biotic and abiotic plant stresses. Part of the Planteome suite of reference ontologies. Formerly called the Ontology of Plant Stress

Makefile 75.61% Batchfile 0.32% Shell 10.64% Scala 7.74% Ruby 5.69%
plant-stress ontology abiotic-stresses obofoundry obo biotic-stresses

plant-stress-ontology's Introduction

DOI

Plant Stress Ontology

Description: One of the Planteome suite of ontologies for plants. The PSO describes biotic and abiotic plant stresses.

More information can be found at http://obofoundry.org/ontology/pso

Versions

Stable release versions

The latest version of the ontology can always be found at:

http://purl.obolibrary.org/obo/pso.owl

OBO Dashboard- PSO

Editors' version

Editors of this ontology should use the edit version: src/ontology/pso-edit.owl

Contact

Please use this GitHub repository's Issue tracker to request new terms/classes or to report errors or specific concerns related to the ontology.

Acknowledgements

This ontology repository was created using the Ontology Development Kit (ODK).

plant-stress-ontology's People

Contributors

austinmeier avatar cmungall avatar cooperl09 avatar elserj avatar mariealaporte avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

plant-stress-ontology's Issues

PSO:0000237 cassava Acaro solitario damage

Need to clarify the name and taxon ID of this term. It is linked to NCBI taxon for the genus Oligonychus (NCBITaxon:50018), which includes mites & ticks. Acaro solitario is not listed in NCBI, and I have not been able to locate it with a quick search of the literature.

The synonym OLIGPE is listed at EPPO: https://gd.eppo.int/taxon/OLIGPE for Oligonychus peruvianus, which appears to be an old name.
ácaro solitario appears to be a Spanish synonym?

Also need to change the affected plant part to vascular leaf

Travis check broken?

@marieALaporte @cmungall
my most recent update to oops-edit.owl has seemed to break the travis check. I thought it is because I didn't update the imports in the Makefile, but even after adding the new 'aps-test-diseases.owl' and 'upper-level.owl' to the Makefile imports the travis check is still not working.

Cloning the repo, and opening the ontology on a different computer seemed to work okay, but I'd like that shiny green button to remind me that everything is okay.

I'm guessing it has something to do with the paths of the imported ontologies? If either of you could take a look at my last two commits, and see if they notice something odd, I'd be appreciative.

The error travis gave me:
make: *** [mirror/ncbitaxon.owl] Error 137
The command "cd src/ontology && make test" exited with 2.

Upper classes hierarchy for pattern apply?

It was mentioned that we could have a separate pattern file for creating the upper classes in the ontology for using the yaml design patterns. @cmungall could you point me to an example, or template I could use to achieve this?

List of plant diseases from PHI-base

It would really help the Pathogen-Host Interactions database (PHI-base) to have a comprehensive ontology of plant disease, so I'm including a table of all plant diseases from PHI-base: specifically all diseases where the host species is part of the Viridiplantae kingdom (NCBITaxon:33090).

Note that the list has not yet been manually reviewed (the PHI-base team is planning to do this over the next month or so), but I'm posting it here first so you can check how suitable it is.

See below for a link to the table as a tab-separated file (I had to zip it because GitHub won't allow TSV files to be uploaded to issues).

phibase_plant_diseases.zip

Table columns

I've tried to follow the structure of the TSV file that contains the scrape of the APS website, but I've included some extra columns to help with manual review of the data:

  • disease_old: the disease name as it currently appears in PHI-base (from version 4.10 of the database, which has not yet been released). I've included this so you can compare the original name to the cleaned name in the next column.

  • disease: the revised disease name, after normalizing letter case, removing redundant host information (see section below), and fixing inconsistent naming. I've tried to simplify the disease name as much as possible, with the aim of making the fewest assumptions about how PSO is planning to name their disease classes.

  • pathogen: the NCBI Taxonomy ID for the pathogen species. This is sourced directly from PHI-base.

  • pathogen_label: The scientific name for the pathogen species. This is sourced directly from PHI-base, and hasn't been cross-referenced against the names in the NCBI Taxonomy.

  • host: the NCBI Taxonomy ID for the host species. This is sourced directly from PHI-base. Note that the host column includes model host organisms (such as Nicotiana benthamiana in the case of publications containing tobacco leaf assays).

  • host_label: the scientific name for the host species. This is sourced directly from PHI-base, and hasn't been cross-referenced against the names in the NCBI Taxonomy.

  • plantstructure_old: the name for the affected plant tissue as it appears in PHI-base. I've remapped these names to Plant Ontology terms in the following columns; I've included the original names so the mapping can be manually reviewed.

  • plantstructure: the Plant Ontology term ID that is the closest match for the tissue type in PHI-base. Some rows contain multiple values, which are delimited with the pipe character. I manually remapped these terms myself, but I haven't manually reviewed the source publications to check whether the PHI-base tissue name is correct.

    Note that I was unable to find a PO term for 'seedling': an exact match for this term exists in the Brenda Tissue Ontology (BTO:0001228), but not in the Plant Ontology. I've left a placeholder called '(seedling)' in the column for now.

  • plantstructure_label: the corresponding label for the Plant Ontology term ID, also delimited with the pipe character (the order of the labels matches the order of the term IDs).

  • references: a list of publication identifiers sourced directly from PHI-base. The list is delimited with the pipe character. These have not been manually reviewed, so I can't guarantee that they're primary sources describing the disease. I've preferred the PubMed ID (PMID) where available, and used the DOI where the PMID is missing. I think we almost always have a DOI in addition to the PMID, so please let me know if you want that included in a separate column.

Notes

As previously mentioned: to keep the disease names as general as possible, I've removed the host common name or genus from the disease name where it matches the host in the 'host' column, since the information seems redundant in these cases (although it's arguably less redundant when the disease name contains the genus of the host, since that specifies that the pathogen is not specific to the host).

I've kept the pathogen name in the disease name when it seems to be part of the accepted name for the disease (e.g. Fusarium ear blight). This might not be ideal if PSO plans to include the pathogen and host species with the disease name: if the term names were naively generated, PSO would end up with disease names like 'Fusarium graminearum Fusarium ear blight on Triticum aestivum', instead of something less redundant like 'Fusarium graminearum ear blight on Triticum aestivum'.

For cases where the host name in the disease doesn't match the host in the host column, I've retained the host name (usually the common name) in parentheses after the disease name. This is to help identify cases where a model host organism has been used instead of the 'natural' host; the model hosts are usually Nicotiana benthamiana or Arabidopsis thaliana.

The inclusion of model hosts could be problematic. I'm not sure whether PSO wants to make a distinction for model hosts, or whether they should be included at all. (While it's true that many pathogens can cause disease on tobacco leaves when inoculated, it may not be notable that they can do so.)

Many of the diseases in the list may be synonymous with each other; the PHI-base team is hoping to identify as many of these cases as possible when we manually review the list.


CC: @ValWood @CuzickA

bin folder

I think you should delete the folder named 'bin' from the repo

list of PDO diseases that don't have a DP

PDO:0000126 rice rugged stunt viral disease
PDO:0000061 wheat bacterial leaf blight
PDO:0000219 maize Marasmiellus borde blanco fungal disease
PDO:0000012 maize fungal disease
PDO:0000079 Microdochium oryzae pecky rice fungal disease
PDO:0000086 rice Fusarium seedling blight fungal disease
PDO:0000047 rice leaf scald fungal disease
PDO:0000170 rice phytoplasma disease
PDO:0000005 plant viral disease
PDO:0000027 rice aggregate sheath spot fungal disease
PDO:0000008 wheat bacterial disease
PDO:0000004 plant fungal disease
PDO:0000129 rice yellow dwarf phytoplasma disease
PDO:0000272 maize Gonatobotrys simplex minor ear rot fungal disease
PDO:0000125 rice necrotic mosaic viral disease
PDO:0000203 maize Didymella leaf spot fungal disease
PDO:0000153 maize purple leaf sheath bacterial disease
PDO:0000217 maize Ascochyta ischaemi yellow leaf blight fungal disease
PDO:0000011 maize bacterial disease
PDO:0000196 maize Botryosphaeria gray ear rot fungal disease
PDO:0000232 maize Hyalothyridium leaf spot fungal disease
PDO:0000183 maize northern leaf spot fungal disease
PDO:0000045 rice leaf smut fungal disease
PDO:0000200 maize Cunninghamella minor ear rot fungal disease
PDO:0000003 rice bacterial disease
PDO:0000210 rice Pythium root rot fungal disease
PDO:0000075 Curvularia pecky rice fungal disease
PDO:0000209 rice Fusarium root rot fungal disease
PDO:0000077 Fusarium pecky rice fungal disease
PDO:0000039 rice eyespot fungal disease
PDO:0000092 bacterial pecky rice
PDO:0000010 wheat viral disease
PDO:0000245 maize Peyronellaea yellow leaf blight fungal disease
PDO:0000013 maize viral disease
PDO:0000214 rice Pythium water-mold fungal disease
PDO:0000270 maize Aspergillus minor ear rot fungal disease
PDO:0000090 pecky rice fungal disease
PDO:0000019 rice bacterial leaf streak disease
PDO:0000220 maize Sclerophthora brown stripe downy mildew fungal disease
PDO:0000007 rice viral disease
PDO:0000128 rice transitory yellowing viral disease
PDO:0000197 maize Physalospora ear rot fungal disease
PDO:0000131 rice tungro viral disease
PDO:0000081 rice fungal disease
PDO:0000080 rice water-mold fungal disease
PDO:0000213 rice Fusarium water-mold fungal disease
PDO:0000063 rice root rot fungal disease
PDO:0000235 maize Phaeosphaeria leaf spot fungal disease
PDO:0000014 rice bacterial blight disease
PDO:0000093 rice seedling blight fungal disease
PDO:0000193 maize Ascochyta minor leaf spot fungal disease
PDO:0000001 plant disease
PDO:0000237 maize Sphacelotheca head smut fungal disease
PDO:0000009 wheat fungal disease
PDO:0000121 rice black streak dwarf viral disease
PDO:0000149 maize bacterial stripe disease
PDO:0000185 maize foolish seedling fungal disease
PDO:0000198 maize Hormodendrum ear rot fungal disease
PDO:0000085 rice Curvularia seedling blight fungal disease

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.