Difference between revisions of "EQ Editor"

From phenoscape
(Detailed steps)
(Detailed steps)
Line 42: Line 42:
====Detailed steps====
====Detailed steps====
One possible workflow would be a curator dealing with a single publication during a session of working with the EQ Editor.  Steps might be:
The standard workflow would be a curator dealing with a single publication during a session of working with the EQ Editor.  Steps might be:
# Create a new EQ Editor document.
# Create a new EQ Editor document.

Revision as of 16:25, 13 June 2007

EQ Editor requirements

The EQ Editor will be used by curators to annotate phenotypic descriptions of Ostariophysi using EQ syntax and ontologies.

The curator will use the EQ Editor to code phenotypic data from an existing publication into the EQ format. This data consists of descriptions of character state values for corresponding species (or, more precisely, specimens). A published character state description may contain: the species or higher taxonomic specification, a textual description of the character state value, reference to a voucher specimen for this description, an image showing the character.

Data Model

The following are essential data elements to be captured by the EQ Editor for each character state description (format is in parentheses). There is some additional discussion of how to treat character definitions at "EQ for character matrices".

  • species name (free text until taxonomic ontology is available?)
  • voucher specimen lot ID (format?)
  • specimen count
  • specimen preparation (cleared and stained, etc.)
  • EQ statement for character state (Q should be a value)
    • E from fish anatomy (ontology ID)
    • Q from PATO (ontology ID)
    • measurement (number) - used if Q is an attribute suitable for measurement (e.g. "length")
    • measurement unit (units ontology ID)
    • E2 from fish anatomy (if Q is descendant of "relational quality of continuant" or "relational quality of occurrent") (ontology ID)
  • original description (free text)
  • publication/citation (DOI? older publications don't have DOI, do they? Another possibility is SICI)
  • image or URL for image (image data or URL)
  • evidence statement (confirmation by taxonomic expert, etc.) - this requires discussion


Sources of data

The publication being coded may contain data in one of a few different formats. The given data format may suggest its own style of workflow. These publication types include 3 main forms:

  1. Description of many characters for many species and higher taxonomic levels; no character-by-taxon matrix published.
  2. A data matrix with multiple species and multiple characters. There is a character state value for each cell in this matrix.
  3. A single species description of values for many characters.
  4. Description of a single character for many species (perhaps less common than the other formats?). If focusing on a single character the data may come from multiple publications.

It seems like scenarios 2 and 3 can be treated as special cases of scenario 1. For each character, an interface is required for choosing the Entity and Quality from their respective ontologies, and entering free text such as the original character descriptions, as well as other relevant data.

Since many species will share common values of character states, the interface should have a way of choosing previously entered character states, perhaps by separately enumerating the possible values for a character. EQ coding will be performed at the level of character states, but there may be a facility for dynamically viewing entries in a character matrix format. See "EQ for character matrices" for a discussion - at the June 5 PI meeting we decided to work with only character states.

Detailed steps

The standard workflow would be a curator dealing with a single publication during a session of working with the EQ Editor. Steps might be:

  1. Create a new EQ Editor document.
  2. Enter document-wide data:
    1. publication information (author, title, journal)
    2. list of specimens - input specimen info and choose taxon from taxonomic ontology for each one
  3. Begin making character state annotations:
    1. Select a specimen or multiple specimens to which this character state applies (there should be facilities for efficiently choosing sets of specimens/taxa)
    2. Create a new EQ statement
    3. Choose Entity from anatomy ontology
    4. Choose Quality from PATO (usually a Value term)
    5. If the Quality is an Attribute term (such as "length"), enter a measurement and its units
    6. If the Quality is relational, enter a second Entity from the anatomy ontology
  4. At any point, the curator can save the current work to a document (or database). We should investigate requirements regarding the document format (relationship to PhenoXML/PhenoSyntax, NEXUS, etc.), which will depend on the detailed data model.


  • What should the user be able to do if there is not an appropriate term in the ontology?
  • What will be done (in the immediate term) with the annotations produced by the EQ Editor? Will they be stored in separate documents, or compiled into a central repository?
  • Is a "post-composition" capability required?
  • Need to add a button to say "Need a new term"

Features perhaps suited for EQSYTE

At the February 2007 PI meeting, some features of the workflow were discussed which may be most useful when the central database of character states is in place, such as:

  • see what is already present about a particular character or "similar" characters (based on related entities or qualities)
  • see what values have been previously assigned for a character (from other publications)
  • view conflicting character states from different publications, choose to keep both or reconcile


Some technology choices may figure into the application requirements, particularly if integration with another application or system is a desired feature. Possibilities include:

  • Implement EQ editing as a Mesquite plug-in, providing some additional interface to the character editing already in Mesquite. This would require extensions to the NEXUS format for storing ontology term information. Here is some more discussion on Mesquite.
  • Extending Phenote with any additional functionality that is required. Phenote is being actively developed by the model organism community, but deals with a list of unordered EQ statements rather than a species-by-character matrix. Here is some more discussion on Phenote.
  • Web-based application.
  • Components from all of the above.