Details of request “Information on the Real Time Display system for bus schedules

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
13160 sent 2014-12-17 17:04:35 +1300 waiting_response 2014-12-17 17:04:35 +1300 waiting_response outgoing
13163 response 2014-12-18 08:02:38 +1300 2014-12-22 09:02:44 +1300 waiting_response incoming
13227 status_update 2014-12-22 09:02:44 +1300 waiting_response 2014-12-22 09:02:44 +1300 waiting_response
14136 response 2015-02-05 13:53:14 +1300 2015-02-05 14:32:35 +1300 waiting_response incoming
14140 status_update 2015-02-05 14:32:35 +1300 waiting_response 2015-02-05 14:32:35 +1300 waiting_response
14366 response 2015-02-17 11:50:58 +1300 2015-02-18 08:16:08 +1300 waiting_response incoming
14373 followup_sent 2015-02-18 08:15:04 +1300 outgoing
14374 status_update 2015-02-18 08:15:16 +1300 waiting_clarification 2015-02-18 08:15:16 +1300 waiting_clarification
14375 status_update 2015-02-18 08:16:07 +1300 waiting_response 2015-02-18 08:16:07 +1300 waiting_response
14392 response 2015-02-19 11:29:25 +1300 incoming
14512 response 2015-02-24 12:19:42 +1300 incoming
14513 response 2015-02-24 13:48:12 +1300 2015-02-25 09:24:31 +1300 waiting_response incoming
14530 status_update 2015-02-25 09:24:31 +1300 waiting_response 2015-02-25 09:24:31 +1300 waiting_response
14531 followup_sent 2015-02-25 09:27:29 +1300 outgoing
14532 response 2015-02-25 09:28:02 +1300 incoming
14591 response 2015-02-27 16:20:30 +1300 2015-03-03 08:22:48 +1300 partially_successful incoming
14631 status_update 2015-03-03 08:22:48 +1300 partially_successful 2015-03-03 08:22:48 +1300 partially_successful
17412 response 2015-07-31 12:52:42 +1200 2015-08-01 13:30:50 +1200 partially_successful incoming
17444 comment 2015-08-01 09:04:10 +1200
17448 status_update 2015-08-01 13:30:50 +1200 partially_successful 2015-08-01 13:30:50 +1200 partially_successful
17449 comment 2015-08-01 13:33:33 +1200
19007 destroy_incoming 2015-10-07 19:14:27 +1300
20744 destroy_incoming 2015-12-04 13:10:28 +1300
20745 destroy_incoming 2015-12-04 13:10:37 +1300
20746 edit 2015-12-04 13:11:15 +1300 partially_successful 2015-12-04 13:11:15 +1300 partially_successful
20864 destroy_incoming 2015-12-09 19:55:56 +1300
20865 edit 2015-12-09 19:56:25 +1300

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.