forked from Cal-CS-61A-Staff/seating
-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Description
- The seating layouts should ideally be stored in the DB
- We should standardize the list of room names.
- ideally you should be able to view a layout in the app.
- We should have multiple layouts per room.
How denormalized should the data be?
- Room: (name, campus id, map url(?), building name(?))
- Layout: (room_id, name, a list of seats?, a list of "available seats")
- Seat: (name, room_id, attributes: {lefty? broken? etc}, seat location)
What are the standard list of attributes? (Probably no custom ones)
Who can edit or update room layouts?
How do we create a "seat"
Should updating a "seat" update for all layouts?
We should still be able to import a CSV.
Metadata
Metadata
Assignees
Labels
No labels