You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The same course/section can be listed by multiple subject areas. Right now, Hotseat can't handle this: we consider each course to be a completely separate course. Here are some initial thoughts here:
Thoughts
DB schema:
The multiple-listed status could change from term to term, but each row in our courses table refers to the same class across different quarters. As a result, we may want to maintain the many-to-many relationship of multiple-listing in a table separate from courses, with term as a constraint.
User-visible pages:
We could try to combine multiple-listed classes into a single page, while keeping the current DB schema for courses and sections. But it can be hard to determine the "canonical" subject area for a class – which could actually be different based on the term and section.
Alternatively, we could keep separate pages for multiple-listed classes (and keep the current DB schema), but provide links to the other multiple-listed classes and display reviews for the other equivalent courses on the current page.
Test cases
A most extreme example would be LIFESCI 192A:
More normal examples include COM SCI M51A / EC ENGR M16.
The text was updated successfully, but these errors were encountered:
The same course/section can be listed by multiple subject areas. Right now, Hotseat can't handle this: we consider each course to be a completely separate course. Here are some initial thoughts here:
Thoughts
DB schema:
courses
table refers to the same class across different quarters. As a result, we may want to maintain the many-to-many relationship of multiple-listing in a table separate fromcourses
, withterm
as a constraint.User-visible pages:
Test cases
A most extreme example would be LIFESCI 192A:
More normal examples include COM SCI M51A / EC ENGR M16.
The text was updated successfully, but these errors were encountered: