Page MenuHomePhabricator

Spike: Do we need additional course properties?
Closed, DeclinedPublic

Description

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?

Event Timeline

awight created this task.Jan 14 2016, 9:16 AM
awight raised the priority of this task from to Needs Triage.
awight updated the task description. (Show Details)
awight added subscribers: Aklapper, Base, awight, StudiesWorld.
Abit set Security to None.

I am not sure what this means.

awight closed this task as Declined.Feb 17 2016, 6:49 AM
awight claimed this task.

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.