Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multi-family analyses #1158

Open
Madelinehazel opened this issue Jun 21, 2022 · 1 comment
Open

Multi-family analyses #1158

Madelinehazel opened this issue Jun 21, 2022 · 1 comment
Labels
backend Flask bug Something isn't working frontend React

Comments

@Madelinehazel
Copy link
Contributor

Madelinehazel commented Jun 21, 2022

We would like to be able to run multi-family analyses.
To do so, we would need to change:

  • The requirement for there to be one family ID in the analysis request
  • Setting the family codename to the first element in the list (rather, some combination of the set of family codenames?)
  • BUG: On the frontend, it is currently not possible to select multiple families for an analysis if you have to search for families on different pages (e.g. 2060 and 1954); if you select the datasets for the first family, and then search for the datasets for the second family, the selection for the first family disappears.
@kevinlul kevinlul added backend Flask bug Something isn't working frontend React labels Jun 21, 2022
@kevinlul
Copy link
Collaborator

Source of bug: with remote data and custom pagination, previous search results and pages are discarded: mbrn/material-table#1921
Solution: implement ourselves like in the issue a way of keeping track of selections across pages and search results, or support some kind of OR query in the filters so everything you might want to select can be contained in one search page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Flask bug Something isn't working frontend React
Projects
None yet
Development

No branches or pull requests

2 participants