"Roster" Entity

The ‘roster’ entity represents a list of the players associated with a given team.

Typically, a roster should be attached to a team ‘Instance’, as opposed to a team ‘definition’ ... which supports archiving of roster history.

COMMON SCHEMA

  • id: Id (primary key)
  • Schema: type: type (Active, custom, lineup, etc)
  • Schema: parent_id: Parent ID (team instance)
  • Field: Players (Should be a stored array of references, instead of individual entries for each player?)

BUNDLES

ACTIVE ROSTER

The ‘active’ roster represents the complete roster of players for a team within a given season.

  • Implements default schema

CUSTOM ROSTERS

Supports custom rosters for things like the ‘9 day injury list’

  • Implements default schema

LINEUPS

A 'lineup' represents the players on a roster which participated in a given game

  • Implements default schema, plus:
    • Field: Match_id: References the match to which the lineup is associated

FIELDS

  • Players: Contains an stored array of player references, one for each roster member
  • Match_id: References the match to which a lineup is associated

Notes

  • Need to sort out how to support/represent in-game lineup changes

Add new comment

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.