Keep up to date with Event Data

Once an Event has been created, we won't remove it from our system. However, there are some circumstances where we may edit it or mark it as deleted. We try to avoid editing Events once they are created but in some cases, notably Twitter, we routinely do this because of our obligations.

If you retrieve Events from Event Data, or you perform calculations based on data from Event Data, you should check back to make sure the original data hasn't changed. Examples of when you might like to check:

  • if you are publishing a research paper, make a final check before publication
  • if you producing on-going data derived from Event Data, you may want to re-check every month or so

Data can change for a number of reasons:

  • if a Tweet was deleted by its author, we are obliged to remove it from Event Data
  • if we ran a report that indicated that we produced obviously incorrect data as a result of a software bug, we may mark Events as having been deleted or edited.

When an Event is updated, we will add the an updated field, an updated-date field and an updated-reason. The updated field will have a value of:

  • deleted
  • when a Tweet is deleted. We will remove the Tweet content (tweet ID and author) but retain all other parts of the Event
  • when we identified obviously faulty data
  • edited
  • when we identified obviously faulty data but it can be corrected

For further discussion see Updates. For more details of how to do this check the Query API documentation.