You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, all applicants are shown on a single page. This worked okay for the last two years but became slightly inconvenient as the number of applicants grew over 500. It would be better to implement pagination so users don't need to scroll through all of the items. The total number of cards may also be causing a small performance hit in the browser.
If the applicants are divided into pages, there would also need to be a way to search for a specific applicant by name or UID since the desired record may not be on the first page (see ParticipantsTable for reference).
Given the total number of applicants should be under 1000, we should be fine with using client-side collections rather than implementing pagination and searching on our API endpoints.
If time permits, it would also be good to add collection preferences to adjust the number of cards per page and perhaps also the visible properties.
The text was updated successfully, but these errors were encountered:
Related to #530:
Currently, all applicants are shown on a single page. This worked okay for the last two years but became slightly inconvenient as the number of applicants grew over 500. It would be better to implement pagination so users don't need to scroll through all of the items. The total number of cards may also be causing a small performance hit in the browser.
If the applicants are divided into pages, there would also need to be a way to search for a specific applicant by name or UID since the desired record may not be on the first page (see
ParticipantsTable
for reference).Given the total number of applicants should be under 1000, we should be fine with using client-side collections rather than implementing pagination and searching on our API endpoints.
If time permits, it would also be good to add collection preferences to adjust the number of cards per page and perhaps also the visible properties.
The text was updated successfully, but these errors were encountered: