Skip to content
This repository has been archived by the owner on Apr 7, 2020. It is now read-only.

Historical data analysis #53

Open
edward-shen opened this issue Feb 15, 2018 · 2 comments
Open

Historical data analysis #53

edward-shen opened this issue Feb 15, 2018 · 2 comments

Comments

@edward-shen
Copy link
Contributor

edward-shen commented Feb 15, 2018

A friend of mine asked to see if we could do some historical analysis and indicate on each course when they offer it. This is useful because it allows users to see and plan our their schedule, especially for courses that are only historically offered in the spring/fall.

We have banner information since 2012, so we should be able to use that.

I was thinking of something like this:
We calculate the occurrences of when that class was offered, e.g. if a class was offered 5 times in the last 6 years in the fall, we'd add "Generally offered in the fall (83.3% of the time)." If a class was offered maybe twice in the last 6 years in the summer, and always in the spring, we'd have (Historically always offered in the Spring, rarely offered in the summer (33.3% of the time)."

Alternatively, we could have a table that shows each percentage.

We'd effectively add 4-6 new fields for every course, one for each semester.

This poses some initial problems:
Will there be 3 spots for summer courses (Full summer, Summer I, Summer II)?
We'd likely need to cache banner data, because with the new API I have a feeling they're removing accessible data from the past.

@edward-shen
Copy link
Contributor Author

Solving #24 would also probably help with this.

@ryanhugh
Copy link
Owner

Sounds good to me! Once we add the ability to re-use data that we have already scraped we can load in all the data all the way back to 2012 and have everything available for processing. Lets finish #24 before this.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants