This repository has been archived by the owner on May 29, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2
Project Outline
Robert Lin edited this page Oct 31, 2018
·
8 revisions
A club or hackathon administrator who needs to manage and assess a large number of applicants through multiple "events" (e.g. application, resume screen, and interview) for an "application period".
- create and authenticate accounts
- verify email address
- create
clubs
Consists of:
- email (ID)
- name
- add
users
asadministrators
toclubs
- create
application periods
, which consists of a list ofevents
- save
event
templates that can be reused across application periods - maintains a pool of
applicants
that get dropped by age
- an
event
is a set of inputs - "datapoints" - which could be of the following classes:- email address
- short text
- long text
- links
- enums (options, can be used to set
tags
on participatingapplicants
)
-
events
should be able to settags
on participatingapplicants
- an
event
can be eitherexternal
(for applicants to use) orinternal
(foradmins
to use to fill data about an applicant) - for example:- external form for club application
- internal form for application review
- internal form for interview
- no account creation needed - entry automatically created based on datapoints from
events
Consists of:
- email (ID key)
- name
- phone number
- relevant
application periods
- includingevents
andtags
assigned to the user during the period
- find and order
applicants
based on conditions (event
datapoints,tags
, etc.)- send emails to all
applicants
in a result set
- send emails to all
- drag and drop to reorder, which adjusts a hidden internal ranking score to the relevant
applicants
- pull up all data the club has about an applicant
- Scheduling features
- Security log
- Data export
- Deletion protection for clubs
- Dashboard