30

I wanted to do some data mining on the SEDE, and I ran across a limitation which I cannot understand.

The Data Explorer table ReviewTaskResults currently contains the following information:

  • Id
  • ReviewTaskId
  • ReviewTaskResultTypeId (listed in ReviewTaskResultTypes)
  • CreationDate
  • RejectionReasonId (for suggested edits; listed in ReviewRejectionReasons)
  • Comment

However, it does not contain any information on the users casting these reviews. However, this information is already public. For recent examples, compare the results at the top of the table with the corresponding review pages on the site, which clearly attribute each review outcome to the corresponding reviewer:

Is there a privacy reason why this data was cut from the data dumps? It should be relatively straightforward to just include it in future dumps.

  • 1
    Apart from the announcement where Shog9 states to be over-cautious when leaving out the userid and one answer to support your scenario I can't find any reason this shouldn't be supported. – rene Jul 18 '16 at 14:01
  • 6
    We've taken a very cautious approach to releasing potentially private data. When it comes to SEDE, I'm always a little worried that people will create queries to target specific users for bad behavior. It's one thing to have the data public, but not easily searchable and quite another to have the data collected in one convenient location. That said, I think this is a good candidate for including in the public data and I'll see about adding it. – Jon Ericson Dec 8 '16 at 15:09
  • @JonEricson Thanks for your response. It's good to know even pretty old requests still have a chance of getting looked at. – E.P. Dec 8 '16 at 15:18
  • Related on MSO: How was the number of .015% of Meta users calculated?. – E.P. Jul 29 at 18:15

You must log in to answer this question.

Browse other questions tagged .