-
Notifications
You must be signed in to change notification settings - Fork 11
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.
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
find/add non-Translator APIs to BTE #372
Comments
In parsing the smartapi registry for entries with
OpenTarget, ChEMBL, and RGD are worth looking into more on whether they should be included by default in the Code:
|
Notes:
I think we'd want to prioritize resources that have non-overlapping data w/ the BioThings APIs... In the config file, These apis are listed as being external
|
I think these are all resources that are already in Translator. But I think only people added to it can see this... I went through some of my bookmarks (my main folder for possible resources)....and I organized it into this. The questions are the stuff I haven't done systematically yet >.< Questions:
Other notes:
List of resources to review:
Less promising? |
other resources related to research issues (besides grantome.com):
|
Related: incorporating new biothings api: figuring out if x-bte can handle other query-language apis: creating biothings instances of new resources:
Side stuff... On updating what we already have:
On adding Translator APIs: |
Resources discussed during Feb relay this week:
|
biothings/pending.api#57 on evaluating an existing api, or making a new pending |
Discussion of CTD's API: https://suwulab.slack.com/archives/CC218TEKC/p1648008085792669?thread_ts=1647966388.829489&cid=CC218TEKC. Also updated the posts above for the issues in the pending repo. |
https://www.expasy.org/ there may be tools/APIs here? |
https://rampdb.nih.gov/about has an API with an OpenAPI v3 spec |
note that CIVIC is using a GraphQL API (can we handle this with OpenAPI v3 / x-bte annotation?)
|
RGD evaluationDoes this resource have structured info on relationships between biomedical stuff?
Potential value add:
Potential issues:
Are we allowed to use it?
Does this resource already have an api that is usable for x-bte annotation, or do we need to stand up a biothings api?
-MyGene.info had RGD at some point (not sure if it's still there) and NCBI gene had ids for RGD QTLs until about June of 2021 (many if not all NCBI gene ids for RGD QTLs were retired between January and June of 2021). -Not seeing any endpoint for mapping QTLs to genes (probably have to go about it using the endpoints for gene or qtl chromosome start and end points |
IUPHAR/BPS Guide to Pharmacology evaluationDoes this resource have structured info on relationships between biomedical stuff?
Potential value add:
Potential issues:
Are we allowed to use it?
Does this resource already have an api that is usable for x-bte annotation, or do we need to stand up a biothings api?
|
Note: DGIdb has an API but it takes names/symbols as input (not IDs…), and it doesn't have an OpenAPI spec. The "names, not ID" issue means we can't integrate that API into Translator / BTE well....we have to download the data and make a BioThings API instead... |
Collections of a lot of resources, most of which should have their own APIs:
|
Pasting an old note of mine:
|
Some data resource lists that could be helpful: |
food resources https://foodmetabolome.org/databases |
In #370, we analyzed the list of 46 APIs currently listed in the
config.js
file, summarized below. One of the things that jumped out at me is that all but five (bolded) are translator-associated APIs. One of the advantages of the BTE/SmartAPI approach is that, in theory, we can easily annotate APIs "in the wild" that we don't maintain. But to really demonstrate that, we need to increase the number of those "in the wild" APIs. This ticket is to track our identification/incorporation of such APIs, either by reviewing the existing SmartAPI registry for appropriate APIs that aren't yet in ourconfig.js
file, or by finding and registering new APIs.The text was updated successfully, but these errors were encountered: