Details of request “Call Logs of Multiple Incidents

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
40276 sent 2017-05-20 19:27:08 +1200 waiting_response 2017-05-20 19:27:08 +1200 waiting_response outgoing
40277 response 2017-05-20 19:33:01 +1200 incoming
40278 response 2017-05-20 19:33:03 +1200 2017-05-20 23:57:23 +1200 waiting_response incoming
40279 followup_sent 2017-05-20 23:57:20 +1200 outgoing
40280 status_update 2017-05-20 23:57:23 +1200 waiting_response 2017-05-20 23:57:23 +1200 waiting_response
40281 response 2017-05-21 00:03:01 +1200 2017-05-21 18:40:43 +1200 waiting_response incoming
40284 followup_sent 2017-05-21 18:40:40 +1200 outgoing
40285 status_update 2017-05-21 18:40:43 +1200 waiting_response 2017-05-21 18:40:43 +1200 waiting_response
40286 response 2017-05-21 18:43:01 +1200 2017-05-21 22:54:42 +1200 waiting_response incoming
40288 status_update 2017-05-21 22:54:42 +1200 waiting_response 2017-05-21 22:54:42 +1200 waiting_response
40296 response 2017-05-22 09:23:01 +1200 incoming
40297 response 2017-05-22 09:23:03 +1200 incoming
40298 response 2017-05-22 09:23:05 +1200 incoming
40299 response 2017-05-22 09:53:01 +1200 incoming
40305 response 2017-05-22 12:43:02 +1200 incoming
40306 response 2017-05-22 12:53:01 +1200 incoming
40307 response 2017-05-22 12:53:03 +1200 incoming
40309 response 2017-05-22 13:03:03 +1200 incoming
40310 response 2017-05-22 13:13:02 +1200 incoming
40314 response 2017-05-22 14:03:02 +1200 2017-05-22 15:36:52 +1200 waiting_response incoming
40321 status_update 2017-05-22 15:36:52 +1200 waiting_response 2017-05-22 15:36:52 +1200 waiting_response
40429 response 2017-05-23 08:43:01 +1200 2017-05-23 20:10:39 +1200 waiting_response incoming
40466 status_update 2017-05-23 20:10:39 +1200 waiting_response 2017-05-23 20:10:39 +1200 waiting_response
40673 response 2017-05-30 11:00:20 +1200 incoming
40678 response 2017-05-30 12:40:21 +1200 incoming
40679 response 2017-05-30 12:50:20 +1200 2017-05-30 23:07:05 +1200 partially_successful incoming
40704 status_update 2017-05-30 23:07:05 +1200 partially_successful 2017-05-30 23:07:05 +1200 partially_successful
40806 response 2017-06-02 11:21:53 +1200 2017-06-03 18:01:22 +1200 waiting_response incoming
40832 status_update 2017-06-03 18:01:22 +1200 waiting_response 2017-06-03 18:01:22 +1200 waiting_response
40833 followup_sent 2017-06-03 18:02:55 +1200 outgoing
40834 response 2017-06-03 18:11:53 +1200 incoming
40835 response 2017-06-03 18:11:55 +1200 2017-06-04 19:10:50 +1200 waiting_response incoming
40845 status_update 2017-06-04 19:10:50 +1200 waiting_response 2017-06-04 19:10:50 +1200 waiting_response
40913 response 2017-06-06 12:11:01 +1200 2017-06-06 19:29:52 +1200 waiting_response incoming
40946 status_update 2017-06-06 19:29:52 +1200 waiting_response 2017-06-06 19:29:52 +1200 waiting_response
41447 followup_sent 2017-06-20 23:11:25 +1200 outgoing
41448 response 2017-06-20 23:21:01 +1200 incoming
41455 response 2017-06-21 11:41:01 +1200 2017-06-21 21:07:43 +1200 partially_successful incoming
41488 followup_sent 2017-06-21 21:07:22 +1200 outgoing
41489 status_update 2017-06-21 21:07:43 +1200 partially_successful 2017-06-21 21:07:43 +1200 partially_successful
41746 response 2017-06-28 14:09:20 +1200 2017-06-28 20:23:38 +1200 successful incoming
41769 status_update 2017-06-28 20:23:38 +1200 successful 2017-06-28 20:23:38 +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.