Annotation of phenotypic diversity: decoupling data curation and ontology curation using Phenex

James P. Balhoff, Wasila M. Dahdul, Thomas Dececchi, Hilmar Lapp, Paula M. Mabee, Todd J. VisionJ. Biomed. Semant 2014 · DOI · OpenReview

Introduction

In evolutionary biology, researchers use character matrices to describe physical traits (phenotypes) across different species. To make this data useful for large-scale computational analysis, these descriptions must be linked to ontologies—standardized, machine-readable vocabularies. However, curators often face a significant bottleneck known as "ontology lag." When a curator encounters a trait that lacks a corresponding term in existing ontologies, they traditionally have to stop their work, submit a request, and wait for approval before continuing. Phenex is a desktop application designed to streamline this process by decoupling data curation from the slow pace of ontology development.

The Ontology Request Broker (ORB)

The core innovation of Phenex is the Ontology Request Broker (ORB). Integrated with the NCBO BioPortal, the ORB allows curators to request a "Provisional Term" directly within the application. This provides a temporary identifier that can be used immediately, preventing workflow interruptions.

The Phenex workflow: (A) Data annotation with provisional terms, (B) Ontology editing and term promotion, and (C) Automated data updates.

As illustrated in the workflow diagram, the system manages the lifecycle of these terms. Once a permanent ID is assigned by ontology editors, Phenex automatically migrates the data. When a file is reopened, the software checks for these updates and replaces provisional IDs with permanent ones, automating a maintenance task that was previously manual and error-prone.

Enhancing Collaboration and Quality Control

Phenex also addresses the social and technical challenges of collaborative research. Rather than forcing biologists to adopt developer-centric tools like Git, the authors optimized Phenex for "low-barrier" file-sharing services like Dropbox. By using the jpathwatch library to monitor for external changes and employing a "continual autosave" feature, the software minimizes data loss and helps resolve edit conflicts in shared environments.

Furthermore, the application includes a real-time AnnotationConsistencyChecker. This tool provides live feedback, flagging logical errors—such as using a relational quality on a single entity—as the curator works. This transforms the user interface into a training tool, helping researchers learn complex annotation standards like the Entity-Quality (EQ) model through immediate, actionable feedback.

Conclusion and Future Work

Developed for and tested by the Phenoscape project, Phenex has demonstrated that allowing for asynchronous work significantly improves curation efficiency. By meeting researchers where they are and providing real-time guidance, the software lowers the barrier to high-quality semantic annotation. Future work will focus on supporting more complex multi-stage approval workflows and allowing consistency rules to be defined declaratively, enabling non-programmers to customize quality control checks for different biological domains.

Summary updated

Abstract

Phenex ( http://phenex.phenoscape.org/ ) is a desktop application for semantically annotating the phenotypic character matrix datasets common in evolutionary biology. Since its initial publication, we have added new features that address several major bottlenecks in the efficiency of the phenotype curation process: allowing curators during the data curation phase to provisionally request terms that are not yet available from a relevant ontology; supporting quality control against annotation guidelines to reduce later manual review and revision; and enabling the sharing of files for collaboration among curators. We decoupled data annotation from ontology development by creating an Ontology Request Broker (ORB) within Phenex. Curators can use the ORB to request a provisional term for use in data annotation; the provisional term can be automatically replaced with a permanent identifier once the term is added to an ontology. We added a set of annotation consistency checks to prevent common curation errors, reducing the need for later correction. We facilitated collaborative editing by improving the reliability of Phenex when used with online folder sharing services, via file change monitoring and continual autosave. With the addition of these new features, and in particular the Ontology Request Broker, Phenex users have been able to focus more effectively on data annotation. Phenoscape curators using Phenex have reported a smoother annotation workflow, with much reduced interruptions from ontology maintenance and file management issues.
BibTeX
@article{balhoff2014annotation,
  author = {James P. Balhoff and Wasila M. Dahdul and Thomas Dececchi and Hilmar Lapp and Paula M. Mabee and Todd J. Vision},
  title = {{Annotation of phenotypic diversity: decoupling data curation and ontology curation using Phenex}},
  journal = {J. Biomed. Semant.},
  year = {2014},
  doi = {10.1186/2041-1480-5-45},
}
Figure