This issue opens a design question: How do we improve the location selection for an event to only show options relevant to a course? Perhaps we need an association table for course specific locations?
We do want to be able to link to true rooms for cases where office hours are being held in XL rooms that should not be reservable.
We may also want the ability to add course-specific options which are not full-on rooms in academics (such as a professor's office). So perhaps the join table is a full entity where the relation to an official "Room" is optional; or we modify the implementation of "Room" to have a global or office_hours attribute that, when True, represents a room that is globally available for selection in office hours locations.
This issue opens a design question: How do we improve the location selection for an event to only show options relevant to a course? Perhaps we need an association table for course specific locations?
We do want to be able to link to true rooms for cases where office hours are being held in XL rooms that should not be reservable.
We may also want the ability to add course-specific options which are not full-on rooms in academics (such as a professor's office). So perhaps the join table is a full entity where the relation to an official "Room" is optional; or we modify the implementation of "Room" to have a
global
oroffice_hours
attribute that, whenTrue
, represents a room that is globally available for selection in office hours locations.