I agree, that sounds like a good goal. What I’m now thinking about is how to get to a path to deliver something like that.
We plan our development roadmap quarterly, and while we can often squeeze in bug fixes and small changes in when needed, adding this as described wouldn’t be small. As a result, this is in the queue to be scheduled, and does not yet have any ETA.
Things that I can think would be easier given where we are today:
We have stored in the database the top 100 correlations between several datasets stored in a database. We could add a simple API which will fetch the top 100 correlates for a set of genes. However, you won’t get more than the top 100 and you won’t get a p-value because it’s simply not already stored in the DB.
I could share the python code that the portal uses to compute large tables of correlations from our published files. This would hopefully allow one to compute any correlations you want, but it would require one to be comfortable with python.
I think the original suggestion sounds like a capability that I think people would find useful, but it’ll require making a few changes to implement, and therefore won’t be something that we’ll be able to get to for a while.
Would one of the two “easy” options I listed be a worthwhile short-term substitute?