Details of request “Cocos Keeling Island Surveillance System

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
9655 sent 2015-07-05 19:15:03 +1000 waiting_response 2015-07-05 19:15:03 +1000 waiting_response outgoing
9658 response 2015-07-06 13:10:17 +1000 2015-07-06 15:04:29 +1000 waiting_response incoming
9659 status_update 2015-07-06 15:04:29 +1000 waiting_response 2015-07-06 15:04:29 +1000 waiting_response
9665 response 2015-07-07 10:24:11 +1000 2015-07-08 14:27:16 +1000 waiting_response incoming
9679 status_update 2015-07-08 14:27:15 +1000 waiting_response 2015-07-08 14:27:16 +1000 waiting_response
9713 followup_sent 2015-07-10 12:58:38 +1000 outgoing
9729 response 2015-07-13 09:53:10 +1000 2015-07-13 10:28:31 +1000 waiting_response incoming
9730 status_update 2015-07-13 10:28:31 +1000 waiting_response 2015-07-13 10:28:31 +1000 waiting_response
9731 followup_sent 2015-07-13 10:32:02 +1000 outgoing
9760 response 2015-07-15 14:02:22 +1000 2015-08-11 11:25:06 +1000 waiting_response incoming
10008 followup_sent 2015-08-11 11:24:58 +1000 outgoing
10009 status_update 2015-08-11 11:25:06 +1000 waiting_response 2015-08-11 11:25:06 +1000 waiting_response
10010 response 2015-08-11 11:38:09 +1000 2015-08-11 11:38:51 +1000 waiting_response incoming
10011 status_update 2015-08-11 11:38:51 +1000 waiting_response 2015-08-11 11:38:51 +1000 waiting_response
10012 followup_sent 2015-08-11 11:40:06 +1000 outgoing
10126 response 2015-08-27 14:28:34 +1000 2015-08-27 18:21:54 +1000 waiting_response incoming
10131 status_update 2015-08-27 18:21:53 +1000 waiting_response 2015-08-27 18:21:53 +1000 waiting_response
10532 response 2015-10-06 14:13:27 +1100 2015-10-06 19:24:17 +1100 waiting_response incoming
10540 status_update 2015-10-06 19:24:16 +1100 waiting_response 2015-10-06 19:24:17 +1100 waiting_response
10543 status_update 2015-10-06 21:28:32 +1100 waiting_response 2015-10-06 21:28:32 +1100 waiting_response
10564 followup_sent 2015-10-08 11:55:28 +1100 outgoing
10568 response 2015-10-08 15:26:20 +1100 2015-10-09 12:01:27 +1100 waiting_response incoming
10580 status_update 2015-10-09 12:01:27 +1100 waiting_response 2015-10-09 12:01:27 +1100 waiting_response
10581 followup_sent 2015-10-09 12:08:10 +1100 outgoing
11150 edit_incoming 2015-11-14 17:43:48 +1100 incoming
11151 edit_incoming 2015-11-14 17:46:10 +1100 incoming

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.