Details of request “2015 Requests for Information - Apple

Event history

This table shows the technical details of the internal events that happened to this request on Right to Know. 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 Right to Know. 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 FOI 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
11979  sent  2016-01-14 22:46:40 +1100  waiting_response  2016-01-14 22:46:41 +1100  waiting_response  outgoing  
11980  response  2016-01-14 22:47:14 +1100    2016-01-14 22:53:33 +1100  waiting_response  incoming  
11981  status_update  2016-01-14 22:53:33 +1100  waiting_response  2016-01-14 22:53:33 +1100  waiting_response   
11993  response  2016-01-15 13:42:04 +1100    2016-01-16 19:17:07 +1100  waiting_response  incoming  
12003  status_update  2016-01-16 19:17:07 +1100  waiting_response  2016-01-16 19:17:07 +1100  waiting_response   
12086  response  2016-01-22 12:02:17 +1100    2016-01-22 20:22:59 +1100  waiting_clarification  incoming  
12094  status_update  2016-01-22 20:22:59 +1100  waiting_clarification  2016-01-22 20:22:59 +1100  waiting_clarification   
12095  followup_sent  2016-01-22 20:30:54 +1100  waiting_response  2016-01-22 20:30:54 +1100  waiting_response  outgoing  
12096  response  2016-01-22 20:31:33 +1100    2016-01-22 20:31:54 +1100  waiting_response  incoming  
12097  status_update  2016-01-22 20:31:54 +1100  waiting_response  2016-01-22 20:31:54 +1100  waiting_response   
12221  response  2016-02-02 12:18:27 +1100    2016-02-02 12:54:04 +1100  waiting_response  incoming  
12223  status_update  2016-02-02 12:54:04 +1100  waiting_response  2016-02-02 12:54:04 +1100  waiting_response   
12314  response  2016-02-08 15:55:28 +1100    2016-02-08 20:34:41 +1100  rejected  incoming  
12321  status_update  2016-02-08 20:34:41 +1100  rejected  2016-02-08 20:34:41 +1100  rejected   
12322  followup_sent  2016-02-08 20:45:00 +1100  internal_review  2016-02-08 20:45:00 +1100  internal_review  outgoing  
12323  response  2016-02-08 20:45:29 +1100        incoming  
12350  response  2016-02-10 09:11:19 +1100    2016-02-11 16:45:39 +1100  internal_review  incoming  
12359  status_update  2016-02-11 16:45:39 +1100  internal_review  2016-02-11 16:45:39 +1100  internal_review   
12587  response  2016-02-24 13:46:46 +1100    2016-02-26 19:41:38 +1100  internal_review  incoming  
12749  followup_sent  2016-02-26 19:41:31 +1100        outgoing  
12750  status_update  2016-02-26 19:41:38 +1100  internal_review  2016-02-26 19:41:38 +1100  internal_review   
12751  response  2016-02-26 19:42:07 +1100        incoming  
12795  response  2016-02-29 09:35:36 +1100    2016-03-04 11:00:37 +1100  internal_review  incoming  
12959  status_update  2016-03-04 11:00:37 +1100  internal_review  2016-03-04 11:00:37 +1100  internal_review   
13004  response  2016-03-07 14:54:35 +1100    2016-03-07 16:38:55 +1100  internal_review  incoming  
13007  status_update  2016-03-07 16:38:55 +1100  internal_review  2016-03-07 16:38:55 +1100  internal_review   
13008  followup_sent  2016-03-07 16:39:44 +1100        outgoing  
13104  followup_sent  2016-03-14 22:28:04 +1100        outgoing  
13105  response  2016-03-14 22:28:35 +1100        incoming  
13699  response  2016-04-12 10:46:21 +1000    2016-04-21 22:53:15 +1000  internal_review  incoming  
14020  status_update  2016-04-21 22:53:15 +1000  internal_review  2016-04-21 22:53:15 +1000  internal_review   
14873  response  2016-06-02 13:37:09 +1000    2016-07-05 21:13:32 +1000  partially_successful  incoming  
15422  status_update  2016-07-05 21:13:31 +1000  partially_successful  2016-07-05 21:13:32 +1000  partially_successful   

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 Right to Know 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.