I've modeled the event-to-url association backwards. We should get users to check off that they're attending an event, add to some sort of user-events join collection (or maybe on the user collection).
If we have a better association between users and events, we know which users were at which event (wildly useful), and derive the url's event from the user that last updated the url, this'll also very useful in tracking down who attended / onboarded at which event.
From @b5 on February 2, 2017 13:38
I've modeled the event-to-url association backwards. We should get users to check off that they're attending an event, add to some sort of user-events join collection (or maybe on the user collection).
If we have a better association between users and events, we know which users were at which event (wildly useful), and derive the url's event from the user that last updated the url, this'll also very useful in tracking down who attended / onboarded at which event.
Copied from original issue: b5/pipeline#18