Finalize db schema.

[jaybobo]

question1
Does someone have a picture of the data model somewhere?

question2
How do we want to handle the relationships between Users, Pairs & Skills? It seems to me that Skills are a one-time resource that live for the length of an event.

question3
If so, should an event queue Users before they're put into pairs? I would think a User upon accessing an Organization's Event would need to select their Skill for theEvent, queue themselves and change their state to ready_for_pairing.

[jaybobo]

cc: @cartoloupe @TravisSperry

[TravisSperry]

Q1-I don't know if anyone photographed the sketch of the data model... spammed Slack

Q2-I found myself putting in the the same if not similar skills each week... Maybe there's a many_to_many on skills and users. Then when someone joins an event they can specify the skills (teaching/learning) for that particular event? <-- @jaybobo said this in Q3

Q3- Who starts en event? Or does it start automatically? Are people who RSVP'd for an event automatically added? Are they sent an email asking if they want to join? <-- The last seems like it might be the best option.

Basic Start of Event Flow
-User gets email asking if they want to join an event they rsvp'd for. They receive a link to go to the event's page...
-On the event page the user could click button to join event. Prior to confirming they're joining they can select the skills they would like to teach and or learn. Confirm, and they are added to the event.
-Users wouldn't be added to an event until they confirm skills and join. Up until then they might just be interested?

[cartoloupe]

Q1 - I think I saw a few people take pictures of the board. I will work on some failing tests that will drive what I remember of the board.

Q2 - This makes sense so far. Since Skills are a one-time resource for Event, maybe they should be recorded at the Event level, or the Pairs level? If so, it seems like they would be connected to a User through Event.

Q3 - These are good questions; they're helping define the workflow. I think every Event needs to have an organizer (a type of User) who starts it.

I like the RSVP -> event auto-add, and the RSVP -> email options. I think email would work best too, because the time between the RSVP and the event, the user might have a change of plans.