Currently, when a team is being updated via lpupdate ( called by update off the ./manage script ) membership.
The current data being pulled is very little, but it will be enough to prove the concept.
The data pulled is an array of POSIX dates that mark the date / time of the join to the team. I set it up as follows ( to try and make it easy to expand, when we need to )
Extra data will be pulled after the iteration is finished ( pull down lp member object and store real name for oldest member etc )
How should this be changed to fit with the database? My guess is that we should allow for general statistics, if we would hypothetically pull from other sources as well.
Currently, when a team is being updated via lpupdate ( called by update off the ./manage script ) membership.
The current data being pulled is very little, but it will be enough to prove the concept.
The data pulled is an array of POSIX dates that mark the date / time of the join to the team. I set it up as follows ( to try and make it easy to expand, when we need to )
array( { "join" : nnnn }, { "join" : nnnn }, { "join" : nnnn } );
Extra data will be pulled after the iteration is finished ( pull down lp member object and store real name for oldest member etc )
How should this be changed to fit with the database? My guess is that we should allow for general statistics, if we would hypothetically pull from other sources as well.