Details of request “Abhorrent Violent Material Act

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
46863  sent  2020-06-08 21:38:34 +1000  waiting_response  2020-06-08 21:38:34 +1000  waiting_response  outgoing  
46909  response  2020-06-10 11:29:27 +1000    2020-06-15 18:52:46 +1000  waiting_clarification  incoming  
47006  status_update  2020-06-15 18:52:46 +1000  waiting_clarification  2020-06-15 18:52:46 +1000  waiting_clarification   
47016  response  2020-06-16 12:29:03 +1000    2020-06-16 15:52:30 +1000  waiting_response  incoming  
47021  status_update  2020-06-16 15:52:30 +1000  waiting_response  2020-06-16 15:52:30 +1000  waiting_response   
47136  response  2020-06-19 16:23:06 +1000    2020-07-14 10:37:17 +1000  waiting_response  incoming  
54922  overdue  2020-07-09 00:00:00 +1000         
47818  comment  2020-07-14 10:37:11 +1000         
47819  status_update  2020-07-14 10:37:17 +1000  waiting_response  2020-07-14 10:37:17 +1000  waiting_response   
48641  response  2020-08-07 10:41:13 +1000    2020-11-06 15:25:14 +1100  successful  incoming  
51246  status_update  2020-11-06 15:25:14 +1100  successful  2020-11-06 15:25:14 +1100  successful   
62000  edit  2021-05-07 03:45:11 +1000         
62001  edit  2021-05-07 03:45:11 +1000         
62002  edit  2021-05-07 03:45:11 +1000         
62003  edit  2021-05-07 03:45:11 +1000         
62004  edit  2021-05-07 03:45:11 +1000         
62005  edit  2021-05-07 03:45:11 +1000         
62006  edit  2021-05-07 03:45:11 +1000         
62007  edit  2021-05-07 03:45:11 +1000         
62008  edit  2021-05-07 03:45:11 +1000         
62009  edit  2021-05-07 03:45:11 +1000         
62010  edit  2021-05-07 03:45:11 +1000         
67221  comment  2021-07-26 03:49:56 +1000         
124172  edit  2022-11-07 03:45:16 +1100         
124173  edit  2022-11-07 03:45:16 +1100         
124174  edit  2022-11-07 03:45:16 +1100         
124175  edit  2022-11-07 03:45:16 +1100         
124176  edit  2022-11-07 03:45:16 +1100         
124177  edit  2022-11-07 03:45:16 +1100         
124178  edit  2022-11-07 03:45:16 +1100         
124179  edit  2022-11-07 03:45:16 +1100         
124180  edit  2022-11-07 03:45:16 +1100         
124181  edit  2022-11-07 03:45:16 +1100         
124182  edit  2022-11-07 03:45:16 +1100         
124183  edit  2022-11-07 03:45:17 +1100         
124184  edit  2022-11-07 03:45:17 +1100         
124185  edit  2022-11-07 03:45:17 +1100         
124186  edit  2022-11-07 03:45:17 +1100         
124187  edit  2022-11-07 03:45:17 +1100         
124188  edit  2022-11-07 03:45:17 +1100         
124189  edit  2022-11-07 03:45:17 +1100         
124190  edit  2022-11-07 03:45:17 +1100         
124191  edit  2022-11-07 03:45:17 +1100         
124192  edit  2022-11-07 03:45:17 +1100         
124193  edit  2022-11-07 03:45:17 +1100         
124194  edit  2022-11-07 03:45:17 +1100         

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.