OPS example workflow in the GitHub installation guide

[NuriaQueralt]

Hi,

i ran the workflow and the following error arised when executing the OPS-JSON node:

ERROR OPS_JSON 0:70 Execute failed: ("NullPointerException"): null

cheers,
n

[danidi]

Hi!
It seems that the OPS_Swagger node lost the information which API call to run. You need to reconfigure the OPS_Swagger node, and select the "target class pharmacology list" API call. But it doesn't seem to be a very good example for a workflow anyways, I'll try to replace it with something better.

[danidi]

When loading the workflow, it gives the following warning: String for key "templateSelectionCopy" not found. Maybe that causes the issue.

[NuriaQueralt]

@danidi now works very well!!! thank you!!!

[AslanDevbrat]

@danidi hello I tried your way but now iI am getting empty results? And this warning
WARN OPS_JSON 3:70 Node created empty data tables on all out-ports.

[danidi]

Hi @AslanDevbrat,
I fear the Open PHACTS Discovery platform was taken offline in 2019, so this is unfortunately no longer working. (see https://www.openphactsfoundation.org/open-phacts-platform-update-march-2019/)

[AslanDevbrat]

@danidi So is there a way to use that knime node?

[egonw]

Basically, no. The service behind it is offline, so there is nothing to give the node any content.

I would recommend replacing the node with calls to the databases that were integrated in the Open PHACTS platform directly, and use KNIME to integrate that data.

[danidi]

Theoretically, the Ops_Swagger node was developed to work with any swagger configuration, so it could theoretically be used with others as well. But as @egonw mentioned, you could access other data sources directly (with the GET Request nodes), and interpret json data with the JSON Path node.