Details of request “Correspondence with any of the terms: 'Maelstrom', 'Sequeira', 'Radio Birdman' and variations

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
37363 sent 2018-12-11 16:40:01 +1100 waiting_response 2018-12-11 16:40:01 +1100 waiting_response outgoing
37626 response 2018-12-21 23:18:48 +1100 2018-12-22 07:40:07 +1100 waiting_response incoming
37630 followup_sent 2018-12-22 07:39:40 +1100 outgoing
37631 status_update 2018-12-22 07:40:07 +1100 waiting_response 2018-12-22 07:40:07 +1100 waiting_response
37632 response 2018-12-22 07:40:10 +1100 2018-12-26 17:14:25 +1100 waiting_response incoming
37642 followup_sent 2018-12-22 09:02:47 +1100 outgoing
37643 followup_sent 2018-12-22 09:04:56 +1100 outgoing
37683 status_update 2018-12-26 17:14:25 +1100 waiting_response 2018-12-26 17:14:25 +1100 waiting_response
37969 followup_sent 2019-01-11 09:44:45 +1100 outgoing
37970 status_update 2019-01-11 09:45:19 +1100 waiting_response 2019-01-11 09:45:19 +1100 waiting_response
38212 followup_sent 2019-01-30 10:39:31 +1100 outgoing
38213 status_update 2019-01-30 10:39:52 +1100 waiting_response 2019-01-30 10:39:52 +1100 waiting_response
38218 response 2019-01-30 11:53:08 +1100 2019-01-30 11:56:03 +1100 waiting_response incoming
38219 status_update 2019-01-30 11:56:03 +1100 waiting_response 2019-01-30 11:56:03 +1100 waiting_response
38222 followup_sent 2019-01-30 12:09:22 +1100 outgoing
38225 status_update 2019-01-30 12:10:59 +1100 waiting_response 2019-01-30 12:10:59 +1100 waiting_response
38587 followup_sent 2019-02-15 15:36:39 +1100 outgoing
38588 status_update 2019-02-15 15:36:55 +1100 waiting_response 2019-02-15 15:36:55 +1100 waiting_response
38594 response 2019-02-15 15:42:15 +1100 2019-02-15 16:03:13 +1100 waiting_response incoming
38599 followup_sent 2019-02-15 16:03:08 +1100 outgoing
38600 status_update 2019-02-15 16:03:13 +1100 waiting_response 2019-02-15 16:03:13 +1100 waiting_response
38607 response 2019-02-15 16:07:27 +1100 2019-02-18 15:44:19 +1100 waiting_response incoming
38643 status_update 2019-02-18 15:44:19 +1100 waiting_response 2019-02-18 15:44:19 +1100 waiting_response
38831 response 2019-03-05 16:37:16 +1100 2019-03-19 08:20:18 +1100 waiting_response incoming
39029 status_update 2019-03-19 08:20:18 +1100 waiting_response 2019-03-19 08:20:18 +1100 waiting_response
39139 response 2019-03-26 12:38:13 +1100 2019-05-01 17:09:41 +1000 partially_successful incoming
39888 status_update 2019-05-01 17:09:41 +1000 partially_successful 2019-05-01 17:09:41 +1000 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 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.