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
we should add a way to configure applicant "waves" in the portal.
the concept of "waves"
it is common in applications of all kinds for there to be multiple waves of admissions. ie, there is a first deadline, a second deadline, maybe a third, etc. however, usually application decisions are made on a rolling basis (by the wave), so for example, first wave decisions are made after the first wave closes.
current state of portal
currently, there is no concept of waves in our portal. we are able to make applicant decisions independently, so we can admit/deny applicants before our application deadline, and applicants will see their decision in the portal, but teams is still a problem (see #143 ) and CRUD permissions per wave deadline don't exist (not per-se a problem, just kinda weird).
implementation spec
from the admin portal, admins should be able to configure wave deadlines. for example, I might set a wave deadline "6/30/2021 11:59:59 EST" and "7/6/2021 11:59:59". applicants applying before the first deadline are in wave 1. applicants applying before the second deadline are wave 2. there is no third deadline, so the wave2 deadline is final submission deadline. admins should also have to configure a confirm-by date per wave, and will have the ability to toggle show decision status per wave.
this will affect teams (see #143 ), decision exporting (export by wave), and sorting/filtering in admin portal (add new "wave" field to applicants). we can also implement admin warnings based on wave show decision status (ie if show decision = true for wave 1, display warning "ur mom applied in wave 1 and wave 1 show decision status = true, but they don't have a decision yet".
The text was updated successfully, but these errors were encountered:
we should add a way to configure applicant "waves" in the portal.
the concept of "waves"
it is common in applications of all kinds for there to be multiple waves of admissions. ie, there is a first deadline, a second deadline, maybe a third, etc. however, usually application decisions are made on a rolling basis (by the wave), so for example, first wave decisions are made after the first wave closes.
current state of portal
currently, there is no concept of waves in our portal. we are able to make applicant decisions independently, so we can admit/deny applicants before our application deadline, and applicants will see their decision in the portal, but teams is still a problem (see #143 ) and CRUD permissions per wave deadline don't exist (not per-se a problem, just kinda weird).
implementation spec
from the admin portal, admins should be able to configure wave deadlines. for example, I might set a wave deadline "6/30/2021 11:59:59 EST" and "7/6/2021 11:59:59". applicants applying before the first deadline are in wave 1. applicants applying before the second deadline are wave 2. there is no third deadline, so the wave2 deadline is final submission deadline. admins should also have to configure a confirm-by date per wave, and will have the ability to toggle show decision status per wave.
this will affect teams (see #143 ), decision exporting (export by wave), and sorting/filtering in admin portal (add new "wave" field to applicants). we can also implement admin warnings based on wave show decision status (ie if show decision = true for wave 1, display warning "ur mom applied in wave 1 and wave 1 show decision status = true, but they don't have a decision yet".
The text was updated successfully, but these errors were encountered: