Details of request “Correspondence Related to “The Juice Media”

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
29332  sent  2017-09-09 22:34:41 +1000  waiting_response  2017-09-09 22:34:42 +1000  waiting_response  outgoing  
29352  response  2017-09-11 16:40:00 +1000    2017-09-11 16:42:41 +1000  waiting_clarification  incoming  
29353  status_update  2017-09-11 16:42:41 +1000  waiting_clarification  2017-09-11 16:42:41 +1000  waiting_clarification   
29354  followup_sent  2017-09-11 16:48:11 +1000  waiting_response  2017-09-11 16:48:11 +1000  waiting_response  outgoing  
29599  response  2017-09-28 13:31:31 +1000    2017-09-28 14:06:32 +1000  waiting_clarification  incoming  
29601  status_update  2017-09-28 14:06:32 +1000  waiting_clarification  2017-09-28 14:06:32 +1000  waiting_clarification   
29602  followup_sent  2017-09-28 14:07:43 +1000  waiting_response  2017-09-28 14:07:43 +1000  waiting_response  outgoing  
29606  response  2017-09-28 15:01:25 +1000    2017-09-28 15:07:31 +1000  waiting_clarification  incoming  
29607  status_update  2017-09-28 15:07:31 +1000  waiting_clarification  2017-09-28 15:07:31 +1000  waiting_clarification   
29608  followup_sent  2017-09-28 15:07:56 +1000  waiting_response  2017-09-28 15:07:56 +1000  waiting_response  outgoing  
29747  response  2017-10-05 15:56:20 +1100    2017-10-09 09:01:11 +1100  waiting_clarification  incoming  
29815  status_update  2017-10-09 09:01:10 +1100  waiting_clarification  2017-10-09 09:01:10 +1100  waiting_clarification   
29816  followup_sent  2017-10-09 09:03:57 +1100  waiting_response  2017-10-09 09:03:57 +1100  waiting_response  outgoing  
29822  response  2017-10-09 12:11:16 +1100    2017-10-09 14:30:59 +1100  waiting_clarification  incoming  
29855  status_update  2017-10-09 14:30:59 +1100  waiting_clarification  2017-10-09 14:30:59 +1100  waiting_clarification   
29856  followup_sent  2017-10-09 14:33:38 +1100  waiting_response  2017-10-09 14:33:38 +1100  waiting_response  outgoing  
29961  response  2017-10-11 12:07:09 +1100        incoming  
30100  response  2017-10-16 16:21:43 +1100    2017-10-16 18:52:22 +1100  waiting_clarification  incoming  
30105  status_update  2017-10-16 18:52:22 +1100  waiting_clarification  2017-10-16 18:52:22 +1100  waiting_clarification   
30106  followup_sent  2017-10-16 18:52:49 +1100  waiting_response  2017-10-16 18:52:49 +1100  waiting_response  outgoing  
30116  response  2017-10-17 09:09:37 +1100    2017-10-17 09:38:28 +1100  waiting_response  incoming  
30120  status_update  2017-10-17 09:38:28 +1100  waiting_response  2017-10-17 09:38:28 +1100  waiting_response   
30123  response  2017-10-17 10:27:49 +1100    2017-10-28 10:52:08 +1100  waiting_response  incoming  
30343  status_update  2017-10-28 10:52:08 +1100  waiting_response  2017-10-28 10:52:08 +1100  waiting_response   
54146  overdue  2017-11-16 00:00:00 +1100         
30829  response  2017-11-30 15:36:18 +1100    2017-12-10 17:05:37 +1100  partially_successful  incoming  
30972  status_update  2017-12-10 17:05:37 +1100  partially_successful  2017-12-10 17:05:37 +1100  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.