Currently, it can be inconvenient and overcomplicated for our end users to perform some common aggregate operations such as getting a section's course or the professors which teach the section.
As such, we should add the following endpoints which immediately aggregate and return matching sections' courses or professors:
Courses:
Query based: GET /section/course (allows for querying like the base section endpoint)
ID specific: GET /section/{sectionId}/course (gets course only for a specific section)
Professors:
Query based: GET /section/professors (allows for querying like the base section endpoint)
ID specific: GET /section/{sectionId}/professors (gets professors only for a specific section)
Currently, it can be inconvenient and overcomplicated for our end users to perform some common aggregate operations such as getting a section's course or the professors which teach the section.
As such, we should add the following endpoints which immediately aggregate and return matching sections' courses or professors:
Courses:
GET /section/course
(allows for querying like the base section endpoint)GET /section/{sectionId}/course
(gets course only for a specific section)Professors:
GET /section/professors
(allows for querying like the base section endpoint)GET /section/{sectionId}/professors
(gets professors only for a specific section)