-
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
RaMP: process of x-bte annotation + adding to BTE #705
Comments
Discussion topics: 1: current BTE has buggy behavior when parsing the output of this API: see here, and here. I therefore suggest NOT "fully deploying" this as a KP used by BTE and others (by adding to BTE's config list) until this has been addressed
2: writing up all the possible x-bte annotation (depends on 1)
3: discussing with the RaMP team: what SmartAPI yaml file to have x-bte annotations on and register in the SmartAPI registry (including what repo).
|
Updated notes:
|
Found some info on ID namespaces available: https://github.com/ncats/RaMP-DB?tab=readme-ov-file#important-notes |
Opening an issue here to better track the status of this effort. In the future, when data resources reach the x-bte annotation part, we'll want to open an issue in this repo for tracking.
Previous discussion in biothings/pending.api#69, with the currently-relevant comments starting biothings/pending.api#69 (comment)
Related to post-processing and JQ-related work, which is described in biothings/pending.api#69 (comment) and #489 (comment)
I'm writing x-bte annotation in my fork: https://github.com/colleenXu/RaMP-Client/blob/x-bte-annotation/libs/features/ramp/ramp-api/src/assets/data/ramp_openapi_with_extensions.yml
That file is registered https://smart-api.info/registry?q=ac9c2ad11c5c442a1a1271223468ced1
The text was updated successfully, but these errors were encountered: