REVAMP RANK SYSTEM

[Apexal]

After meeting with Board Members, the current way I have ranks set up (all relative to camps and not bound to user account at all) would not work well in practice.

It appears (subject to change)

• Admins always stay admins
• Ambassadors are assigned general geographical areas and stay ambassadors for a while
• Program Directors function in an area governed by an Ambassador and usually stay Program Director for a while
• Teachers are generally bound to a specific area but can move around in ranks?

[Apexal]

This is what I will do:

Ranks are per user now (as they were in the very beginning) User schema changes:

// For teachers
rank: 'teacher',
rankInfo: { camp: campId }

// For directors
rank: 'director',
rankInfo: { ambassador: ambassadorId, camp: campId }

// For ambassador
rank: 'ambassador',
rankInfo: { area: 'Area Name', camps: campId }

• Rank is first determined on application when a user chooses their superior
• Change in rank has to be applied for and approved
• Administrators (Board members) can manage all camps
• Ambassadors can manage all camps in their area
• Program directors can manage their one camp
• Teachers can manage (with limits) their one camp

[Apexal]

After talking to higher ups, it seems like ranks are set at one point during the school year and don't change for months, until after the camp finishes. After this everything pretty much resets for next year. Because of this, associating users directly with ranks may not be best practice.

Perhaps rank info will be erased from user schema's and only will be handled by workshops.

The process would be something like this:

• Early in the year a ambassador/program director schedules a new workshop starting months later
• Teachers apply to join it/are invited to join it and the program director accepts/denies applications
• Ranks are set on the camp
• Eventually workshop ends and is archived by director
• Involved users don't have an active involvement anymore
• Repeat

[Apexal]

Thinking about it more made me realize users who are ambassadors/program directors need to keep their rank associated with their user so they can manage workshops at any time. Perhaps ranks should be kept but definitely active workshop ID's shouldn't be kept on users.

[Apexal]

Here is a pretty good overall solution:

• Upon registering on the website, users decide what they want to be Ambassador, Program Director, or Teacher and once accepted it is associated with their account
• Changing this "global" rank can be a separate process/application
• Ambassadors/directors can schedule new workshops only
• Teachers can apply to workshops