This turned into a bit of a brain dump of what needs to happen in the lifecycle of a member. I'm posting it here as an issue for discussion purposes.
Intro Member Creation
create an intro eval record in the evaluation table.
record intro membership status start in the membership table.
send email to freshman for password creation.
create packet based on current membership (important that new member creation with residency status occurs before packets are generated).
Packet Passage (tentative behavior)
If an intro member passes their packet:
ask intro member for password confirmation in some way (by notice in app or by email)
enable user creation script to pull from pvals and confirmed password, creating a matching LDAP account. RTPs can create accounts at leisure.
LDAP data will be pulled on first login to the version behind webauth
Introductory Evaluation
create new membership evaluation record in the evaluation table. Should start the same day as the intro eval that was just passed (otherwise attendance data will be lost)
Both Evaluations
Eval Director selects pending evaluations to consider (for slideshow generation)
separate evaluations by category and then by distance from deadline.
those evaluation and associated membership statuses become unavailable
Evaluations happen
add conditional to evaluation if necessary
record new membership status if applicable
Director releases evaluation results after informing members
This turned into a bit of a brain dump of what needs to happen in the lifecycle of a member. I'm posting it here as an issue for discussion purposes.
Intro Member Creation
evaluation
table.membership
table.Packet Passage (tentative behavior)
If an intro member passes their packet:
Introductory Evaluation
evaluation
table. Should start the same day as the intro eval that was just passed (otherwise attendance data will be lost)Both Evaluations