"Team" Entity

The ‘team’ entity represents an individual team participating in a particular sports league.

COMMON SCHEMA

  • Schema: id: Id (primary key)
  • Schema: type: Type – Bundle type (‘Team Definition’, ‘Team Instance’)
  • Schema: name: Name – Team name
  • Schema: parent_id: Parent ID – Id of the parent this entry belongs to.
  • Schema: parent_type: Parent Type – Type of the parent this entry belongs to (League, Team)

BUNDLES

TEAM DEFINITION

This represents the team ‘definition’; namely the team name, location, logo, and any other information that isn’t likely to change from season to season.

  • Implements default schema, plus
    • Parent type should always be a ‘league’
  • Extendable (via fields) to provide a ‘team profile’

TEAM INSTANCE

The team ‘instance’ represents the container for an instance of a team within a given season. Typically, most references to a team will likely be to the team ‘instance’; which should pull any common information out of the parent team ‘definition’ that needs to be included.

  • Implements default schema, plus
    • Parent type should always be ‘team’

DEFINED FIELDS

n/a

ALLOWED PARENT REFERENCES

  • Team Definition -> League Container (many to one)
  • Team Instance -> Team Definition (many to one)

NOTES

  • How do we theme an entity view? (not as simple as node-type.tpl.php, I’m guessing!)

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.