Design

A conference is a collection of actions.

An action may have a deadline and may have prerequisites. Every action has either a deadline or at least one prerequisite.

An action may be assigned to a person or a role.

A role is fulfilled by a person for a known term.

A person is a first name, last name, and email address.

An action is performed in one of three ways:

• Posting a web form
• Checking a box or radio button (on a web page)
• Uploading a document or spreadsheet

Some actions must be performable multiple times.

An action may have associated policy.

Policy may include requirements, suggestions, and advice. (Requirements themselves are probably also associated with actions, e.g., checkboxes. Ugh.) Requirements and suggestions should probably appear on the web page that supports performing the action. Advice should probably be linked.

Long term storage (database) should remember who served in what roles when. We probably need to accommodate multiple persons sharing a role, reassigning roles, and ...?

A user can create an action.

Existence of an action contingent on a choice, e.g., if physical PC meeting then book room and assistant.

Actions might include some things that look vaguely unrelated to the conference like "appoint someone to steering committee" or "schedule instantiation of next year's conference" (as an action with a deadline). Basically the idea is to tie periodic events to the conference.

The Wizard may implement some actions. At least one: instantiate conference.

We want reminders.