Closed preecej closed 6 years ago
In the interim, I will be removing the BAR service option from the interface.
BAR changed the format of their service-delivered data to send UniProt IDs. We are now able to digest their data via the IntAct PSICQUIC registry.
My local Reactome environment hosts its own web ContentService/. That service calls PSICQUIC to get a URL registry of available interaction data services, including BAR. Using the resulting provider URL, the local service makes another call to retrieve data for given accession ids at given resources.
This entire process returns results for IntAct, but not for BAR, but I can't quite see all of the data interactions. BAR gives good results directly via HTTP, so I'm not sure what is going on.
Circadian rhythm example for AT1G22770: http://plantreactomedev.oicr.on.ca/PathwayBrowser/#/R-ATH-8933811&SEL=R-ATH-8933813&DTAB=MT
Local calls:
Remote, direct calls (both return several results):
I can't figure out how to see inside the local calls to know if the remote, wrappered BAR calls are incorrectly formatted, even with browser tracing.