As an admin, I can now link an office hour to a specific room slot. This lets us know which office hours will be using which physical room slots, so that we can figure out how busy the room will be, which rooms are currently unused, etc.
Discussion
Recently, the room slot entity was created to store information about the location of an office hour. This issue aims to connect the room slot entity with the office hour entity to make the process of managing office hours simpler. Ultimately, the office hour entity will have fewer properties (id, tutor assignment, room slot, zoom room link, notes) without losing any functionality. This issue implements this change in the back end, while #292 implements the front end. This should make issue #193 much simpler because the office hour query will include all upcoming office hour information.
Acceptance Criteria
[x] Office hours no longer store location/time data, and can store a room slot
[x] Adequate test coverage
Implementation Todos
Front end:
The front end of this issue should be implemented in issue #292.
Back end:
[x] Modify OnlineOfficeHours.js (entity) to store a RoomSlot rather than time/location
[x] Modify OnlineOfficeHours.js (tests) to work with the new RoomSlot property
[x] Fix references like the constructors for the online office hours to look to the room slot within the office hour for the time/location data
User Story
As an admin, I can now link an office hour to a specific room slot. This lets us know which office hours will be using which physical room slots, so that we can figure out how busy the room will be, which rooms are currently unused, etc.
Discussion
Recently, the room slot entity was created to store information about the location of an office hour. This issue aims to connect the room slot entity with the office hour entity to make the process of managing office hours simpler. Ultimately, the office hour entity will have fewer properties (id, tutor assignment, room slot, zoom room link, notes) without losing any functionality. This issue implements this change in the back end, while #292 implements the front end. This should make issue #193 much simpler because the office hour query will include all upcoming office hour information.
Acceptance Criteria
Implementation Todos
Front end:
The front end of this issue should be implemented in issue #292.
Back end:
Testing: