BTE queries focus on making API calls with entity identifiers (or entity types) as the primary inputs. However, some APIs accept (or require) secondary parameters that define an analysis. For example, the /lilgim/query API accepts a tissue parameter to constrain their gene expression correlation analysis. We will design and implement a mechanism for such parameters to be defined and included in the BTE query path execution plan.
BTE queries focus on making API calls with entity identifiers (or entity types) as the primary inputs. However, some APIs accept (or require) secondary parameters that define an analysis. For example, the
/lilgim/queryAPI accepts a tissue parameter to constrain their gene expression correlation analysis. We will design and implement a mechanism for such parameters to be defined and included in the BTE query path execution plan.