Details of request “Request for the detailed Transport Rate Calculations outlined in the GWRC 2018/19 Annual Plan

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
48239 sent 2018-01-12 09:27:34 +1300 waiting_response 2018-01-12 09:27:34 +1300 waiting_response outgoing
48240 response 2018-01-12 09:42:56 +1300 2018-01-12 09:48:32 +1300 waiting_response incoming
48241 status_update 2018-01-12 09:48:32 +1300 waiting_response 2018-01-12 09:48:32 +1300 waiting_response
49501 response 2018-02-13 16:45:34 +1300 2018-02-14 13:52:34 +1300 waiting_response incoming
49558 status_update 2018-02-14 13:52:34 +1300 waiting_response 2018-02-14 13:52:34 +1300 waiting_response
50798 followup_sent 2018-03-15 10:55:06 +1300 outgoing
51434 response 2018-04-04 16:12:04 +1200 2018-04-04 22:32:58 +1200 waiting_response incoming
51440 followup_sent 2018-04-04 22:32:46 +1200 outgoing
51441 status_update 2018-04-04 22:32:58 +1200 waiting_response 2018-04-04 22:32:58 +1200 waiting_response
52476 response 2018-04-27 16:29:30 +1200 2018-05-29 11:26:07 +1200 waiting_response incoming
54094 status_update 2018-05-29 11:26:07 +1200 waiting_response 2018-05-29 11:26:07 +1200 waiting_response
54097 followup_sent 2018-05-29 12:10:57 +1200 outgoing
54098 followup_sent 2018-05-29 12:11:00 +1200 outgoing
54166 response 2018-05-30 16:39:29 +1200 2018-05-30 16:54:35 +1200 waiting_response incoming
54171 status_update 2018-05-30 16:54:34 +1200 waiting_response 2018-05-30 16:54:35 +1200 waiting_response
55044 followup_sent 2018-06-20 11:21:22 +1200 outgoing
55109 response 2018-06-21 10:36:25 +1200 2018-06-21 11:05:56 +1200 waiting_response incoming
55112 status_update 2018-06-21 11:05:56 +1200 waiting_response 2018-06-21 11:05:56 +1200 waiting_response
55328 response 2018-06-26 15:06:25 +1200 2018-06-27 12:26:50 +1200 partially_successful incoming
55383 status_update 2018-06-27 12:26:50 +1200 partially_successful 2018-06-27 12:26:50 +1200 partially_successful
67852 response 2019-03-04 16:56:12 +1300 2019-03-04 20:06:28 +1300 waiting_response incoming
67863 status_update 2019-03-04 20:06:28 +1300 waiting_response 2019-03-04 20:06:28 +1300 waiting_response
71507 response 2019-05-10 11:28:23 +1200 2019-05-26 12:22:20 +1200 partially_successful incoming
71568 status_update 2019-05-13 10:08:00 +1200 waiting_response 2019-05-13 10:08:00 +1200 waiting_response
72196 status_update 2019-05-26 12:22:20 +1200 partially_successful 2019-05-26 12:22:20 +1200 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.