Details of request “UNI-DSL Specification as maintained by NBN Co

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
10146 sent 2015-08-30 23:50:37 +1000 waiting_response 2015-08-30 23:50:37 +1000 waiting_response outgoing
10196 response 2015-09-04 17:03:51 +1000 2015-09-05 10:16:19 +1000 waiting_clarification incoming
10201 status_update 2015-09-05 10:16:18 +1000 waiting_clarification 2015-09-05 10:16:19 +1000 waiting_clarification
10399 followup_sent 2015-09-24 23:42:16 +1000 waiting_response 2015-09-24 23:42:17 +1000 waiting_response outgoing
10496 response 2015-10-02 16:14:55 +1000 2015-10-02 17:32:30 +1000 waiting_clarification incoming
10497 followup_sent 2015-10-02 17:32:13 +1000 outgoing
10498 status_update 2015-10-02 17:32:30 +1000 waiting_clarification 2015-10-02 17:32:30 +1000 waiting_clarification
10656 followup_sent 2015-10-14 08:50:16 +1100 waiting_response 2015-10-14 08:50:16 +1100 waiting_response outgoing
10710 response 2015-10-16 17:16:24 +1100 2015-10-28 19:44:36 +1100 waiting_response incoming
10711 comment 2015-10-16 19:51:34 +1100
10778 comment 2015-10-22 15:06:14 +1100
10873 status_update 2015-10-28 19:44:35 +1100 waiting_response 2015-10-28 19:44:36 +1100 waiting_response
11058 followup_sent 2015-11-09 20:39:46 +1100 outgoing
11244 followup_sent 2015-11-20 17:06:40 +1100 outgoing
11280 response 2015-11-23 12:51:41 +1100 2015-11-23 17:40:06 +1100 waiting_response incoming
11284 status_update 2015-11-23 17:40:05 +1100 waiting_response 2015-11-23 17:40:05 +1100 waiting_response
11407 response 2015-12-03 17:14:57 +1100 2015-12-04 18:55:10 +1100 waiting_response incoming
11411 status_update 2015-12-04 18:55:09 +1100 waiting_response 2015-12-04 18:55:10 +1100 waiting_response
11421 followup_sent 2015-12-06 18:56:55 +1100 outgoing
11552 comment 2015-12-16 09:24:18 +1100
11811 response 2016-01-05 17:53:24 +1100 2016-01-06 17:43:32 +1100 partially_successful incoming
11829 comment 2016-01-06 16:50:30 +1100
11833 status_update 2016-01-06 17:43:31 +1100 partially_successful 2016-01-06 17:43:32 +1100 partially_successful
12006 response 2016-01-17 12:01:24 +1100 2016-02-07 22:57:48 +1100 partially_successful incoming
12291 status_update 2016-02-07 22:48:16 +1100 attention_requested 2016-02-07 22:55:45 +1100 attention_requested
12293 status_update 2016-02-07 22:57:48 +1100 partially_successful 2016-02-07 22:57:48 +1100 partially_successful
12305 edit_incoming 2016-02-08 11:37:19 +1100 incoming
12306 edit 2016-02-08 11:38:16 +1100
12307 comment 2016-02-08 11:43:44 +1100
12309 edit_comment 2016-02-08 12:13:37 +1100

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.