Feature Requests

When searching with few filters, it lags a few seconds before loading results. This is normal, but when searching for something by typing from scratch, like ECON 159, it searches E (which takes a few seconds), then EC (which takes a few seconds), and so on before you finalize your search. This could be alleviated by having searches be non-blocking and then just discard the results if a new search query is placed.

I'd love to be able to type something like "graduate CPSC courses that don't conflict with my worksheet", or "4000-level MUSI classes on MW" and get a query built for me. Similar to this https://www.mongodb.com/docs/atlas/atlas-ui/query-with-natural-language/

I would love to be able to message my friends on course table, or leave comments on their schedule. Otherwise, a feature on the course catalog that shows friends with the course in their worksheet.

I want to see the 4.2+'s who have taught 20 classes not, the 5.0's who have taught 1 : ( especially when solid meta these days is registering based on prof.

It would be great if we could add friends while using coursetable on our phones! Thank you!

I end up drafting my instructor permission requests on a google doc and it requires a lot of flipping back and forth to look at course description. I'd like to have all planning in one place. Could you add a saveable notebook to the worksheet page to draft instructor permission requests? Ideally could be open while a course popup was clicked on from the worksheet.

From our user survey: > Ability to add private notes to each course (for example, I like to keep a list of pros/cons for each class)

It would be great to add the distributional categories from the CPSC Grad Student handbook (Programming-Intensive, Theory, etc.), as that is important information for a CPSC grad student to see and ideally filter by.

Can't really trust a > 4.8 when they've only taught one course :/

There seems to be a considerable bias, especially for smaller seminars, in that only students completing the class can submit evaluations. Knowing the reasons for why students decided to withdraw from a course could offer valuable additional insight to future students. This of course would supplement the current scraped data, and perhaps could benefit from a basic verification functionality to prevent falsified reviews (such as uploading a screenshot of the withdraw request, etc) during the comment submission process.