Details of request “Number of coinciding requests for OIA's

Event history

This table shows the technical details of the internal events that happened to this request on FYI. 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 FYI. 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 OIA 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
10921 sent 2014-09-14 10:32:25 +1200 waiting_response 2014-09-14 10:32:25 +1200 waiting_response outgoing
10922 response 2014-09-14 10:32:54 +1200 2014-09-14 16:38:38 +1200 waiting_response incoming
10926 status_update 2014-09-14 16:38:38 +1200 waiting_response 2014-09-14 16:38:38 +1200 waiting_response
10997 followup_sent 2014-09-16 13:16:58 +1200 outgoing
10998 response 2014-09-16 13:17:39 +1200 2014-09-16 13:24:23 +1200 waiting_response incoming
10999 status_update 2014-09-16 13:24:23 +1200 waiting_response 2014-09-16 13:24:23 +1200 waiting_response
11285 followup_sent 2014-09-29 12:20:23 +1300 outgoing
11286 response 2014-09-29 12:20:52 +1300 2014-09-29 12:24:29 +1300 waiting_response incoming
11287 status_update 2014-09-29 12:24:29 +1300 waiting_response 2014-09-29 12:24:29 +1300 waiting_response
11290 response 2014-09-29 15:05:46 +1300 2014-10-02 22:19:12 +1300 waiting_response incoming
11298 move_request 2014-09-29 21:12:44 +1300
11328 comment 2014-09-30 23:45:57 +1300
11349 comment 2014-10-01 20:30:04 +1300
11353 comment 2014-10-01 23:48:28 +1300
11395 status_update 2014-10-02 22:19:12 +1300 waiting_response 2014-10-02 22:19:12 +1300 waiting_response
11396 followup_sent 2014-10-02 22:23:10 +1300 outgoing
11674 response 2014-10-16 09:29:45 +1300 2014-10-16 09:46:40 +1300 waiting_response incoming
11675 status_update 2014-10-16 09:46:40 +1300 waiting_response 2014-10-16 09:46:40 +1300 waiting_response
11676 comment 2014-10-16 10:41:23 +1300
11677 comment 2014-10-16 10:45:09 +1300
11743 comment 2014-10-17 12:23:16 +1300
11898 response 2014-10-24 16:15:49 +1300 2014-10-24 16:31:21 +1300 waiting_response incoming
11900 status_update 2014-10-24 16:31:20 +1300 waiting_response 2014-10-24 16:31:21 +1300 waiting_response
11932 followup_sent 2014-10-28 12:05:31 +1300 outgoing
12003 comment 2014-11-02 09:23:21 +1300
12006 comment 2014-11-02 13:59:47 +1300
12033 response 2014-11-03 16:36:35 +1300 2014-11-03 16:44:49 +1300 waiting_response incoming
12034 status_update 2014-11-03 16:44:49 +1300 waiting_response 2014-11-03 16:44:49 +1300 waiting_response
13178 response 2014-12-18 17:14:52 +1300 2014-12-18 17:50:55 +1300 rejected incoming
13181 followup_sent 2014-12-18 17:50:24 +1300 outgoing
13182 status_update 2014-12-18 17:50:55 +1300 rejected 2014-12-18 17:50:55 +1300 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 FYI 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.