aston217
08-14-2013, 06:00 PM
Hey Ben (or anyone else who might know),
I've seen instructions before for removing duplicate names and things of this nature from draft classes, and I presume this is for the DB, as the game itself wouldn't have trouble with two players named the same thing.
As for what part of it, I always assumed it was for associating ratings with players. But it seems like there must be another reason too, because this doesn't seem necessary.
To combine extractor & the player_active/player_historical, you can match name, birthdate, and college, which should result in unique matches. If you're importing change tracker data, all of those fields exist in the *.db files that changetracker generates (although not in the CSVs).
Anything I am missing?
I've seen instructions before for removing duplicate names and things of this nature from draft classes, and I presume this is for the DB, as the game itself wouldn't have trouble with two players named the same thing.
As for what part of it, I always assumed it was for associating ratings with players. But it seems like there must be another reason too, because this doesn't seem necessary.
To combine extractor & the player_active/player_historical, you can match name, birthdate, and college, which should result in unique matches. If you're importing change tracker data, all of those fields exist in the *.db files that changetracker generates (although not in the CSVs).
Anything I am missing?