Code Monkey home page Code Monkey logo

Comments (7)

newgene avatar newgene commented on June 22, 2024
  • need to consume new /meta_knowledge_graph endpoint to get the predicates information
  • update input query graph to use new v1.1 format (mostly change word to its plural)

from call-apis.js.

newgene avatar newgene commented on June 22, 2024

Can potentially test with this TRAPI v1.1 example:

http://smart-api.info/registry?q=305a2909830b776df7a02b7207e4acc5

e.g. this should work:

http://api.bte.ncats.io/v1/smartapi/305a2909830b776df7a02b7207e4acc5/meta_knowledge_graph

from call-apis.js.

newgene avatar newgene commented on June 22, 2024

Also test an actual TRAPI query to a specific http://api.bte.ncats.io/v1/smartapi/<api_id>/query URL to confirm it's working.

from call-apis.js.

marcodarko avatar marcodarko commented on June 22, 2024

Update:
OpenPredict (trapi 1.1.0) works for testing this endpoint:
https://api.bte.ncats.io/v1/smartapi/e9f69b81e755e163fdf6c41a2b5e07c0/meta_knowledge_graph

However, the previous test url provided uses Automat KEGG (trapi 1.1.0) and it does not work (but should), it appears that this API is not making it into the specs file collected by our cron job that looks at the registry. We need to investigate why that is.

from call-apis.js.

marcodarko avatar marcodarko commented on June 22, 2024

@andrewsu @newgene I think the reason that API (Automat KEGG ) doesn't appear is because they have "/1.1/meta_knowledge_graph" instead of "/meta_knowledge_graph" thus failing our check and not being included. What should we do about it?

from call-apis.js.

marcodarko avatar marcodarko commented on June 22, 2024

*Note on why some of these APIs don't work for this endpoint: /v1/<ID>/meta_knowledge_graph
This endpoint will ultimately look through the specs.json (response from a query to SmartAPI for all translator APIs) for this API and look in the paths for a property "x-bte-kgs-operations" in them, if that is not found the operations returned will be 0 and that triggers an "error" on our side but it simply means that nothing was found. As I understand, this was the old way to specify operations now moved to its own endpoint: /meta_knowledge_graph . How do we want to handle such cases? or is this endpoint going to be deprecated at some point?

from call-apis.js.

colleenXu avatar colleenXu commented on June 22, 2024

Can this issue be closed? I have another one currently open that's related...biothings/biothings_explorer#269

from call-apis.js.

Related Issues (12)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.