diff options
| author | Saunak Sen | 2023-06-28 10:38:06 -0500 |
|---|---|---|
| committer | GitHub | 2023-06-28 10:38:06 -0500 |
| commit | fd795503106c223a228e68fe472f03e48cd85681 (patch) | |
| tree | 5591ddbe93364405af8901b9fa134391e7455799 | |
| parent | be807e5399c7f34a6457a32a87b13d489a4f02d0 (diff) | |
| download | gn-docs-fd795503106c223a228e68fe472f03e48cd85681.tar.gz | |
Update questions-to-ask-GN.md
Added note on trait metadata.
| -rw-r--r-- | api/questions-to-ask-GN.md | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/api/questions-to-ask-GN.md b/api/questions-to-ask-GN.md index c35b4ae..d61ca9a 100644 --- a/api/questions-to-ask-GN.md +++ b/api/questions-to-ask-GN.md @@ -137,6 +137,9 @@ Return trait metadata such as probeset info or other "trait covariates" for the * Current: through SPARQL * Proposed: https://genenetwork.org/api/v_pre1/mouse/bxd/HC_M2_0606_P/1436869_at +> The above scheme works for single features, but most analysis involves analyzing the "omid" data in its entirety. For those cases, making repeated calls is cumbersome. It would be better to have a single call that will return all thetrait covariates at once. For gene expression we will want the gene name, and genomic position at the least. We will also want free text metadata that explan what the probesets are, eg. what database/version is used for the gene names or probesets, preprocessing steps, authors/reference and experimental protocols. + + ## List datasets ``` |