You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm taking a stab at it - and this is the first draft
DB design
This is where we're sketching out the information which Ticket
will persist for us.
As a user [contact with credentials] I would like to see what tickets [events] my coworkers [contacts belonging to contact] and I have.
As a participating scout [contact with credentials] I'd like to be able to comment [post belonging to a post] on a comment [post] where someone [contact] suggests that I [contact belonging to event] should accept responsibility [with role "delegated_to"] for a ticket labeled 'Åbningslejrbål' [event]
Core Elements
event
contact
post
We could totally abstract this away by adding
event
id
resource_id
...
contact
id
resource_id
...
post
id
resource_id
...
resource
id
ancestors
resource_events
resource_id
event_id
resource_contacts
resource_id
contact_id
resource_posts
resource_id
post_id
The text was updated successfully, but these errors were encountered:
I'm taking a stab at it - and this is the first draft
DB design
This is where we're sketching out the information which Ticket
will persist for us.
Core Elements
We could totally abstract this away by adding
event
contact
post
resource
resource_events
resource_contacts
resource_posts
The text was updated successfully, but these errors were encountered: