Live Scores

[goodtune]

Add a new relationship to a Match - the concept of a MatchEvent which is a means to include scores and/or dismissals.

By adding supplemental information on a different table we can have no impact on any existing processing for ladder generation (this is all triggered by signal handlers attached to the saving of the Match instance).

Finding "in progress" matches should be as simple as finding matches that should have started (Match.datetime in the past) with home_team_score and away_team_score both equal to null and the presence of a non-scoring event (ie. a "match start" event which won't affect the score calculation).

When producing a form for score input in the admin interface it can be pre-populated by with the aggregate from the live score. Scoring events that include a player (strictly a TeamAssociation) can be pre-populated into the detailed score entry.

Keep a timestamp so we can print a chronology in the web UI.

• Add MatchEvent concept
• Add protected view in front-end web application for live scorers
  • Need to be able to correct mistakes (use reversal technique so aggregations will negated)
  • Consider use of certificate based authentication – allows us to authorize device with per-device certificates
• Add admin view to edit MatchEvent instances
• Add in_progress virtual attribute to MatchQuerySet to be used in front-end views
• Update match_detail view to show list of events while the match is in_progress