This repository was archived by the owner on Apr 10, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Events and Bookings
jules2689 edited this page Nov 12, 2014
·
5 revisions
- Similarly to tutor, "tutor" users may also create "Event events"
- Event events are sessions that can handle a classroom size number of children
- Registration (booking) will be handled through the system and customers or non-customers will be able to register their children. Customers will be fast tracked through the process, while customers will need to register through a full customer signup (they will be registered and signed up at the same time).
- Event events will indicate name, dates and times, description, type of event, materials needed, spots available etc.
- Createable by Tutors and Admins, modifiable by the tutor that made it or an admin
| column | type |
|---|---|
| id | PK (int) |
| name | varchar(255) |
| description | TEXT |
| spots_available | integer, default = 3 |
| subject_id | FK |
| type | varchar(255) [ tutor or event event ] |
| materials_needed | TEXT |
| address_id | FK |
| price | DECIMAL(10,2) |
| tax_rate | DECIMAL(10,3) |
Shopify may have free and open source money handlers in Ruby.
- A booking is a link between "customer", "event", "tutor", "child"
- It is simply a join table
- Booking has one child, one tutor, one event, one customer
| column | type |
|---|---|
| id | PK (int) |
| customer_id | FK |
| child_id | FK |
| tutor_id | FK |
| event_id | FK |