Migrate to the Sites framework / store dorm-specific data in a model
Bug #1140457 reported by
Luke Faraone
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Dormbase |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Rather than having DORM_SHORTNAME and BUILDING defined in settings.py, we should probably store this data in the Sites framework.
This may involve us creating a new Dormitory class that uses a foreign-key to a Site as its primary key.
Data a Dormitory class needs to store:
- Dorm (short/long?) name
- Dorm building number
| Changed in dormbase: | |
| milestone: | none → march2-hackathon |
| description: | updated |
| description: | updated |
Revision history for this message
| Jacob Hurwitz (jhurwitz) wrote | #1 |
To post a comment you must log in.
Another thing we may want to do: Let dorms enable/disable certain parts of the site. (Eg, Random doesn't have LaundryView. Dorm X may not have movie rentals at desk. Dorm Y may not have guestlists.)