Description:

Fields:

• realplayerid - id field of the "score_realplayer" table
• firstname - first name of a real player
• middlename - middle name of a real player (can be null)
• lastname - last name of a real player
• dob - date of birth of a real player
• careerstatus - level of experience of player (class standing or years experience)

Notes:

• The "position" field needs to be moved to a separate relationship table to handle real players with multiple position eligibility. The inability for flexible real player positions was a flaw in PPS 5.0
• A decision needs to be made for handling real players as they move from fantasy game pools or across real sports. Do we create duplicate real players after graduation (such as a "College Football Darren McFadden and a "Pro Football Darren McFadden") or do they move from one real team to another real team? My inclination is that each SCORE OS implementation will have player pool data related to a particular fantasy game (college football, pro football, pro basketball) and to tie a single real player record to multiple games/sports will pose problems. Thus, you could make the argument that a real player record is tied to a particular fantasy game (college football, pro football) or a particular real sport (basketball, football). Not to mention the complications for Deion Sanders and Charlie Wards of the world who can play across multiple sports. In the instance of the Cradle-to-Grave scenario, the player pool for fantasy college football, fantasy pro football, and fantasy combined football would be three separate player pools in the system.