Closed AveshCSingh closed 12 years ago
When I do WebISO, I will be adding a table for organization users that are allowed to create stuff. This table will actually have a field for organization (to pair each user with one) and each event will be paired with the user who created it, so all you would have to do in the end is walk up the table hierarchy to get the organization it was listed for.
(aka, it would end up literally being in Rails code event.user.organization)
But a single user may have multiple organizations, so he could create multiple events under different organizations.
For example, acsingh could create JV Apps Team Meeting (ACM) and Engineers Without Borders PR meeting (EWB).
In this circumstance, we cannot distinguish which organization is associated with which event.
Yeah, I was thinking that as well. It would be better to have a table organizations, define a relationship between organizations and user, and then have a relationship between events and users, in addition to a relationship between events and organizations. This way, a filtering feature can be later on made to grab events by organization, but at the same time we can hold individual users accountable (which is what is desired).
I can take on the task of setting this all up.
This sounds great! As long as:
(1) always holds as far as I can tell
(2) may be broken for joint-events between organizations. Can you make the relationship Event -> Organization as a has-many relationship?
Yeah, the relationship will be has many.
Did this.
Add 2 more fields to the backend and the frontend event creation interface: -Link to source, -Organization that is hosting event