One League API

This sandbox is intended as a collection point for code, issues, and discussion regarding the 'One League API' initiative for Drupal 7.

Current Status

Basic (ie. id/label/title only) entity types defined and created.

Goals

• To provide a single, flexible, and efficient data model and related API which can be leveraged by any sports/league related modules
• To consolidate the functionality of existing D6 league-related modules into a single D7 collection, thus reducing duplication and increasing interoperability of league related modules
• To build a strong foundation of both new and existing league-related module maintainers, building a strong pool of experience to support future enhancements, plugins, features, and support of sport/league related Drupal modules.

Features and Flexibility

The API and data model should be flexible enough to support each of the following: (Please edit the page and add your own generic feature requirements!)

• Multiple sports (Even within the same site)
• League/Conference/Division seperations (and inter-division/conference games if desired)
• Facilities tracking/assignment
• Maintaining 'Team' objects across seasons
• Flexible 'Roster' tracking, and per-game lineups
• both the 'players as users' model used in ULT, as well as the 'players as objects' model used in LeagueSite
• Tracking of team 'admin' in addition to players (and flexibility to support 'player-coaches')
• Per-sport 'positions'
• Both single game and game/set/match structures
• Tracking of both 'exhibition' and 'league' games/results
• Scoring summaries by sport
• Player Statistics by sport
• Amateur/Professional/Fantasy league setups
• Per-league administration and permissions