`/meta_knowledge_graph` MetaEdge `knowledge_types` cannot be `lookup_and_score`?

[colleenXu]

@andrewsu @tokebe (Follow up on Andrew's Slack thread)

According to the current TRAPI spec, the /meta_knowledge_graph MetaEdges can only have the values lookup and/or inferred in their knowledge_types array.

But in the code we're deploying to address https://github.com/biothings/biothings_explorer/issues/485, we changed BTE-ARA's/meta_knowledge_graph response to use lookup_and_score (which is technically correct!). Note that the team-specific / api-specific endpoints still use lookup.

So....there's a question of what to do next:

• bring this up with the TRAPI group? (EDIT: asked in Translator Slack)
• change to use lookup for BTE-ARA's /meta_knowledge_graph endpoint? (Does this involve changing the SmartAPI yamls?)
• does this need to be a hotfix/patch to Test? It's not clear to me how urgent this is - since it only affects the ARA endpoint
• ~does Retriever also need adjusting?~ DONE: see Jackson's next post.

[tokebe]

Retriever has already been adjusted since it doesn't do scoring. This shouldn't be too involved to patch quickly, so I guess it's a matter of what the TRAPI group says.

[colleenXu]

We should change this to lookup, according to Eric Deutsch (TRAPI group, Translator Slack link).

While it doesn't seem to matter much, I imagine we don't want to push the use of lookup_and_score to Prod....so we'll want to make changes + deploy them up to Test in the next week or so? @tokebe

[colleenXu]

See https://github.com/biothings/bte-server/compare/c5aecdd860e4...397d8ac49567

Not sure of its deployment status right now

[colleenXu]

I double-checked and this is deployed on CI right now. But we want this to be deployed to all instances as a fix...