rjenks / con-org Goto Github PK

The volunteer system is for more than just volunteers. It has been used for Press, Guests and Panelists. It could be used for other non-volunteer purposes. The system needs to recognize these special uses and adapt the vocabulary and workflow as needed.

The emails automatically sent from the volunteer system need to take into account of non-volunteer departments. It is no appropriate to send guests or press "you have been accepted as a volunteer" messages.

Back Office -> Announce sends emails to non-volunteer departments when trying to email assigned or unassigned volunteers.

For emergency purposes it is advisable to pre-print a stack of valid badges that can be used as temporaries during a period where registration has lost access to the internet or the site goes down. Pre-printing and activating these badges should not impact the attendance count.

Need to understand the full use case. Maybe this is only needed to fix mistakes.

Need to determine pattern.

Minimum Functionality

• Full Schedule w/ Ability to register for programming
• My Schedule w/ ability to un-register for programming
• Map

Needs more definition to reduce noise. Maybe only "highlighted" programming.

(req by Freddy)

To allow for scaling and proper inventory handling, move the shopping cart to the database.

(per Jonathan)

(per Jonathan)

(per Jonathan)

Need to add a lot more data.

• Include a list of other times this same block is scheduled
• Include more details about the panelists
• Include panel setup details if the viewer is staff

Minimum Functionality

• Full Schedule w/ Ability to register for programming
• My Schedule w/ ability to un-register for programming
• Map

The catalog supports adding inventory counts to items. The system needs to:

• Properly decrement the count upon purchase
• Properly prevent offering/adding to cart an item that no longer has inventory (including what is in the cart of other shoppers)

Most of the admin pages should restrict this to Supervisor. There is no reason to allow most of the admin pages to be made public or member accessible. Without a restriction it might be done in error.

• Easier to pick person for item

Children under 13 don't have their own login accounts. Need to find a way to allow the adult account (account which holds their child badge) to sign them up for events.

Prevent purchasing membership for self if they already have a membership which expires the same or later date than what they are trying to purchase. This includes trying to add multiple memberships for themselves into the shopping cart.

This would allow giving out coupon codes that could only be used once to purchase a particular catalog item that is hidden. For example a comp badge.

Add a field in Purchase where user can type a coupon code with a "Enter" button.
Maintain a list of entered coupon codes in their session
Add catalog items to the purchase screen unlocked by the coupon code

Don't allow roles tied to an event to not include any of the dates of the event.