Difference between revisions of "Neglected items"

From phenoscape
(Polymorphic matrix states in Phenex)
(Search for phenotypes in web interface via anatomy part_of)
Line 12: Line 12:
  
 
===Search for phenotypes in web interface via anatomy part_of===
 
===Search for phenotypes in web interface via anatomy part_of===
 +
Currently the web interface and data service provide results using the is_a subsumption relation - searching for "bone" will return annotations to any particular bone.  However we have not added a way to search for annotations to parts of some anatomical entity.  This should already be supported by OBD - needs to be added to our query services and web interface.
 +
 
===Employing homology statements in data queries (via reasoning?)===
 
===Employing homology statements in data queries (via reasoning?)===
 
==="Systematic character" PATO subset===
 
==="Systematic character" PATO subset===
  
 
[[Category:Informatics]]
 
[[Category:Informatics]]

Revision as of 21:00, 19 February 2009

This is a list of various items that have come up at meetings and other discussions, which don't seem to have made it onto any development plan or roadmap.

Measurement value literals in OBD (including ranges)

Phenotypes that include a measurement are not stored without the measurement in OBD, for example "count" or "length" phenotypes. These values need to be imported and provided to the web interface.

Measurement input interface supporting ranges for Phenex

Phenex supports input of a single number for measurements. Many publications provide ranges, which may or may not be bounded on both sides ("5-10", "more than 7").

Fully automated dataloader script

The dataloader should run in an automated way on a server. It should be easy to install and run from any computer. I know Cartik is working on this but I'm not sure it's on a roadmap. --jim 15:53, 19 February 2009 (EST)

Polymorphic matrix states in Phenex

Data matrices sometimes use the NEXUS format for specifying polymorphic states. NeXML supports polymorphic state assignments, but Phenex doesn't provide any facilities for working with polymorphic states.

Search for phenotypes in web interface via anatomy part_of

Currently the web interface and data service provide results using the is_a subsumption relation - searching for "bone" will return annotations to any particular bone. However we have not added a way to search for annotations to parts of some anatomical entity. This should already be supported by OBD - needs to be added to our query services and web interface.

Employing homology statements in data queries (via reasoning?)

"Systematic character" PATO subset