Summary
The study history page can load very slowly. This is probably because of the potential for a large amount of data (all responses and associated videos for a given user), along with no pagination.
In practice I don't know how many users are affected by this. The page loads slowly for me (because I have so many responses due to testing), and we've had one parent report the issue as well.
Solution
We should add pagination to this view so that only the most recent N responses are loaded to start with. Moving through the pages should trigger a full page reload.
One thing to think about is how to handle the potential for many videos associated with a single response. Right now we load all videos for every response, but we might need to use some kind of pagination for this too, given that there is no upper limit to the number of video recordings associated with a response.
Summary
The study history page can load very slowly. This is probably because of the potential for a large amount of data (all responses and associated videos for a given user), along with no pagination.
In practice I don't know how many users are affected by this. The page loads slowly for me (because I have so many responses due to testing), and we've had one parent report the issue as well.
Solution
We should add pagination to this view so that only the most recent N responses are loaded to start with. Moving through the pages should trigger a full page reload.
One thing to think about is how to handle the potential for many videos associated with a single response. Right now we load all videos for every response, but we might need to use some kind of pagination for this too, given that there is no upper limit to the number of video recordings associated with a response.