How to prevent multiple uploads of archived traces

[dnesbitt61]

A potential problem with a central Datastore shared by numerous providers could be that archived data could be uploaded numerous times - thus leading to over-weighting of statistics from that set of archived trace data.

There does not seem to be a way to identify any single report as being uploaded previously (especially since we want to maintain privacy).

One possible protection could be to have an extra control at the data provider key (or Id) level that would reject data over X days old. For some initial period, a data provider would be permitted to upload archived statistics. After that initial period only "recent" traces would be permitted. This might require some level of coordination between the Datastore maintainer and the data provider.