Skip to content

Paginate studies history page to fix 500 error#1859

Open
becky-gilbert wants to merge 6 commits intodevelopfrom
paginate-studies-history
Open

Paginate studies history page to fix 500 error#1859
becky-gilbert wants to merge 6 commits intodevelopfrom
paginate-studies-history

Conversation

@becky-gilbert
Copy link
Copy Markdown
Contributor

@becky-gilbert becky-gilbert commented Mar 25, 2026

Fixes #1801

This PR adds pagination to the family-facing studies history page (My Past Studies), in order to fix 500 response timeout errors when there are lots of previous studies/responses.

  • The page now uses pagination for the study list. The first 10 studies are shown on the page, and the user can navigate forwards/backwards across sets of 10 studies, up to their total number of previous studies.
  • The page now uses pagination for responses within each study. The first set of 10 responses are shown, and the user can navigate across sets of 10 responses for any particular study. (Note that this feature probably won't apply to most family users, but it's helpful for researchers/developers who create a huge number of responses for the same study while testing).

Pagination of responses within studies:

study_resp_pages

Pagination of studies:

study_pages

When there are fewer than 10 studies, there is no study pagination:

no_past_studies

When there are fewer than 10 responses for a study, there is no response pagination:

no_resp_pages

… within studies on study history page - keeps all query params and adds response_page_{study_pk} var with page number request
…per study (1); add query parameters for navigating across study pages and response pages
@becky-gilbert becky-gilbert self-assigned this Mar 25, 2026
@becky-gilbert becky-gilbert requested a review from mekline March 25, 2026 21:33
@sonarqubecloud
Copy link
Copy Markdown

@becky-gilbert becky-gilbert added Bug [Work Type] An issue with the program Participant [Audience] Participant-facing Performance Tuning [Work Type] Refactoring that is user-facing, affecting latency and/or space complexity labels Mar 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Bug [Work Type] An issue with the program Participant [Audience] Participant-facing Performance Tuning [Work Type] Refactoring that is user-facing, affecting latency and/or space complexity

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Study history page loads slowly

1 participant