This issue is to report a need for the WFR to support a query_options operation with kp_timeout and approved_threshold parameters. Specifically, development and testing of the TCDC CQS Path A query (https://github.com/NCATSTranslator/Clinical-Data-Committee-Tracking-Voting/tree/main/GetCreative()_DrugDiscoveryRepurposing_RarePulmonaryDisease/Path_A) found that query results are cleaner when run through the ARAX UI than when submitted to the WFR. The reason is that ARAX allows users to specify timeout and threshold limits in the full TRAPI message, but the WFR only sends the message body to ARAS, so ARAX does not see the query_options request. The TCDC is thus requesting a fix to support the query_options operation with kp_timeout and approved_threshold parameters.
This issue is to report a need for the WFR to support a
query_optionsoperation withkp_timeoutandapproved_thresholdparameters. Specifically, development and testing of the TCDC CQS Path A query (https://github.com/NCATSTranslator/Clinical-Data-Committee-Tracking-Voting/tree/main/GetCreative()_DrugDiscoveryRepurposing_RarePulmonaryDisease/Path_A) found that query results are cleaner when run through the ARAX UI than when submitted to the WFR. The reason is that ARAX allows users to specify timeout and threshold limits in the full TRAPI message, but the WFR only sends the message body to ARAS, so ARAX does not see the query_options request. The TCDC is thus requesting a fix to support thequery_optionsoperation withkp_timeoutandapproved_thresholdparameters.