Hi,

I am trying to setup a new portal to help a local youth group with an online voting system to select their office bearers.

Here are the requirements. Please help me with any design ideas:

1. Since this is a poll, we don't want to associate / link "user info" with "nomination" info they will enter on the ballot form.

2. As such we don't want to have links like REGISTER or LOGIN on the site visible to general public. But we need a way for Admins and Poll coordinators to login to the site using a 'secret' channel.

3. The Home will contain the Page 1 of a 2 page form. Page 1 captures Name, Email address, City, and the local club they belong to. When they submit the Page 1, Page 2 will be displayed.  Based on the local club they belong to, a different version of page 2 will be displayed.

3.a: I would like to create a user record at this point. With Email as the User name, City as the password & confirm password fields.

4. The info captured on Page 1 should be displayed in read-only mode on Page 2. 

5. SUBMIT link should only be present on page 2. (or the last page of the multi-page form).

6. Once the Form is submitted on the last page, we want to set a special flag to signify a person with these attributes has voted already. If the same person tries to vote again, (based on the  information entered on page 1), the system should be able to show a message stating that "you have already voted; you can only vote once'

7. The user data and the voting data should be stored in DNN (possibly in user profile) for easy reporting.

Key questions here are:

Q1: How to create a new user record without actually asking for username and password. How can we use the email address and some other info (such as City or local club name) as the password and create a user record behind the scenes and associate the voting info from Page 2 to that? (Unique id concept??)

Q2: How to set a flag (or a role?) to denote a user has already voted?

Q3: How to recognize the user when he /she comes back at a later time and tries to vote again? (since we don't have a login system)

Q4: the reason the group doesn't want to have login / register functionality is that it appears these features may sound like 'too complex'. In their view, it would be simpler and easier if they don't need to 'register'; they simply want to fill a form and submit it.

Any ideas and details on implementing this are greatly appreciated.

Regards,

VR