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

Filter/search support for Pagination #84

Open
yuanchen233 opened this issue Jun 14, 2024 · 1 comment
Open

Filter/search support for Pagination #84

yuanchen233 opened this issue Jun 14, 2024 · 1 comment
Assignees

Comments

@yuanchen233
Copy link
Collaborator

yuanchen233 commented Jun 14, 2024

The pagination for getParticipant and getDeployment should support filter/search
We should do pagination on database level

@yuanchen233 yuanchen233 self-assigned this Jun 14, 2024
@yuanchen233
Copy link
Collaborator Author

yuanchen233 commented Aug 16, 2024

Since we have expectedParticipantData now, we should consider save and access participant information (email, name, etc.,) here, and use Keycloak only for identity management, this will

  • Save a lot of resources and time when processing recruitment/participants related operations.
  • Save participant information in our database, instead of Keycloak database
  • Have user information page back on Portal
  • Requires changes to participants page, as information will not be stored in keycload anymore (or extra work)

Maybe also consider change Participants page --> Recruitment page, and remove deployed participants, since they should be managed in deployments

The process time is expected to reduce significantly for Participants and Deployments page on Portal, and we can keep rely on frontend to do pagination.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

1 participant