Details of request “Dentistry - Admission Statistics and Selection Process

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
19263  sent  2016-11-14 17:18:19 +1100  waiting_response  2016-11-14 17:18:19 +1100  waiting_response  outgoing  
19300  response  2016-11-15 11:40:40 +1100    2016-11-19 19:48:13 +1100  waiting_response  incoming  
19603  followup_sent  2016-11-19 19:48:09 +1100        outgoing  
19604  status_update  2016-11-19 19:48:12 +1100  waiting_response  2016-11-19 19:48:12 +1100  waiting_response   
19666  response  2016-11-22 12:01:08 +1100    2016-11-22 12:03:10 +1100  waiting_response  incoming  
19667  status_update  2016-11-22 12:03:10 +1100  waiting_response  2016-11-22 12:03:10 +1100  waiting_response   
53664  overdue  2016-12-15 00:00:00 +1100         
20867  followup_sent  2016-12-17 07:03:08 +1100        outgoing  
21254  response  2017-01-05 10:22:13 +1100    2017-01-09 08:00:38 +1100  waiting_response  incoming  
21366  status_update  2017-01-09 08:00:37 +1100  waiting_response  2017-01-09 08:00:38 +1100  waiting_response   
21418  response  2017-01-11 11:33:49 +1100    2017-01-11 11:58:56 +1100  partially_successful  incoming  
21420  status_update  2017-01-11 11:58:55 +1100  partially_successful  2017-01-11 11:58:55 +1100  partially_successful   
26765  response  2017-06-15 12:31:42 +1000    2017-06-19 09:13:14 +1000  partially_successful  incoming  
26815  status_update  2017-06-19 09:13:14 +1000  partially_successful  2017-06-19 09:13:14 +1000  partially_successful   
27472  response  2017-07-13 16:31:06 +1000        incoming  
27752  response  2017-07-27 16:32:03 +1000    2017-08-07 08:43:37 +1000  partially_successful  incoming  
27984  status_update  2017-08-07 08:43:36 +1000  partially_successful  2017-08-07 08:43:37 +1000  partially_successful   
28500  response  2017-08-10 16:31:57 +1000    2017-10-05 12:56:56 +1100  partially_successful  incoming  
29711  status_update  2017-10-05 12:56:56 +1100  partially_successful  2017-10-05 12:56:56 +1100  partially_successful   
30022  response  2017-10-12 10:31:56 +1100        incoming  
30298  response  2017-10-26 10:32:09 +1100        incoming  
30550  response  2017-11-09 09:32:44 +1100        incoming  
30728  response  2017-11-23 09:33:35 +1100        incoming  
30931  response  2017-12-07 09:32:16 +1100        incoming  
31033  response  2017-12-13 17:32:22 +1100        incoming  
31269  response  2018-01-04 15:04:57 +1100        incoming  
31521  response  2018-01-18 10:33:31 +1100        incoming  
31533  response  2018-01-19 15:09:06 +1100        incoming  
31559  response  2018-01-22 11:03:16 +1100        incoming  
31611  response  2018-01-24 17:35:22 +1100        incoming  
31683  response  2018-02-01 10:33:10 +1100        incoming  
31874  response  2018-02-14 17:31:46 +1100        incoming  
31878  response  2018-02-15 10:31:40 +1100        incoming  
32138  response  2018-03-07 17:31:47 +1100    2019-05-05 21:40:08 +1000  successful  incoming  
39934  status_update  2019-05-05 21:40:08 +1000  successful  2019-05-05 21:40:08 +1000  successful   
39935  comment  2019-05-05 21:43:32 +1000         

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.