Details of request “Information regarding the number of bus complaints involving cyclists in Wellington

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
67305 sent 2019-02-20 16:15:21 +1300 waiting_response 2019-02-20 16:15:21 +1300 waiting_response outgoing
67325 response 2019-02-21 07:05:57 +1300 2019-02-25 13:16:28 +1300 waiting_response incoming
67425 status_update 2019-02-25 13:16:28 +1300 waiting_response 2019-02-25 13:16:28 +1300 waiting_response
68751 response 2019-03-20 17:06:01 +1300 2019-03-20 18:54:43 +1300 partially_successful incoming
68754 followup_sent 2019-03-20 17:48:16 +1300 outgoing
68755 status_update 2019-03-20 17:50:35 +1300 successful 2019-03-20 17:50:35 +1300 successful
68764 status_update 2019-03-20 18:54:30 +1300 waiting_response 2019-03-20 18:54:30 +1300 waiting_response
68765 status_update 2019-03-20 18:54:43 +1300 partially_successful 2019-03-20 18:54:43 +1300 partially_successful
68766 followup_sent 2019-03-20 18:58:21 +1300 outgoing
68950 followup_sent 2019-03-25 09:34:36 +1300 outgoing
68951 followup_sent 2019-03-25 09:34:37 +1300 outgoing
68953 response 2019-03-25 09:55:57 +1300 2019-03-25 12:45:25 +1300 waiting_response incoming
68965 status_update 2019-03-25 12:45:25 +1300 waiting_response 2019-03-25 12:45:25 +1300 waiting_response
69035 comment 2019-03-25 18:36:14 +1300
69072 followup_sent 2019-03-26 11:30:56 +1300 outgoing
69133 response 2019-03-27 10:55:57 +1300 2019-03-27 10:58:21 +1300 waiting_response incoming
69134 followup_sent 2019-03-27 10:58:17 +1300 outgoing
69135 status_update 2019-03-27 10:58:21 +1300 waiting_response 2019-03-27 10:58:21 +1300 waiting_response
69174 followup_sent 2019-03-28 08:25:53 +1300 outgoing
69181 response 2019-03-28 10:45:57 +1300 incoming
69552 response 2019-04-03 17:15:58 +1300 2019-04-04 09:49:00 +1300 waiting_response incoming
69586 followup_sent 2019-04-04 09:48:48 +1300 outgoing
69587 status_update 2019-04-04 09:49:00 +1300 waiting_response 2019-04-04 09:49:00 +1300 waiting_response
69591 followup_sent 2019-04-04 10:18:26 +1300 outgoing
69939 followup_sent 2019-04-10 18:43:28 +1200 outgoing
70075 followup_sent 2019-04-12 15:35:47 +1200 outgoing
70945 response 2019-04-30 09:11:13 +1200 2019-04-30 09:33:14 +1200 successful incoming
70949 followup_sent 2019-04-30 09:33:06 +1200 outgoing
70950 status_update 2019-04-30 09:33:14 +1200 successful 2019-04-30 09:33:14 +1200 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.