This deal with Ochs has got me thinking. . I wish I had an easy way of going back to previous seasons and players that might not have been on my team in the past, or players that I cut/traded to see how they are doing.
This line of thoguht brought me back to the "Ultimate" IFL database, which I ahve been tossing around since the beginning of the league. Due to time constraints, and my impending deployment, I may not be abnle to finish it for another 6 months. I could work on it whil edeployed, but I wouldn't be able to get it "online" until after I came back.
Some of the things that I am considering are including stats and player ratings.
For player ratings I end up coming back to three big questions that I would like feedback on.
1. How do I extract the data and still be consistent? If I use my scout for everything, the data might be off for players not on my team, and those positions that my scout isn't so good at. Would this be an acceptable variance?
2. How often do I enter a data capture? I was thinking about the following: Begin season/Draft Preview, Post Draft, After TC, After Pre season, week 6, Week 12, After Bowl Game. & numbers per year.
3. Are names ever repeated? Will their be another player called James Tart in five years? Or are all the player names unique?
And now for the stats:
1. Is it worthwhile to track every game? Or should I only track season stats with team splits. For instance a player that plays 4 games for one team and 12 for another in a single season? How useful is it to go back 3 years to a specific game to see a stat breakdown? Of course, if I do a game-by-game stats, I could then track obscure records like a QB rating when the temp is below freezing.
2. Should I put a limit on the number of players that I track? 32x53=1696 players for one year. After 4 years, the number of players that have played in a game could easily reach 2500. Besides kickers, coudl I limit to it to players who have started at least one game without a significant impact to the DB?
3. And jsut for the hell of it, what kind of obscrue stats/records would you all like to see?
This line of thoguht brought me back to the "Ultimate" IFL database, which I ahve been tossing around since the beginning of the league. Due to time constraints, and my impending deployment, I may not be abnle to finish it for another 6 months. I could work on it whil edeployed, but I wouldn't be able to get it "online" until after I came back.
Some of the things that I am considering are including stats and player ratings.
For player ratings I end up coming back to three big questions that I would like feedback on.
1. How do I extract the data and still be consistent? If I use my scout for everything, the data might be off for players not on my team, and those positions that my scout isn't so good at. Would this be an acceptable variance?
2. How often do I enter a data capture? I was thinking about the following: Begin season/Draft Preview, Post Draft, After TC, After Pre season, week 6, Week 12, After Bowl Game. & numbers per year.
3. Are names ever repeated? Will their be another player called James Tart in five years? Or are all the player names unique?
And now for the stats:
1. Is it worthwhile to track every game? Or should I only track season stats with team splits. For instance a player that plays 4 games for one team and 12 for another in a single season? How useful is it to go back 3 years to a specific game to see a stat breakdown? Of course, if I do a game-by-game stats, I could then track obscure records like a QB rating when the temp is below freezing.
2. Should I put a limit on the number of players that I track? 32x53=1696 players for one year. After 4 years, the number of players that have played in a game could easily reach 2500. Besides kickers, coudl I limit to it to players who have started at least one game without a significant impact to the DB?
3. And jsut for the hell of it, what kind of obscrue stats/records would you all like to see?

Comment