Chunlei Wu
Chunlei Wu
For example, https://docs.myvariant.info/en/latest/doc/release_changes.html#20200829, which is corresponding to builds: `warm_hg19_20200807_y1trd7tr` and `superhot_hg19_20200817_66idty4q`.
Right now we cannot do facets on "clinvar.rcv.clinical_significance", because it's indexed "text" type: http://myvariant.info/v1/query?q=chrom:22&size=0&facets=clinvar.rcv.clinical_significance We could index it as "keyword" so facets will work, but we cannot query this field...
VEP: http://uswest.ensembl.org/info/docs/tools/vep/index.html Similar to the SnpEff annotation we have already, VEP is a tool to compute variant impact.
These two variants are the same should be merged into one (with "CT" after "del"): http://myvariant.info/v1/variant/chr17:g.41276045_41276046delCT and http://myvariant.info/v1/variant/chr17:g.41276045_41276046del
>The Consensus CDS (CCDS) project is a collaborative effort to identify a core set of human and mouse protein coding regions that are consistently annotated and of high quality. The...
Currently, mygene.info doc has a static data source table: https://docs.mygene.info/en/latest/doc/data.html#data-sources We should modify it to use the same auto-generated data src table from other API docs, e.g. from MyVariant.info: https://docs.myvariant.info/en/latest/doc/data.html#data-sources...
We need to update https://docs.mygene.info for new features available at the production API, such as * accept json as the POST content-type * new query parameters available for each endpoint
A more "formal" solution to #42 and #7: * generate a JSON-schema style schema on the gene object * there could be two versions of schemas available: * one is...