Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue #113: Strongly recommend ensembl gene ID in 1.1 #143

Merged
merged 2 commits into from
Sep 1, 2017
Merged

Issue #113: Strongly recommend ensembl gene ID in 1.1 #143

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
fb30128
Update search-api.md
fschiettecatte Aug 5, 2017
e856d90
Update search-api.md
fschiettecatte Aug 8, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions search-api.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -191,9 +191,10 @@ After receiving a request, the remote server can respond in one of two ways:
* Is a **list of candidate causal genes and variants** described by:
* `gene`: (***mandatory***)
* `id`: A gene symbol or identifier (***mandatory***):
* `<gene symbol>` from the [HGNC database](http://www.genenames.org/) OR
* `<ensembl gene ID>` OR
* `<entrez gene ID>`
* `<entrez gene ID>` OR
* `<gene symbol>` from the [HGNC database](http://www.genenames.org/)
* The use of ensembl gene ID is ***strongly*** encouraged and will become mandatory in 2.0
* `variant` (*optional*): the specific variant
* `assembly`: reference assembly identifier, including patch number if relevant, of the form: `<assembly>[.<patch>]` (***mandatory*** if `variant` is provided)
* example valid values: `"NCBI36"`, `"GRCh37"`, `"GRCh37.p13"`, `"GRCh38"`, `"GRCh38.p1"`
Expand Down