Change Details

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.

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. I suggest that the different group types be defined as broadly as practically useful, so it's easy to pick which type to use and it doesn't become a burden to program leaders.

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. I suggest that the different group types be defined as broadly as practically useful, so it's easy to pick which type to use and it doesn't become a burden to program leaders.