Details of request “Provision of name and link to accuracy of Census data

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
15846  sent  2016-08-08 22:31:00 +1000  waiting_response  2016-08-08 22:31:00 +1000  waiting_response  outgoing  
15917  response  2016-08-15 11:21:35 +1000    2016-08-22 13:28:48 +1000  waiting_response  incoming  
16061  status_update  2016-08-22 13:28:47 +1000  waiting_response  2016-08-22 13:28:48 +1000  waiting_response   
16314  response  2016-09-01 17:02:10 +1000    2016-09-02 12:13:21 +1000  waiting_response  incoming  
16332  followup_sent  2016-09-02 12:13:10 +1000        outgoing  
16333  status_update  2016-09-02 12:13:20 +1000  waiting_response  2016-09-02 12:13:21 +1000  waiting_response   
16390  response  2016-09-05 17:21:08 +1000    2016-09-29 19:00:20 +1000  waiting_response  incoming  
53480  overdue  2016-09-08 00:00:00 +1000         
17114  status_update  2016-09-29 19:00:20 +1000  waiting_response  2016-09-29 19:00:20 +1000  waiting_response   
17228  response  2016-10-04 17:32:49 +1100        incoming  
55714  very_overdue  2016-10-08 00:00:00 +1100         
17385  response  2016-10-10 16:57:42 +1100        incoming  
17386  response  2016-10-10 16:57:43 +1100        incoming  
17387  response  2016-10-10 16:59:21 +1100        incoming  
17667  followup_sent  2016-10-22 14:41:56 +1100  internal_review  2016-10-22 14:41:56 +1100  internal_review  outgoing  
17679  response  2016-10-24 10:56:33 +1100        incoming  
18729  response  2016-11-07 15:57:04 +1100    2016-11-22 12:41:54 +1100  successful  incoming  
19671  status_update  2016-11-22 12:41:54 +1100  successful  2016-11-22 12:41:54 +1100  successful   
19672  followup_sent  2016-11-22 12:44:56 +1100        outgoing  
22945  response  2017-02-22 12:19:28 +1100        incoming  
22953  response  2017-02-22 13:25:47 +1100    2017-02-22 17:28:45 +1100  waiting_response  incoming  
22970  status_update  2017-02-22 17:28:45 +1100  waiting_response  2017-02-22 17:28:45 +1100  waiting_response   

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.