I figure that a many-to-many relationship between User and Course is probably the best way to store previous courses; similar situation with planned courses, but I made an intermediary class (Scheduled) to keep track of the planned semester so that we can throw those courses onto a visual schedule when that gets made. Not sure what else I need to do to fully implement this; if anyone else has suggestions, drop them here.
Implemented Ashton's semester code & combined both taken and planned courses into a single relation labelled "CreditHour" (liable to change). Issue closed.
I figure that a many-to-many relationship between User and Course is probably the best way to store previous courses; similar situation with planned courses, but I made an intermediary class (Scheduled) to keep track of the planned semester so that we can throw those courses onto a visual schedule when that gets made. Not sure what else I need to do to fully implement this; if anyone else has suggestions, drop them here.