aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorrupertoverall2023-06-28 13:45:00 +0200
committerGitHub2023-06-28 13:45:00 +0200
commit0e5094c513ad0c65616f97b804f96406bab92d8d (patch)
tree1ab0d05ce61d6525e7bd00693f1792a7babc49f4
parentd0d39ba5d598331342b144d833724cf296c07c26 (diff)
downloadgn-docs-0e5094c513ad0c65616f97b804f96406bab92d8d.tar.gz
Add note on URL keywords.
-rw-r--r--api/questions-to-ask-GN.md1
1 files changed, 1 insertions, 0 deletions
diff --git a/api/questions-to-ask-GN.md b/api/questions-to-ask-GN.md
index 15d06d1..254fb82 100644
--- a/api/questions-to-ask-GN.md
+++ b/api/questions-to-ask-GN.md
@@ -70,6 +70,7 @@ curl -s http://genenetwork.org/api/v_pre1/groups/mouse |jq '.[8:10]' -M
}
]
```
+**Note: I wonder if the key "Short_Abbreviation" could have a different name. This is the keyword that users need in order to construct the URLs. I guess most people would be looking for something in the metadata a bit more 'important'-sounding: like "Key" or "Keyword" or even "Title" ("ID" is already used by a database index - although this value can't be used in the URLs). The name of the key required for URL-building is also different for each hierarchy level ("Name" in most cases (although sometimes all lowercase) but "id" for phenotype traits for example).**
## Return cross info