-
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
TRAPI 1.5: support source_record_urls #803
Comments
For development, use these yamls:
We'll add overrides to these yamls when we deploy this feature. And WE ARE WAITING AND WON'T MERGE the SmartAPI yaml PRs until AFTER this feature is deployed to Prod: After these SmartAPI yaml PRs are merged, overrides to this branch's yamls can be removed from BTE. |
@colleenXu Do you have any example queries that would hit BindingDB and likely return |
@tokebe Sorry for seeing this late >.< Query for "protein-ligand" operation
Start with CD47 (aka UniProtKB:Q08722 / NCBIGene:961)
Currently this is one of the edges:
With the different handling for
Query for "ligand-protein" operation
Start with chemical INCHIKEY:NZLXOECMDRNZDN-GUYCJALGSA-N
Currently there's only 1 edge
With the different handling for
|
I've updated my comment above with all of the adjusted SmartAPI yamls for this feature. We'll add overrides to these yamls for this feature later. I didn't adjust the MyGene reverse operation ( I don't think this is a blocking issue for this feature though. |
I've added a PR in bte-server to add the overrides needed biothings/bte-server#25 Also: could we remove the source_record_urls field when it has no value? Right now it's in every primary knowledge source object, when it'll only be filled in a few cases. (based on a quick look) |
Latest commit should fix this. |
Note: we can keep the override to BioThings rare-source, but I reverted the branch's yaml so it's using ref_url (commit). AKA it's not using this feature anymore. These links provide related literature info, but don't explain where the original association came from (GARD). So they should be edge-attributes |
We'd like to use However, we needed to adjust our "unique edge hashing" so a TRAPI edge could have multiple values in the We have two code changes that have been deployed to dev/CI -> and we want to patch to Test where the rest of the code for this feature is:
|
for source_record_urls issue. see this post and ones after it https://github.com/biothings/biothings_explorer/issues/803\#issuecomment-2060511039
The BTE code + old overrides (having ncats_rare_source rather than pfocr) were deployed to Prod as part of the Octopus release. I tested and it's live. However, the latest PFOCR stuff is only on dev/CI right now. I think we want to get this in as a patch to Test/Prod. So I havne't merged the SmartAPI yaml PR yet, or added the override removal to the chore |
See #811 (comment) for details on how we're going to remove the overrides/deploy the PFOCR stuff. |
Related PRs deployed to Prod. |
I've updated BioThings PFOCR x-bte annotation to use this feature. |
TRAPI 1.5 has updated documentation for "references", that says "urls to an external page for the association" should be put into the KG Edge's sources (in the source_record_urls field for one of the source objects), rather than the
biolink:publications
edge-attribute.We've gotten confirmation from the UI team that they're aware of this and plan to add support for it (Translator Slack link).
My implementation idea: use a different keyword in the response-mapping
ref_url
to tell BTE to add the field's values to thebiolink:publications
edge-attribute (previous issue)source_url
to tell BTE to use the field's values in the sources"resource_role": "primary_knowledge_source"
)source_record_urls
and value is an array of strings (make 1-element arrays for single urls) from the mapped response field.We'd do this for:
BioThings rare-source (rare-source webpages; do special reverses so we can retrieve urls in both directions?)The text was updated successfully, but these errors were encountered: