dhm116 / archangel-django Goto Github PK

The current team model is not normalized and needs to be redesigned.

I suggest:

class Team(models.Model):
  name = CharField()

class SectionTeam(models.Model):
  section = ForeignKey(CourseSection)
  team = ForeignKey(Team)

class LessonTeam(models.Model):
  lesson = ForeignKey(Lesson)
  team = ForeignKey(Team)

class TeamRoster(models.Model):
  team = ForeignKey(Team)
  user = ForeignKey(User)

This would allow a team to:

• Exist for the duration of a course
• Exist only for the duration of a lesson
• Map users to teams without duplicating data

Do we need to support teams spanning multiple lessons, but not the whole course?

When filtering results, duplicate rows can be returned when checking membership in deeply nested tables. Should use the distinct() syntax to eliminate this, however sqlite3 doesn't seem to support that feature...

May block dhm116/ArchAngel/issues/3, but could be handled on the client-side pretty easily.

A request for users returns username, email, id, groups, and the source URL. What about first/last name?