Expose pathway tabular results tables B,C,D through WebAPI endpoint.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 151
- Forks
- 183
- Avg merge
- 14m
- Merged PRs (30d)
- 2
Description
Expected behavior
Would like to get the tabular results of Pathway Results Tables B, C and D via and endpoint.
Actual behavior
These tables are generated on the UI (javascript) side by taking the raw results and deriving tables B, C and D. Table A is the raw data.
This issue is to request the feature that the logic that builds the tables in the UI are implemented in WebAPI so that people can fetch these tables from a WebAPI endpoint. Either the endpiont should derive those results from the raw data, or the analsyis should save those results to a separate results table. The advantage of doing it on the fly is that the data-model dooes not change in the DB and we don't have to alter the analysis SQL to save those results. The disadvantage is that it would be quite a bit slower to fetch the results from the DB and derive the tables on-the-fly.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the WebAPI endpoint handling Pathway Results and the JavaScript logic that currently derives tables B, C and D from raw table A results. Compare deriving the tables on request with saving them separately, then define the endpoint response and verify that it matches the UI-generated tables.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, javascript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100