Details of request “Some CO2 questions

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
73018 sent 2019-06-10 16:04:19 +1200 waiting_response 2019-06-10 16:04:19 +1200 waiting_response outgoing
73020 response 2019-06-10 16:11:45 +1200 2019-06-10 16:15:42 +1200 waiting_response incoming
73021 followup_sent 2019-06-10 16:12:49 +1200 outgoing
73022 status_update 2019-06-10 16:15:42 +1200 waiting_response 2019-06-10 16:15:42 +1200 waiting_response
73344 response 2019-06-17 16:31:43 +1200 2019-06-20 23:36:58 +1200 waiting_response incoming
73824 followup_sent 2019-06-20 23:36:48 +1200 outgoing
73825 status_update 2019-06-20 23:36:58 +1200 waiting_response 2019-06-20 23:36:58 +1200 waiting_response
73964 response 2019-06-23 20:21:43 +1200 2019-06-24 13:35:08 +1200 rejected incoming
74002 status_update 2019-06-24 13:35:08 +1200 rejected 2019-06-24 13:35:08 +1200 rejected
74004 followup_sent 2019-06-24 14:04:46 +1200 outgoing
74006 response 2019-06-24 14:21:43 +1200 2019-06-24 15:02:35 +1200 rejected incoming
74012 status_update 2019-06-24 15:02:35 +1200 rejected 2019-06-24 15:02:35 +1200 rejected
74013 followup_sent 2019-06-24 15:03:54 +1200 outgoing
74032 response 2019-06-24 17:21:02 +1200 2019-06-25 20:21:21 +1200 waiting_response incoming
74041 followup_sent 2019-06-24 21:32:22 +1200 outgoing
74090 status_update 2019-06-25 20:21:21 +1200 waiting_response 2019-06-25 20:21:21 +1200 waiting_response
74433 response 2019-07-02 17:05:41 +1200 2019-07-04 10:22:39 +1200 waiting_response incoming
74561 status_update 2019-07-04 10:22:38 +1200 waiting_response 2019-07-04 10:22:39 +1200 waiting_response
74562 followup_sent 2019-07-04 10:33:49 +1200 outgoing
74563 response 2019-07-04 10:35:41 +1200 2019-07-05 18:05:27 +1200 waiting_response incoming
75056 status_update 2019-07-05 18:05:27 +1200 waiting_response 2019-07-05 18:05:27 +1200 waiting_response
76203 followup_sent 2019-07-19 00:20:08 +1200 outgoing
76349 followup_sent 2019-07-22 13:08:16 +1200 outgoing
76355 response 2019-07-22 14:13:40 +1200 2019-07-22 15:51:15 +1200 waiting_response incoming
76363 followup_sent 2019-07-22 15:51:05 +1200 outgoing
76364 status_update 2019-07-22 15:51:15 +1200 waiting_response 2019-07-22 15:51:15 +1200 waiting_response
76598 followup_sent 2019-07-27 22:11:17 +1200 outgoing
77109 response 2019-07-30 11:49:21 +1200 2019-08-07 00:24:48 +1200 rejected incoming
77186 followup_sent 2019-07-30 23:23:32 +1200 outgoing
77187 status_update 2019-07-30 23:26:26 +1200 not_held 2019-07-30 23:26:26 +1200 not_held
77188 followup_sent 2019-07-30 23:43:15 +1200 outgoing
77215 status_update 2019-07-31 13:02:36 +1200 rejected 2019-07-31 13:02:36 +1200 rejected
77437 followup_sent 2019-08-04 17:17:01 +1200 attention_requested outgoing
77941 status_update 2019-08-07 00:24:48 +1200 rejected 2019-08-07 00:24:48 +1200 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.