Difference between revisions of "ProtegeDesktopUserDocs"

From Protege Wiki
Jump to: navigation, search
(Bugs & feature requests)
Line 15: Line 15:
 
=== Bugs & feature requests ===
 
=== Bugs & feature requests ===
  
Before you report a feature request or potential bug, check the lists below to ensure it hasn't already been reported. If the item is not currently open or you have further information or a question about an existing item, please post a message on the [http://mailman.stanford.edu/mailman/listinfo/p4-feedback Protege 4 mailing list].  Give as much detail as possible (including examples or ontologies if possible) as this will help us track things down more quickly.
+
Before you report a bug or feature request, check the lists below to ensure it hasn't already been reported. If the item is not currently open or you have further information or a question about an existing item, please post a message on the [http://mailman.stanford.edu/mailman/listinfo/protege-user protege-user mailing list].  Give as much detail as possible (including examples or ontologies if possible) as this will help us track things down more quickly.
 +
 
 +
Current GitHub issue tracker: https://github.com/protegeproject/protege/issues?state=open
 +
 
 +
Old GForge bug and feature request trackers (no longer in active use):
  
 
* [https://bmir-gforge.stanford.edu/gf/project/owleditor/tracker/?action=TrackerItemBrowse&tracker_id=121 Feature request tracker] - a searchable list of features that have been requested (and implemented)
 
* [https://bmir-gforge.stanford.edu/gf/project/owleditor/tracker/?action=TrackerItemBrowse&tracker_id=121 Feature request tracker] - a searchable list of features that have been requested (and implemented)
 
 
* [https://bmir-gforge.stanford.edu/gf/project/owleditor/tracker/?action=TrackerItemBrowse&tracker_id=118 Bugtracker] - a searchable list of reported and resolved bugs
 
* [https://bmir-gforge.stanford.edu/gf/project/owleditor/tracker/?action=TrackerItemBrowse&tracker_id=118 Bugtracker] - a searchable list of reported and resolved bugs
  

Revision as of 18:28, February 6, 2014

Protege Desktop User Documentation

This page is the official documentation home for the Protege Desktop application, versions 4.x and higher.



Build status & release notes

The latest Protege Desktop build is the 4.3 release from April 15, 2013.

To help you decide whether to update, please refer to our complete list of release notes for prior versions of Protege.

Bugs & feature requests

Before you report a bug or feature request, check the lists below to ensure it hasn't already been reported. If the item is not currently open or you have further information or a question about an existing item, please post a message on the protege-user mailing list. Give as much detail as possible (including examples or ontologies if possible) as this will help us track things down more quickly.

Current GitHub issue tracker: https://github.com/protegeproject/protege/issues?state=open

Old GForge bug and feature request trackers (no longer in active use):

Frequently asked questions

We've put together a wiki page to answer the most commonly asked questions about Protege Desktop.

Getting started / tutorials

Editor features

Advanced features

Further setup / configuration

Plugins

Finding plug-ins

  • From build 104 P4 will find plugins and updates for you. See our Auto Update page.
  • Plugins for Protege 4.x OWL editor - the list of "Compatible Plugins" on this page is the result of a semantic query that gathers all plug-ins that have declared themselves compatible with the 4.x version of the Protege-OWL editor.
  • CO-ODE Protege 4.x Plugins - the CO-ODE group at the University of Manchester is the biggest contributor of plug-ins to the Protege-OWL editor. This is a good place to go to download early releases and source code for CO-ODE developed plug-ins.

Advertising plug-ins

If you have developed a plug-in for Protege-OWL 4.x and you would like to contribute it to the community, please see contributing plugins.

Contributing

Please see this page for details on how you can contribute.