Details of request “Western Springs College Rebuild

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
15367 sent 2015-04-29 21:28:51 +1200 waiting_response 2015-04-29 21:28:51 +1200 waiting_response outgoing
15368 response 2015-04-29 21:33:59 +1200 incoming
15373 response 2015-04-30 10:23:58 +1200 2015-05-01 12:48:34 +1200 waiting_response incoming
15400 status_update 2015-05-01 12:48:34 +1200 waiting_response 2015-05-01 12:48:34 +1200 waiting_response
15969 followup_sent 2015-05-25 14:56:05 +1200 outgoing
15973 response 2015-05-25 15:55:50 +1200 2015-05-25 16:52:29 +1200 waiting_response incoming
15979 status_update 2015-05-25 16:52:29 +1200 waiting_response 2015-05-25 16:52:29 +1200 waiting_response
16049 followup_sent 2015-05-28 18:42:31 +1200 outgoing
16075 response 2015-05-29 17:05:54 +1200 2015-05-31 13:24:23 +1200 waiting_response incoming
16097 status_update 2015-05-31 13:24:23 +1200 waiting_response 2015-05-31 13:24:23 +1200 waiting_response
16190 followup_sent 2015-06-05 14:02:54 +1200 outgoing
16204 response 2015-06-05 16:41:36 +1200 2015-06-06 21:36:22 +1200 waiting_response incoming
16214 status_update 2015-06-06 21:36:22 +1200 waiting_response 2015-06-06 21:36:22 +1200 waiting_response
16392 followup_sent 2015-06-15 09:43:21 +1200 outgoing
16504 followup_sent 2015-06-18 11:11:53 +1200 outgoing
16519 comment 2015-06-18 15:31:43 +1200
16520 comment 2015-06-18 15:32:34 +1200
16541 comment 2015-06-19 10:43:54 +1200
16575 followup_sent 2015-06-22 11:33:56 +1200 outgoing
16585 response 2015-06-22 16:30:55 +1200 2015-06-22 16:47:56 +1200 waiting_response incoming
16588 status_update 2015-06-22 16:47:56 +1200 waiting_response 2015-06-22 16:47:56 +1200 waiting_response
16683 followup_sent 2015-06-26 14:05:24 +1200 outgoing
16743 comment 2015-06-29 15:58:35 +1200
16754 comment 2015-06-29 21:45:22 +1200
16812 response 2015-07-01 17:43:23 +1200 2015-07-17 14:58:54 +1200 partially_successful incoming
16844 followup_sent 2015-07-03 08:40:40 +1200 outgoing
16845 status_update 2015-07-03 08:41:06 +1200 waiting_response 2015-07-03 08:41:06 +1200 waiting_response
17087 status_update 2015-07-17 14:58:54 +1200 partially_successful 2015-07-17 14:58:54 +1200 partially_successful
17088 comment 2015-07-17 15:00:02 +1200
17089 followup_sent 2015-07-17 15:03:48 +1200 outgoing
17240 response 2015-07-24 17:18:33 +1200 2015-11-23 23:05:56 +1300 partially_successful incoming
20339 status_update 2015-11-23 23:05:55 +1300 partially_successful 2015-11-23 23:05:56 +1300 partially_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 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.