Details of request “DIBP Correspondence regarding "divestment" and "boycott"

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
10505 sent 2015-10-03 15:16:37 +1000 waiting_response 2015-10-03 15:16:37 +1000 waiting_response outgoing
10536 response 2015-10-06 15:33:32 +1100 2015-10-06 19:25:17 +1100 waiting_response incoming
10541 status_update 2015-10-06 19:25:16 +1100 waiting_response 2015-10-06 19:25:16 +1100 waiting_response
10542 followup_sent 2015-10-06 19:30:32 +1100 outgoing
10544 response 2015-10-07 08:27:36 +1100 2015-10-07 11:25:34 +1100 waiting_response incoming
10549 status_update 2015-10-07 11:25:33 +1100 waiting_response 2015-10-07 11:25:34 +1100 waiting_response
10550 followup_sent 2015-10-07 11:34:29 +1100 outgoing
10555 response 2015-10-07 17:17:20 +1100 2015-10-07 17:20:36 +1100 waiting_response incoming
10556 status_update 2015-10-07 17:20:36 +1100 waiting_response 2015-10-07 17:20:36 +1100 waiting_response
10881 response 2015-10-29 13:14:40 +1100 2015-11-02 12:50:10 +1100 waiting_response incoming
10930 status_update 2015-11-02 12:50:10 +1100 waiting_response 2015-11-02 12:50:10 +1100 waiting_response
10931 followup_sent 2015-11-02 13:01:46 +1100 outgoing
11095 followup_sent 2015-11-11 15:17:41 +1100 outgoing
11098 response 2015-11-11 17:40:37 +1100 2015-11-11 18:24:26 +1100 waiting_response incoming
11099 status_update 2015-11-11 18:24:25 +1100 waiting_response 2015-11-11 18:24:26 +1100 waiting_response
11437 followup_sent 2015-12-07 11:35:27 +1100 outgoing
11478 response 2015-12-10 11:35:55 +1100 2015-12-21 12:15:39 +1100 waiting_response incoming
11615 status_update 2015-12-21 12:15:39 +1100 waiting_response 2015-12-21 12:15:39 +1100 waiting_response
11634 comment 2015-12-21 22:22:26 +1100
11685 comment 2015-12-24 13:45:25 +1100
11686 followup_sent 2015-12-24 13:55:45 +1100 outgoing
11743 response 2015-12-31 13:46:50 +1100 2015-12-31 14:08:47 +1100 waiting_response incoming
11744 status_update 2015-12-31 14:08:47 +1100 waiting_response 2015-12-31 14:08:47 +1100 waiting_response
11745 followup_sent 2015-12-31 14:11:44 +1100 outgoing
12428 response 2016-02-17 14:50:53 +1100 2016-02-17 16:56:08 +1100 partially_successful incoming
12432 status_update 2016-02-17 16:56:07 +1100 partially_successful 2016-02-17 16:56:08 +1100 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.