database - DB Schema Organization -

I am currently in the stage of building a scheduling web app (for volunteer staffing of events), and I have more experience There is a question for people who have a problem.

Background: There is a calendar of events, and at any time any user can register for any of the events in later times, but before that incident, one of the administrators will step in And one of those people will select "Staff List", and the rest will be put in "Alternate list".

What I'm still wondering is that there will be an event table, a user table, and then three others:

• UserEvent
  • Maps users Events for which they are registered.
  • Userstuff
    • For the events registered in Maps users, there is reason to be even more staffing.
    • Similar to UserStaff

  The question then makes two parts:

  • Do this Is there a good way?
  • Is each of those three assisted tables and User IDs and Event IDs?

  That is the second question I really want to discuss. It seems that many duplicate content (everything in UserStuff or UserAlt will always be in UserEvent) seems like, so I was thinking of creating a unique key for the UserEvent table, in addition to the composite key, other tables (UserStaff and UserAlt) on the plus side, there is less duplicated content, there is an intermediate table below (UserEvent) that needs to be referenced in almost every query.

  Hopefully I am quite clear, and thanks in advance.

I will have the following tables:

  event (event id, name Event Registration (Event Registration ID, User Id, EventID, Participant Typepad, etc.) Participant Type (Participant Typepad, Name)   / Pre> 
 Participant Type: Name, Date, Location, Capacity, etc. One of the "participants" or "employee".