Presumably, we have different optional and required course fields, depending on course type. Should we explicitly add columns to the courses table to hold every property that can be set on a course over all course types, or should we use a flexible schema?
|Open||None||T107937 Streamline workflow for setting up groups that are not courses|
|Resolved||awight||T120510 [Epic] Implement course "type"|
|Declined||awight||T123617 Spike: Do we need additional course properties?|
My thought when creating this task was that we might need to expand the dashboard's Course class to hold more information, but this doesn't seem to be needed.
In the future I could see us wanting to do something with extra course properties, storing a diverse and interesting metadata about courses in a private Wikibase. Editathons could have an optional Location property, which would be helpful in promoting each event. Complex affiliation networks could be traversed to make related courses discoverable.