Details of request “Server log files

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
15868 sent 2016-08-10 09:41:04 +1000 waiting_response 2016-08-10 09:41:05 +1000 waiting_response outgoing
15890 response 2016-08-11 14:39:18 +1000 incoming
16030 response 2016-08-19 17:14:24 +1000 2016-08-24 15:19:34 +1000 waiting_clarification incoming
16123 followup_sent 2016-08-24 15:19:26 +1000 outgoing
16124 status_update 2016-08-24 15:19:33 +1000 waiting_clarification 2016-08-24 15:19:34 +1000 waiting_clarification
16259 followup_sent 2016-08-31 13:23:38 +1000 waiting_response 2016-08-31 13:23:38 +1000 waiting_response outgoing
16344 response 2016-09-02 16:53:16 +1000 incoming
16346 comment 2016-09-02 19:22:28 +1000
16570 response 2016-09-13 16:48:52 +1000 2016-09-19 12:07:45 +1000 waiting_clarification incoming
16731 status_update 2016-09-19 12:07:44 +1000 waiting_clarification 2016-09-19 12:07:45 +1000 waiting_clarification
16733 followup_sent 2016-09-19 12:18:56 +1000 waiting_response 2016-09-19 12:18:56 +1000 waiting_response outgoing
16852 response 2016-09-21 09:16:43 +1000 2016-09-21 14:42:17 +1000 waiting_response incoming
16890 followup_sent 2016-09-21 14:42:10 +1000 outgoing
16891 status_update 2016-09-21 14:42:17 +1000 waiting_response 2016-09-21 14:42:17 +1000 waiting_response
17296 response 2016-10-06 17:15:03 +1100 2016-10-07 08:59:33 +1100 waiting_response incoming
17301 status_update 2016-10-07 08:59:33 +1100 waiting_response 2016-10-07 08:59:33 +1100 waiting_response
17317 response 2016-10-07 16:06:36 +1100 2016-11-01 17:23:25 +1100 waiting_response incoming
18267 status_update 2016-11-01 17:22:34 +1100 successful 2016-11-01 17:22:34 +1100 successful
18270 status_update 2016-11-01 17:23:25 +1100 waiting_response 2016-11-01 17:23:25 +1100 waiting_response
18287 response 2016-11-02 09:59:53 +1100 2016-11-02 10:19:11 +1100 waiting_response incoming
18288 followup_sent 2016-11-02 10:19:02 +1100 outgoing
18289 status_update 2016-11-02 10:19:10 +1100 waiting_response 2016-11-02 10:19:11 +1100 waiting_response
18929 response 2016-11-09 15:47:26 +1100 2016-11-09 18:27:13 +1100 successful incoming
18935 status_update 2016-11-09 18:27:13 +1100 successful 2016-11-09 18:27:13 +1100 successful
18936 followup_sent 2016-11-09 18:27:58 +1100 outgoing
18989 response 2016-11-10 10:09:59 +1100 2016-12-03 18:32:33 +1100 partially_successful incoming
20229 status_update 2016-12-03 18:32:33 +1100 partially_successful 2016-12-03 18:32:33 +1100 partially_successful
20230 comment 2016-12-03 18:37:02 +1100
20687 response 2016-12-13 18:01:51 +1100 2017-01-03 17:02:21 +1100 successful incoming
21198 status_update 2017-01-03 17:02:21 +1100 successful 2017-01-03 17:02:21 +1100 successful

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.