The Evidence & Conclusion Ontology is developed on GitHub. If you are interested in getting involved and want to contribute to the project, we encourage you to contact us.

Download

Direct download of the ontology with a web browser:

https://github.com/evidenceontology/evidenceontology

You may download ECO ontology files using a web browser. For the most recent release, navigate to the GitHub repository and click on eco.obo or eco.owl. The full file will load into your browser. Next, click on “Raw” on the upper right side of the page and save according to your preferred method.

Raw files are here:

https://raw.githubusercontent.com/evidenceontology/evidenceontology/master/eco.obo https://raw.githubusercontent.com/evidenceontology/evidenceontology/master/eco.owl

Command-line access for downloading the ontology

For those familiar with the command line, please download ECO from our GitHub repository using git:

git clone https://github.com/evidenceontology/evidenceontology.git

Complete instructions are here: https://github.com/evidenceontology/evidenceontology/tree/master/editors

Releases

Here you can download the latest OWL and OBO release. Historical releases are also available for download.

v2018-09-14 latest release

Notes
Contains final updates to ensure all classes are defined.

v2018-09-03

Notes
Provides fix for #175

v2018-08-21

Notes
Includes addition of `eco-base` and `eco-basic` products

See more releases

v2018-05-22

Notes
2018-05-22 release - fixes placement of `molecular_function`.


v2018-05-18

Notes
May 2018 release updates:
* Add over 500 "used in manual" and "used in automatic" terms
* Remove "experimental genomic evidence" and recategorize children
* Clean import files and ontology metadata
* Clarify children of "author statement"


v2018-04-06

Notes
April 2018 release updates:
* Merging of the 'bioassays' branch for review of 'biological assay evidence'
* Addition of OBI mapping logic to children of 'cell-based assay evidence'
* Addition of 68 OMP terms
* Addition of exact synonyms of terms as broad synonyms of their manual assertion children (see #163)


v2018-03-02

Notes
release 2018-03-02
* Merges imported terms from OBI & GO
* Some logic added under 'transcript expression evidence'


v2018-01-09

Notes
Release 2018-01-09 changes:
* Addition of ECO:0007008 'radioligand binding assay evidence'


v2017-12-02

Notes
Release 2017-12-02

Noteable changes:
- Merged lost alt IDs from initial GitHub release
- Add definitions for terms missing definitions
- Ensure standardized definitions for 99.99% of terms


v2017-11-03

Notes
Nov 2017 release.
Add provenance for SIB terms.


v2017-10-06

Notes
Release 2017-10-06

Update of makefile
Addition of new HTP GO code mappings


v2017-09-21

Notes
Unscheduled release to fix go_groupings
2017-09-21


v2017-08-09

Notes
Release 2017-08-09

Fix namespace character change from "/" to "#"


v2017-08-04

Notes
release 2017-08-04


v2017-07-19

Notes
Changes:
* Revert back to dbxrefs for 'definition source'
* Revert back to created_by instead of 'term editor'


v2017-07-10

Notes
**Changes**
* Fixed an issue with escaped colons in the eco.obo file


v2017-07-07

Notes
release 2017-07-07


v2017-06-02

Notes
release 2017-06-02


v2017-05-05

Notes
release v2017-05-05


v2017-04-07

Notes
ECO has been released into the public domain under CC0.


v2017-03-28

Notes
release 2017-03-28


v2017-03-03

Notes
v2017-03-03
release 2017-03-03


v2017-02-03

Notes
v2017-02-03

release 2017-02-03


v2017-01-06

Notes
v2017-01-06

release 2017-01-06


v2016-12-02

Notes
v2016-12-02

release 2016-12-02


v2016-11-04

Notes
None recorded


v2016-10-10

Notes
None recorded


v2016-10-07

Notes
None recorded


v2016-09-16

Notes
None recorded


Develop

Command-line, GUI & IDE access for developers

If you are a developer already contributing to the ECO project, see complete instructions for checking out and editing here: https://github.com/evidenceontology/evidenceontology/tree/master/editors

If you are not a developer but would like to contribute, we’d love to hear from you! Please either submit a tracker issue request or contact the ECO team.