-
Notifications
You must be signed in to change notification settings - Fork 11
Open
Labels
bugSomething isn't workingSomething isn't working
Description
When we updated PFOCR result-augmentation #876 #847, we accidentally turned on this feature for team and smartapi endpoints.
Those endpoints are only used when BTE is being used as a KP (Service Provider's TRAPI wrapper). So the users don't need PFOCR result-augmentation and it's just wasted extra work/time for BTE.
Example: send this query to BTE's Service Provider endpoint (v1/team/Service Provider/query) or Text-Mining-Targeted thru BTE (v1/smartapi/978fe380a147a8641caf72320862697b/query).
The response will have "pfocr" result-augmentation.
Query: decreases MYC
{
"message": {
"query_graph": {
"nodes": {
"creativeQuerySubject": {
"categories":["biolink:ChemicalEntity"]
},
"creativeQueryObject": {
"ids":["NCBIGene:4609"],
"categories":["biolink:Gene", "biolink:Protein"]
}
},
"edges": {
"eA": {
"subject": "creativeQuerySubject",
"object": "creativeQueryObject",
"predicates": ["biolink:affects"],
"qualifier_constraints": [
{
"qualifier_set": [
{
"qualifier_type_id": "biolink:object_direction_qualifier",
"qualifier_value": "decreased"
},
{
"qualifier_type_id": "biolink:object_aspect_qualifier",
"qualifier_value": "activity_or_abundance"
}
]
}
]
}
}
}
}
}
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working