Details of request 'PR Plan for Kim Dotcom Arrest'

Event history

This table shows the technical details of the internal events that happened to this request on FYI. This could be used to generate information about the speed with which authorities respond to requests, the number of requests which require a postal response and much more.

Caveat emptor! To use this data in an honourable way, you will need a good internal knowledge of user behaviour on FYI. How, why and by whom requests are categorised is not straightforward, and there will be user error and ambiguity. You will also need to understand OIA law, and the way authorities use it. Plus you'll need to be an elite statistician. Please contact us with questions.

id event_type created_at described_state last_described_at calculated_state link
2256 sent Thu Aug 09 04:51:31 UTC 2012 waiting_response Thu Aug 09 04:51:31 UTC 2012 waiting_response outgoing
2275 response Fri Aug 10 04:28:53 UTC 2012 incoming
2288 response Sun Aug 12 20:21:14 UTC 2012 incoming
2291 followup_sent Sun Aug 12 23:15:47 UTC 2012 waiting_response Sun Aug 12 23:15:54 UTC 2012 waiting_response outgoing
2293 response Sun Aug 12 23:19:34 UTC 2012 incoming
2294 response Sun Aug 12 23:20:57 UTC 2012 waiting_response Sun Aug 12 23:50:53 UTC 2012 waiting_response incoming
2642 followup_sent Mon Sep 10 22:03:04 UTC 2012 internal_review Mon Sep 10 22:03:04 UTC 2012 internal_review outgoing
2644 response Tue Sep 11 05:15:00 UTC 2012 incoming
2846 response Mon Oct 01 03:13:32 UTC 2012 Mon May 06 02:44:58 UTC 2013 successful incoming
2872 comment Tue Oct 02 23:05:13 UTC 2012 successful
4301 status_update Mon May 06 02:44:58 UTC 2013

Here described means when a user selected a status for the request, and the most recent event had its status updated to that value. calculated is then inferred by FYI for intermediate events, which weren't given an explicit description by a user. See the search tips for description of the states.

You can get this page in computer-readable format as part of the main JSON page for the request. See the API documentation.