Difference between revisions of "Neglected items"
From phenoscape
| Line 1: | Line 1: | ||
| − | This is 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. | + | 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)=== | ===Measurement value literals in OBD (including ranges)=== | ||
Revision as of 20:54, 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.
Contents
- 1 Measurement value literals in OBD (including ranges)
- 2 Measurement input interface for Phenex supporting ranges
- 3 Fully automated dataloader script
- 4 Polymorphic matrix states in Phenex
- 5 Search for phenotypes in web interface via anatomy part_of
- 6 Employing homology statements in data queries (via reasoning?)
- 7 "Systematic character" PATO subset
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 for Phenex supporting ranges
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)
