Details of request “Law Enforcement Request - iiNet Limited

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
6962  sent  2014-12-05 12:18:58 +1100  waiting_response  2014-12-05 12:18:58 +1100  waiting_response  outgoing  
6963  response  2014-12-05 12:19:19 +1100    2014-12-05 12:22:32 +1100  waiting_response  incoming  
6966  status_update  2014-12-05 12:22:31 +1100  waiting_response  2014-12-05 12:22:31 +1100  waiting_response   
7025  response  2014-12-11 12:35:00 +1100    2014-12-11 14:04:42 +1100  waiting_clarification  incoming  
7028  status_update  2014-12-11 14:04:42 +1100  waiting_clarification  2014-12-11 14:04:42 +1100  waiting_clarification   
7033  followup_sent  2014-12-11 16:26:53 +1100  waiting_response  2014-12-11 16:26:53 +1100  waiting_response  outgoing  
7034  response  2014-12-11 16:27:16 +1100    2014-12-12 05:46:56 +1100  waiting_response  incoming  
7035  status_update  2014-12-12 05:46:55 +1100  waiting_response  2014-12-12 05:46:55 +1100  waiting_response   
7063  response  2014-12-15 17:33:54 +1100    2014-12-15 18:17:54 +1100  waiting_response  incoming  
7066  followup_sent  2014-12-15 18:17:40 +1100        outgoing  
7067  status_update  2014-12-15 18:17:54 +1100  waiting_response  2014-12-15 18:17:54 +1100  waiting_response   
7068  response  2014-12-15 18:18:05 +1100    2014-12-15 18:18:24 +1100  waiting_response  incoming  
7070  status_update  2014-12-15 18:18:24 +1100  waiting_response  2014-12-15 18:18:24 +1100  waiting_response   
53008  overdue  2015-01-13 00:00:00 +1100         
55253  very_overdue  2015-02-11 00:00:00 +1100         
7836  response  2015-02-11 16:53:27 +1100    2015-02-11 17:28:34 +1100  waiting_response  incoming  
7843  status_update  2015-02-11 17:28:34 +1100  waiting_response  2015-02-11 17:28:34 +1100  waiting_response   
7974  response  2015-02-18 13:09:45 +1100    2015-02-18 13:59:52 +1100  waiting_response  incoming  
7978  status_update  2015-02-18 13:59:52 +1100  waiting_response  2015-02-18 13:59:52 +1100  waiting_response   
8355  response  2015-03-05 10:33:32 +1100    2015-03-09 22:33:40 +1100  waiting_response  incoming  
8448  followup_sent  2015-03-09 22:33:34 +1100        outgoing  
8449  status_update  2015-03-09 22:33:40 +1100  waiting_response  2015-03-09 22:33:40 +1100  waiting_response   
8478  response  2015-03-10 15:34:19 +1100        incoming  
8479  response  2015-03-10 15:34:19 +1100    2015-03-14 14:57:00 +1100  user_withdrawn  incoming  
8592  status_update  2015-03-14 14:57:00 +1100  user_withdrawn  2015-03-14 14:57:00 +1100  user_withdrawn   
8593  followup_sent  2015-03-14 14:57:33 +1100        outgoing  

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.