CSc 8711, Spring 2011

Assignment 1 - Conference Registration Website

Using PhP/MySQL (and some Javascript), implement a Web-based system to enable registration of conference participants. Some of the participants will have papers to present at the conference while others will be simply attending. Each paper MUST be registered (i.e. paid for) by one of the authors. The initial screen should be as follows:

The registration information to be captured is discussed below:

• Personal and Contact Information: The title, name, institution, and address/contact information of the registrant. The following image shows you a sample interface.
  
• Paper: A pull-down list of paper number and paper title along with a default option of "None" from which the registrant can choose a paper they wish to register. The following image shows a sample interface.
  
• Registration Type: We allow two types of registrations: "Basic" and "Full". Each registration type has a different cost associated with it depending on whether the registration is done before or after a deadline date. We will assume that we are in the early registration period - so the late registration radio buttons should be disabled. Basic registration does not provide banquet or dinner - so if the user chooses basic registration, the banquet and dinner options should be disabled. Of course, basic registrants can purchase additional meals or dinners. The choices for meals are: vegetarian, seafood, and chicken. The choices for dinner are: lobster or vegetarian. The additional tickets numbers should be 0, 1, 2, or 3 and if the user chooses a particular number, only those many ticket choices should be enabled. The following image shows a sample interface.
  
• Residence Halls/Shuttle: The conference provides accomodation in the form of rooms in the residence halls (single and double rooms) for the duration of the conference. The registrant may choose to pay for these rooms by selecting the days on which they wish the accomodation. The conference also provides shuttle bus from the airport to the conference venue in the beginning of the conference and from conference venue to airport at the end of the conference. Registrants may choose to use these shuttles. The following image shows a sample interface.
  

Upon submitting the data, a summary of the registration should be displayed as shown below:

The summary page should have a submit button. Upon clicking this, the payment should be processed (i.e. an entry in the payment table should be made). Ideally this should take the user to a payment processing system such as paypal, but we will skip this part in this assignment.

Report Generation

• Registrant Listing
• Banquet Listing
• Dinner Listing
• Residence Hall Listing
• Shuttle Listing

Some Remarks

• Once a user makes the payment submission, the system should not allow any changes. However, if the user has submitted their data but not made the payment, they should be allowed to return to the system (by logging in again) and make any changes to the data and submit. Note: When the user logs in after having submitted the data in the past (but without making the payment), the data form(s) should be populated with their current values.
• The data capture can be coded as one long page or several pages (preferable and easier).
• Database schema is available at: confReg.sql
• Sample paper/author data is available at paper.sql
• The project will be graded for correctness as well as user friendly interface. Javascript should be used to enhance the interface.