Details of request “Partnerships, engagement or other requests for access to images from home surveillance devices

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
41473  sent  2019-08-30 15:57:25 +1000  waiting_response  2019-08-30 15:57:25 +1000  waiting_response  outgoing  
41474  response  2019-08-30 15:57:50 +1000    2019-08-30 15:59:25 +1000  waiting_response  incoming  
41476  status_update  2019-08-30 15:59:25 +1000  waiting_response  2019-08-30 15:59:25 +1000  waiting_response   
41501  response  2019-09-02 08:50:39 +1000    2019-09-03 11:38:32 +1000  waiting_response  incoming  
41527  status_update  2019-09-03 11:38:32 +1000  waiting_response  2019-09-03 11:38:32 +1000  waiting_response   
41735  response  2019-09-17 13:48:33 +1000    2019-09-29 20:15:13 +1000  waiting_response  incoming  
41900  status_update  2019-09-29 20:15:13 +1000  waiting_response  2019-09-29 20:15:13 +1000  waiting_response   
41901  followup_sent  2019-09-29 20:16:35 +1000        outgoing  
41902  response  2019-09-29 20:17:03 +1000    2019-10-01 10:29:16 +1000  waiting_response  incoming  
41929  status_update  2019-10-01 10:29:16 +1000  waiting_response  2019-10-01 10:29:16 +1000  waiting_response   
54664  overdue  2019-10-02 00:00:00 +1000         
42555  response  2019-10-27 11:54:35 +1100        incoming  
42726  response  2019-11-01 15:27:21 +1100        incoming  
42869  response  2019-11-07 09:45:27 +1100    2020-06-09 10:22:26 +1000  waiting_response  incoming  
46866  status_update  2020-06-09 10:22:26 +1000  waiting_response  2020-06-09 10:22:26 +1000  waiting_response   
46867  followup_sent  2020-06-09 10:24:36 +1000  internal_review  2020-06-09 10:24:36 +1000  internal_review  outgoing  
46868  response  2020-06-09 10:25:43 +1000        incoming  
46873  response  2020-06-09 10:53:02 +1000    2020-06-09 12:37:20 +1000  successful  incoming  
46884  status_update  2020-06-09 12:37:20 +1000  successful  2020-06-09 12:37:20 +1000  successful   
98793  edit  2022-06-10 03:45:18 +1000         
98794  edit  2022-06-10 03:45:18 +1000         
98795  edit  2022-06-10 03:45:18 +1000         
98796  edit  2022-06-10 03:45:18 +1000         
98797  edit  2022-06-10 03:45:19 +1000         
98798  edit  2022-06-10 03:45:19 +1000         
98799  edit  2022-06-10 03:45:19 +1000         
98800  edit  2022-06-10 03:45:19 +1000         
98801  edit  2022-06-10 03:45:19 +1000         
98802  edit  2022-06-10 03:45:19 +1000         
98803  edit  2022-06-10 03:45:19 +1000         
98804  edit  2022-06-10 03:45:19 +1000         
98805  edit  2022-06-10 03:45:19 +1000         
98806  edit  2022-06-10 03:45:19 +1000         
98807  edit  2022-06-10 03:45:19 +1000         
98808  edit  2022-06-10 03:45:19 +1000         
98809  edit  2022-06-10 03:45:19 +1000         
98810  edit  2022-06-10 03:45:19 +1000         
98811  edit  2022-06-10 03:45:19 +1000         

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.