#3 Collect score data for players
We need to collect data for individual players so that team scores
and player stats can be generated. This is not currently scheduled
until a later release, however, it will make testing considerably
easier if implemened now.
Data should be written to the player.xml file. Each game the
player plays in should be contained in its own element, thus we
can replace each element whenever the scores for that particular
game are regenerated.
For example:
<player>
<firstName>foo</firstName>
...
<statistics>
<game id="UniqueGameID">
<cleanSheet/>
<assist>
<normalTimeMinutes>23</normalTimeMinutes>
...
<assist>
<booking>
...
</booking>
</game>
<game id="UniqueGameID">
<goalConceeded>
...
</goalConceeded>
</game>
</statistics>
</player>
At a later date we can add the unofficial/official flags here.
During testing this will be very useful if we create an XSL to
extract all this information and publish it as a table (or even excel
spreadsheet) so that Mike can then compare the auto generated
results for the whole season against the manual ones in his
spreadsheets.
Logged In: YES
user_id=88713
Basic infrastructure for this is now in place:
scores.recordPlayerScoringEvents() should record the scores in the
players database.
However, it can't do this at the moment as the scores.xml document
does not include information about the game from which the score was
extracted. This should be passed on as an attribute of the event element.
Logged In: YES
user_id=88713
The UID for the game is now recorded as an attribute of the event element.
I will now proceed with the implementation of recordPlayerScoringEvents()