Details of request “Source of data for table in 2015 annual report

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
11708  sent  2015-12-27 21:23:00 +1100  waiting_response  2015-12-27 21:23:00 +1100  waiting_response  outgoing  
11709  response  2015-12-27 21:23:24 +1100    2015-12-30 21:13:23 +1100  waiting_response  incoming  
11734  status_update  2015-12-30 21:13:23 +1100  waiting_response  2015-12-30 21:13:23 +1100  waiting_response   
11966  response  2016-01-14 15:20:02 +1100    2016-01-14 18:07:40 +1100  waiting_response  incoming  
11970  status_update  2016-01-14 18:07:40 +1100  waiting_response  2016-01-14 18:07:40 +1100  waiting_response   
11971  followup_sent  2016-01-14 18:08:19 +1100        outgoing  
11996  response  2016-01-15 14:32:18 +1100    2016-02-01 21:28:37 +1100  waiting_response  incoming  
53239  overdue  2016-01-28 00:00:00 +1100         
12216  status_update  2016-02-01 21:28:36 +1100  waiting_response  2016-02-01 21:28:37 +1100  waiting_response   
12218  followup_sent  2016-02-01 22:45:24 +1100        outgoing  
55386  very_overdue  2016-02-26 00:00:00 +1100         
12673  response  2016-02-26 09:55:37 +1100    2016-03-05 22:39:11 +1100  rejected  incoming  
12987  status_update  2016-03-05 22:39:11 +1100  rejected  2016-03-05 22:39:11 +1100  rejected   

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.