OBO-Edit 2.0 Official Release Available for download
Downloading OBO-Edit 2.0
The latest releases in the 2.x series can be downloaded here:
OBO-Edit 2.0 RELEASE NOTES
What's New in OBO-Edit 2
- Refreshed Look
- General Improvements to existing components
- Updated Documentation and Installer
- Menu layout changes
- New components: Configuration Manager, Ontology Change Tracker, OBO Merge Interface, Term Image Display Panel
- New Rule Based Reasoner
- Faster Search and Reasoning capability
- Optimized cross-product editing through the Text Editor
- Functionality to assert implied links and remove redundant links
- Parent Editor functionality to display immediate parents of a sub-selection term and highlight intersection terms.
- Improved Searching and Filtering interface
- I/O and command-line options
- Term and Link renderer's for better data representation and analysis
- Updated standard Gene Ontology dictionary
- Custom user defined dictionary
- Graph Editor with selection, editing and zoom functionality
- Improved autocommit and autosave features
- Components for Advanced Users - Cross-Product Matrix Editor, Intersection Editor, Semantic Parser Manager
- User dictionary save and persistence between sessions
- "Undo" action in Text Editor not working unless focus changes to another term
- Handling of unrecognized and dangling relations
- Over zealous pending edits warning
- Searching terms with implied links through the Link Search Panel (temporary fix available for users willing to compromise on speed and permanent fix available in next release onwards)
- Graph Editor issues
- Buggy component resize behavior
===Importing Settings from previous versions===< Settings from OBO-Edit 1 or 2.0 beta versions are located in the configuration folder found in the user's home directory. You can import your perspective and layout settings from previous versions. Config folder naming convention is consistent with the version. Config files can also be reset when required through the Configuration Manager.
Effective bug reports are the most likely to be fixed. These guidelines explain how to write such reports.
* Reproduce your bug using the most recent release, to see weather it has already been fixed.
* Be precise and clear - explain the behavior so others can reproduce the bug
* Limit bugs to one per report
* No bug is too trivial to report - small bugs may hide big bugs
* Clearly separate fact from speculation
* Search the Bugs Tracker to check weather your bug has already been reported
Reporting a New Bug
- If you have reproduced a bug in the most recent release and no-one else appears to have reported it, then report it on our sourceforge bug tracker:
Frequently Asked Questions
1. What can I do to help?
We need help from the community to test and provide as much feedback as possible to make OBO-Edit even better.
Ways in which you can help:
* Participate in OBO-Edit Working Group Meetings held every Tuesday at 9.30am PST over webex and conference call.
* Join the OBO-Edit Working Group sourceforge mailing list:
* Program or Report New Features - Let us know your ideas for new features or how we can improve existing features.
* Report Bugs
* Add Documentation
* Write Tutorials and put them up on the OBO-Edit wiki page
* Help others learn to use OBO-Edit, etc.
2. Where can I find the source code?
3. Why haven't you responded to the mail I sent you?
The probability of your question getting answered quickly is the highest when you write to the OBO-Edit Working Group Sourceforge Mailing list:
Refer Troubleshooting section in the User Guide
Other Resources and Links
The following resources contain useful information about OBO-Edit
- OBO-Edit website: http://oboedit.org/
Our website is currently not up-to-date as our developer did not find any free time to look at it before official 2.0 release. The website is being exported to a new faster server and the content will be updated as soon as thats done.
- OBO-Edit Wiki: http://wiki.geneontology.org/index.php/OBO-Edit
Visit us here to stay up to date with whats going on, important links and whats going on.