-
Notifications
You must be signed in to change notification settings - Fork 9
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
handling ID-prefixes in BTE in a consistent, straightforward way #591
Comments
Also a consideration: do pending APIs (and Multiomics / Text-mining ones) need to keep both a ontology-specific field (where the value is probably not prefixed) and a general "ID" field for nodes? Like here (the id vs HP field):
|
BTE previously automatically added the prefix to RHEA IDs, and at some point, stopped (this is the confusing part!) I only noticed today while checking on another issue (primary knowledge source). And I tested / made this commit to add the needed prefix for operations using RHEA IDs as input: NCATS-Tangerine/translator-api-registry@d78fd51 I don't know the scope of this issue without doing a review of all the x-bte operations...my own musings below:
|
Noticed issue with GO prefixes and fixed by ensuring prefix is added to sub-queries NCATS-Tangerine/translator-api-registry@3703119 |
Noticed issue with MP prefix and fixed by ensuring prefix is added to sub-queries NCATS-Tangerine/translator-api-registry@72748a1 |
BTE currently:
This can easily lead to bugs and is confusing. With the current big code update, it's not clear if there are some bugs / unexpected behavior with ID-prefixes....which prompted the discussion + writing this issue.
2023-03-22 discussions in group meeting and afterwards:
queryInputs
), BTE should remove the prefix from all ID-namespaces (rather than keeping prefixes for some)Seems like a design decision between @tokebe and me, although @andrewsu and @newgene can weigh in.
Notes:
The text was updated successfully, but these errors were encountered: