Details of request “Damage to canopy”
Event history
This table shows the technical details of the internal events that happened to this request on Right to Know. 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 Right to Know. 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 FOI 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 |
|---|---|---|---|---|---|---|
| 13273 | sent | 2016-03-23 09:30:30 +1100 | waiting_response | 2016-03-23 09:30:31 +1100 | waiting_response | outgoing |
| 13274 | response | 2016-03-23 09:31:10 +1100 | 2016-03-23 10:00:41 +1100 | waiting_clarification | incoming | |
| 13276 | status_update | 2016-03-23 10:00:40 +1100 | waiting_clarification | 2016-03-23 10:00:40 +1100 | waiting_clarification | |
| 13277 | followup_sent | 2016-03-23 10:12:30 +1100 | waiting_response | 2016-03-23 10:12:30 +1100 | waiting_response | outgoing |
| 13278 | response | 2016-03-23 10:13:41 +1100 | incoming | |||
| 13280 | response | 2016-03-23 10:38:04 +1100 | attention_requested | 2016-03-29 11:20:31 +1100 | waiting_clarification | incoming |
| 13367 | status_update | 2016-03-29 11:20:31 +1100 | waiting_clarification | 2016-03-29 11:20:31 +1100 | waiting_clarification | |
| 13659 | response | 2016-04-08 16:02:35 +1000 | incoming | |||
| 13730 | followup_sent | 2016-04-13 16:11:38 +1000 | waiting_response | 2016-04-13 16:11:38 +1000 | waiting_response | outgoing |
| 13731 | response | 2016-04-13 16:12:09 +1000 | 2016-04-17 19:19:13 +1000 | waiting_response | incoming | |
| 13836 | status_update | 2016-04-17 19:19:13 +1000 | waiting_response | 2016-04-17 19:19:13 +1000 | waiting_response | |
| 14319 | response | 2016-05-05 09:39:27 +1000 | incoming | |||
| 14350 | followup_sent | 2016-05-06 09:07:50 +1000 | outgoing | |||
| 14351 | response | 2016-05-06 09:08:23 +1000 | 2016-05-10 09:10:58 +1000 | waiting_response | incoming | |
| 14414 | status_update | 2016-05-10 09:10:58 +1000 | waiting_response | 2016-05-10 09:10:58 +1000 | waiting_response | |
| 53360 | overdue | 2016-05-14 00:00:00 +1000 | ||||
| 14513 | followup_sent | 2016-05-15 11:54:11 +1000 | outgoing | |||
| 14514 | response | 2016-05-15 11:55:29 +1000 | 2016-05-23 21:30:17 +1000 | waiting_response | incoming | |
| 14740 | status_update | 2016-05-23 21:30:17 +1000 | waiting_response | 2016-05-23 21:30:17 +1000 | waiting_response | |
| 55475 | very_overdue | 2016-06-15 00:00:00 +1000 |
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 Right to Know 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.