Details of request “.au Domain Administration Ltd board minutes, agenda and reports

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
25419  sent  2017-05-02 11:20:50 +1000  waiting_response  2017-05-02 11:20:50 +1000  waiting_response  outgoing  
25484  response  2017-05-04 17:31:40 +1000    2017-05-04 17:44:26 +1000  waiting_response  incoming  
25485  status_update  2017-05-04 17:44:26 +1000  waiting_response  2017-05-04 17:44:26 +1000  waiting_response   
25486  followup_sent  2017-05-04 17:47:30 +1000        outgoing  
25685  response  2017-05-12 12:57:00 +1000    2017-05-15 18:02:30 +1000  waiting_response  incoming  
25822  status_update  2017-05-15 18:02:29 +1000  waiting_response  2017-05-15 18:02:30 +1000  waiting_response   
25823  followup_sent  2017-05-15 18:06:28 +1000        outgoing  
26108  response  2017-05-22 19:09:09 +1000    2017-05-24 18:14:29 +1000  waiting_response  incoming  
26185  status_update  2017-05-24 18:14:29 +1000  waiting_response  2017-05-24 18:14:29 +1000  waiting_response   
53931  overdue  2017-06-02 00:00:00 +1000         
26856  followup_sent  2017-06-19 21:51:34 +1000        outgoing  
26857  status_update  2017-06-19 21:52:12 +1000  waiting_response  2017-06-19 21:52:12 +1000  waiting_response   
26865  response  2017-06-20 10:15:51 +1000    2017-06-20 10:26:45 +1000  waiting_response  incoming  
26868  status_update  2017-06-20 10:26:45 +1000  waiting_response  2017-06-20 10:26:45 +1000  waiting_response   
55833  very_overdue  2017-07-04 00:00:00 +1000         
27267  followup_sent  2017-07-04 10:56:52 +1000        outgoing  
27291  response  2017-07-04 17:16:33 +1000    2017-07-05 15:04:30 +1000  waiting_response  incoming  
27315  followup_sent  2017-07-05 15:04:16 +1000        outgoing  
27316  status_update  2017-07-05 15:04:30 +1000  waiting_response  2017-07-05 15:04:30 +1000  waiting_response   
27318  response  2017-07-05 15:29:26 +1000    2017-07-05 15:37:05 +1000  waiting_response  incoming  
27319  status_update  2017-07-05 15:37:05 +1000  waiting_response  2017-07-05 15:37:05 +1000  waiting_response   
27320  followup_sent  2017-07-05 15:44:37 +1000        outgoing  
27324  response  2017-07-05 16:52:48 +1000    2017-07-05 17:02:11 +1000  waiting_response  incoming  
27326  status_update  2017-07-05 17:02:11 +1000  waiting_response  2017-07-05 17:02:11 +1000  waiting_response   
27999  followup_sent  2017-08-07 13:09:04 +1000        outgoing  
28002  response  2017-08-07 14:29:54 +1000        incoming  
28020  response  2017-08-08 10:06:30 +1000    2017-08-09 05:11:04 +1000  successful  incoming  
28334  status_update  2017-08-09 05:11:04 +1000  successful  2017-08-09 05:11:04 +1000  successful   
28335  followup_sent  2017-08-09 05:15:20 +1000        outgoing  

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.