ufosc / swampscheduler Goto Github PK

Use RRules to create an iCal file.

Allow custom course names and abbreviations.
Put locations.
Put period ranges and instructor information in description.

Either create a way to scrape RateMyProfessor or see if this open-source API still works https://github.com/tisuela/ratemyprof-api

Ability to save schedules to the browser as a cookie.

Maybe auto-save.

Include:

• About the app (including how it works and graphics)
• The Team & OSC
• Contact Info

Similar to Registr.

Save selections to the browser cache.
Maybe even link sharing.

Maybe auto-save (display last updated time live).

• (Last Saved Right Now)
• (Last Saved 1 Minute Ago)
• ...

Should we disallow a course from being in multiple selections?

Disallowing this would prevent schedules with multiple sections of the same course.

If we disallow this we should warn the user if they attempt to add a section somewhere they shouldn't.

Getting machine-interpretable information from a UF Degree Audit is not very straightforward and standardized.

Maybe creating a model for each degree (start off simple and work up based on # of requests). Basically a dependency tree.

If the user searches courses by typing in a common class prefix, the search for matching courses will hang. It would be helpful for users to end the search or be able to start a new search with updated terms that implicitly cancels the previous one.

"Scroll to Top" button under generated schedules.

• On hover over a course/section, change the color of sections that belong to that course.
• On hovering over a section (on the left), change the color of the same section (in the middle) if it exists
• On hovering over a section (in the middle), change the color of other sections in the middle that belong to the same course

The goal is to easily identify groups of courses.

create a "no back-to-back" option that calculates the time it takes to get to each class and make sure it is possible to make it within a certain time period

• Update README with more information.
• Change name to SwampScheduler
• Add beautiful screenshots (maybe animations, too -- zooming perspective)
• Add OSC Logo
• Add Documentation link

This would enable the use of React hooks from this file

Searches made with the same letters but different capitalizations are cached separately. For example, if you search "mas" then "Mas" the app calls the API a second time instead of using the cached data. We should normalize capitalization before saving data to fix this issue.

Come, join the dark side!

In reference to Robert's comment #26 (comment).

Expected behavior:
When the user searches "MAC", all math courses are fetched like MAC2312, MAC2313, MAC1105, etc... What we want to do is cache all of these courses (I believe this is already the default behavior for React Query), so when the user queries a specific math course like MAC2312, we will fetch from the cache to get information for that specific course instead of refetching the API.

We can also fetch that course in the background and then update the cache with the latest information.

Collapse-able selections with rotating chevron indicating status. Needs minimum height. Should show some inline statistics of contained sections & courses.

Alot of people depend and use their phones more than their computers, so I think it is a good idea to also create a mobile version of this app if we want it to be widely used.

Something sleeker that takes advantage a better React techniques for less re-rendering would be optimal.

Better theming too.

Should not show E1, E2, and E3 because there are no meetings during those periods.

Should be able to click on an icon (external link box symbol / goto) in a SectionDisplay under selections to bring up its corresponding course:

• show course as a modal (this is cleaner), or
• change search parameters to (by ID and the course's ID).

Group sections in selections by course. They should probably also be collapsable with some inline statistics.

ScheduleDisplay has to convert a Schedule to a different form to easily put the table cells in the <table>.

Maybe just put a function that does the lookup.

Ability to pin/save schedules, change selections, pin/save some more, then click somewhere for "📌 Pinned/Saved Schedules" and maybe bring up a modal to view them.

• UF APIs
• UF_SOC, Generator, etc.

-Learn the gator-evals API and figure out what data we can pull from it
-Entire project depends on the data we can pull so this is a fairly important step

Caches courses to provide faster responses to queries.

• Searching by instructor (last name) (done
• Section ID