The dashboard already has a hacky notion of "legacy" courses (which are synchronized from onwiki to the dashboard, rather than from dashboard to wiki, as I vaguely understood it), those with IDs above 3,000 or something. Let's formalize this idea of course type and include it in the schema.
It makes sense to create an additional table to contain info about course types.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T107937 Streamline workflow for setting up groups that are not courses | |||
| Resolved | awight | T120510 [Epic] Implement course "type" | |||
| Declined | awight | T123616 Design course type schema | |||
| Declined | awight | T123617 Spike: Do we need additional course properties? | |||
| Resolved | Ragesoss | T123618 Migrate legacy courses to new schema | |||
| Resolved | Ragesoss | T123619 Legacy course logic must switch on new course type | |||
| Resolved | Abit | T125724 Spike: Which wikiedu features still need to be customized for more general use? | |||
| Declined | None | T125773 Clean up and improve course type implementation | |||
| Invalid | awight | T126413 Don't restrict who can assign articles | |||
| Resolved | Ragesoss | T125780 Provide course type options when creating a new course |
We recently implemented course typing (using Rails' Single Table Inheritance):
https://github.com/WikiEducationFoundation/WikiEduDashboard/pull/603/files
It will be simple to add another type for Legacy courses, and migrate the existing ones. For Wiki Ed's purposes, and I think this should be the case for Outreach Dashboard as well, Legacy courses are deprecated.