TOPIC: Waiting list

02.) Waiting list:

-Waiting List should work EXACTLY like a registration as far as what data
it collects

-It does not however need to check for any type of overlapping.

-Once an event drops below it's MAX count ie: if a user cancels or if the
admin removes someone, the ADMIN should get an email notice (when a user
removes him/herself) or the admin should get a "pop-up" message that there is now and opening and there are users on a waiting list.

-the ADMIN should be able to select a user to move to the registration
list for that event. BUT this process MUST do overlap checking to make
sure the new user in the event won't conflict with another event (in fact, any time an ADMIN manually enters a user into an event, the overlap
checking should always check, but an ADMIN can "override" the entry if he
wants to) I believe at this time, the ADMIN is NOT allowed to put someone
in an event if it will overlap, but ADMIN should be able to over ride ANYTHING

-There should also be a "view waiting list" list like viewing registrants
so users can decide if they really want to be on the list ie: this event
is full, would you like to view the current list of users on the waiting
list ? if they click yes, they get to view the waiting list, which will
have an option to sign up or not. If they say yes, then it will ask if
they want to sign up on the waiting list.