-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Description
While implementing #187, I realized that there was a lot of helpful course information from Hyperschedule that our database currently can not store.
- course code
this could be useful for figuring out whether we already imported a course via Hyperschedule, since some courses can have different course codes but the same name - course description
- course instructor name(s) (related: see resource teacher attribute #128)
Currently, we only store the course name. But we should consider storing this information in our database, too.
Metadata
Metadata
Assignees
Labels
No labels