Since many users would search for the human ADME gene / protein, rather than the species-specific variant, the new DBs contain the homology mapping to their corresponding human variant:
Here species often show 1:N mappings (multiple variants to the human homolog), as modeler, I would use the sequence homology a kind of "propability" which variant to use to capture the AMDE compound liability for human ADME gene.
Can we add the HOMOLOGY_PERCENT name type as a new column to the expression window to enable this? Something like this:
What is you estimate on how much work would be needed to enable this?
Let me know if you find this helpful.
On another note, would it make sense to "cluster" the process related information into this database? e.g. expression values, tissue/location, concentration / protein amount, synthesis / turnover / half-life....
Dear @Yuri05 @msevestre , I'm working on a technical validation workflow for the new gene expression DBs https://github.com/Open-Systems-Pharmacology/Gene-Expression-Databases/releases/tag/v3.0.1
Since many users would search for the human ADME gene / protein, rather than the species-specific variant, the new DBs contain the homology mapping to their corresponding human variant:
Here species often show 1:N mappings (multiple variants to the human homolog), as modeler, I would use the sequence homology a kind of "propability" which variant to use to capture the AMDE compound liability for human ADME gene. Can we add the HOMOLOGY_PERCENT name type as a new column to the expression window to enable this? Something like this:
What is you estimate on how much work would be needed to enable this? Let me know if you find this helpful.
On another note, would it make sense to "cluster" the process related information into this database? e.g. expression values, tissue/location, concentration / protein amount, synthesis / turnover / half-life....