Details of request “Fusion Centres

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
51580 sent 2018-04-09 10:51:50 +1200 waiting_response 2018-04-09 10:51:50 +1200 waiting_response outgoing
51582 response 2018-04-09 11:36:55 +1200 incoming
51745 response 2018-04-13 11:06:55 +1200 2018-04-13 13:37:11 +1200 waiting_response incoming
51756 status_update 2018-04-13 13:37:11 +1200 waiting_response 2018-04-13 13:37:11 +1200 waiting_response
52683 response 2018-05-03 14:29:30 +1200 2018-05-04 17:11:38 +1200 waiting_response incoming
52742 followup_sent 2018-05-04 17:11:31 +1200 outgoing
52743 status_update 2018-05-04 17:11:38 +1200 waiting_response 2018-05-04 17:11:38 +1200 waiting_response
52787 response 2018-05-07 09:29:29 +1200 2018-05-10 06:51:20 +1200 waiting_response incoming
52798 status_update 2018-05-07 10:22:49 +1200 waiting_response 2018-05-07 10:22:49 +1200 waiting_response
52946 status_update 2018-05-10 06:50:30 +1200 waiting_clarification 2018-05-10 06:50:30 +1200 waiting_clarification
52947 status_update 2018-05-10 06:51:20 +1200 waiting_response 2018-05-10 06:51:20 +1200 waiting_response
54316 response 2018-06-01 13:59:29 +1200 2018-06-01 14:07:46 +1200 waiting_response incoming
54317 status_update 2018-06-01 14:07:46 +1200 waiting_response 2018-06-01 14:07:46 +1200 waiting_response
55757 followup_sent 2018-07-02 18:17:27 +1200 outgoing
55912 response 2018-07-04 13:36:25 +1200 2018-07-04 14:11:44 +1200 waiting_response incoming
55917 followup_sent 2018-07-04 14:11:39 +1200 outgoing
55918 status_update 2018-07-04 14:11:44 +1200 waiting_response 2018-07-04 14:11:44 +1200 waiting_response
56561 response 2018-07-16 15:37:39 +1200 2018-07-21 18:26:20 +1200 waiting_response incoming
56840 status_update 2018-07-21 18:26:20 +1200 waiting_response 2018-07-21 18:26:20 +1200 waiting_response
57153 response 2018-07-27 13:17:39 +1200 2018-08-26 20:11:40 +1200 waiting_response incoming
58449 status_update 2018-08-26 20:11:40 +1200 waiting_response 2018-08-26 20:11:40 +1200 waiting_response
58450 followup_sent 2018-08-26 20:15:00 +1200 outgoing
58484 response 2018-08-27 16:51:16 +1200 incoming
58848 response 2018-09-04 16:11:34 +1200 2018-09-21 07:42:54 +1200 rejected incoming
59447 status_update 2018-09-21 07:42:54 +1200 rejected 2018-09-21 07:42:54 +1200 rejected
76362 response 2019-07-22 15:43:39 +1200 2019-07-25 08:40:58 +1200 partially_successful incoming
76469 status_update 2019-07-25 08:40:58 +1200 partially_successful 2019-07-25 08:40:58 +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.