Details of request “Distance to the Node

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
61957  sent  2021-05-06 10:00:41 +1000  waiting_response  2021-05-06 10:00:41 +1000  waiting_response  outgoing  
61958  response  2021-05-06 10:30:16 +1000    2021-05-10 16:09:05 +1000  waiting_response  incoming  
62244  status_update  2021-05-10 16:09:05 +1000  waiting_response  2021-05-10 16:09:05 +1000  waiting_response   
62846  response  2021-05-20 15:16:17 +1000    2021-05-31 07:32:11 +1000  waiting_clarification  incoming  
63239  followup_sent  2021-05-31 07:32:02 +1000        outgoing  
63240  status_update  2021-05-31 07:32:11 +1000  waiting_clarification  2021-05-31 07:32:11 +1000  waiting_clarification   
63241  response  2021-05-31 09:11:57 +1000    2021-06-04 07:23:03 +1000  waiting_response  incoming  
63568  status_update  2021-06-04 07:23:03 +1000  waiting_response  2021-06-04 07:23:03 +1000  waiting_response   
63817  overdue  2021-06-09 00:00:00 +1000         
65261  response  2021-06-29 08:56:23 +1000    2021-07-14 07:31:42 +1000  rejected  incoming  
66128  status_update  2021-07-14 07:31:41 +1000  rejected  2021-07-14 07:31:42 +1000  rejected   
78672  edit  2022-01-14 03:45:15 +1100         
78673  edit  2022-01-14 03:45:15 +1100         
78674  edit  2022-01-14 03:45:15 +1100         
78675  edit  2022-01-14 03:45:15 +1100         
78676  edit  2022-01-14 03:45:15 +1100         
78677  edit  2022-01-14 03:45:15 +1100         
78678  edit  2022-01-14 03:45:16 +1100         
78679  edit  2022-01-14 03:45:16 +1100         
78680  edit  2022-01-14 03:45:16 +1100         
78681  edit  2022-01-14 03:45:16 +1100         
78682  edit  2022-01-14 03:45:16 +1100         
169086  edit  2023-07-14 03:45:26 +1000         
169087  edit  2023-07-14 03:45:26 +1000         
169088  edit  2023-07-14 03:45:26 +1000         
169089  edit  2023-07-14 03:45:26 +1000         
169090  edit  2023-07-14 03:45:26 +1000         
169091  edit  2023-07-14 03:45:26 +1000         
169092  edit  2023-07-14 03:45:26 +1000         
169093  edit  2023-07-14 03:45:26 +1000         
169094  edit  2023-07-14 03:45:26 +1000         
169095  edit  2023-07-14 03:45:26 +1000         
169096  edit  2023-07-14 03:45:26 +1000         
169097  edit  2023-07-14 03:45:26 +1000         
169098  edit  2023-07-14 03:45:26 +1000         
169099  edit  2023-07-14 03:45:26 +1000         
169100  edit  2023-07-14 03:45:26 +1000         
169101  edit  2023-07-14 03:45:26 +1000         
169102  edit  2023-07-14 03:45:26 +1000         
169103  edit  2023-07-14 03:45:26 +1000         
169104  edit  2023-07-14 03:45:26 +1000         
169105  edit  2023-07-14 03:45:26 +1000         
169106  edit  2023-07-14 03:45:26 +1000         
169107  edit  2023-07-14 03:45:26 +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.