Details of request “Slipper summons and Minchin Protocol

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
594 sent 2013-03-06 18:57:54 +1100 attention_requested 2013-03-06 18:57:54 +1100 waiting_response outgoing
633 response 2013-03-15 17:17:15 +1100 waiting_clarification 2013-03-15 19:59:44 +1100 waiting_clarification incoming
634 followup_sent 2013-03-15 20:00:24 +1100 waiting_response 2013-03-15 20:00:26 +1100 waiting_response outgoing
653 response 2013-03-21 17:31:58 +1100 waiting_response 2013-03-25 12:49:47 +1100 waiting_response incoming
728 response 2013-04-08 11:56:15 +1000 waiting_clarification 2013-04-08 13:02:16 +1000 waiting_clarification incoming
729 followup_sent 2013-04-08 13:07:26 +1000 waiting_response 2013-04-08 13:07:26 +1000 waiting_response outgoing
749 response 2013-04-10 09:08:54 +1000 waiting_clarification 2013-04-10 10:18:48 +1000 waiting_clarification incoming
751 followup_sent 2013-04-10 10:31:00 +1000 waiting_response 2013-04-10 10:31:00 +1000 waiting_response outgoing
760 response 2013-04-11 14:33:01 +1000 waiting_response 2013-04-11 14:34:56 +1000 waiting_response incoming
783 response 2013-04-16 14:31:51 +1000 waiting_response 2013-04-20 16:24:23 +1000 waiting_response incoming
896 response 2013-05-14 13:48:38 +1000 incoming
904 followup_sent 2013-05-15 18:08:06 +1000 outgoing
905 response 2013-05-15 18:08:24 +1000 waiting_response 2013-05-19 11:59:17 +1000 waiting_response incoming
980 response 2013-06-03 16:40:07 +1000 incoming
981 response 2013-06-03 16:40:32 +1000 incoming
982 response 2013-06-03 16:40:48 +1000 incoming
983 response 2013-06-03 16:48:55 +1000 partially_successful 2013-06-28 10:10:44 +1000 partially_successful incoming
1412 comment 2013-06-28 11:49:41 +1000
1537 followup_sent 2013-07-03 09:27:13 +1000 outgoing
1538 response 2013-07-03 09:27:38 +1000 incoming
1539 response 2013-07-03 09:52:37 +1000 incoming
1569 response 2013-07-05 09:47:08 +1000 incoming
1641 followup_sent 2013-07-07 13:01:54 +1000 internal_review 2013-07-07 13:01:54 +1000 internal_review outgoing
1642 response 2013-07-07 13:02:15 +1000 internal_review 2013-07-07 13:11:02 +1000 internal_review incoming
1813 followup_sent 2013-07-14 12:20:17 +1000 internal_review 2013-07-14 12:20:17 +1000 internal_review outgoing
1814 response 2013-07-14 12:20:38 +1000 incoming
1824 response 2013-07-15 15:16:57 +1000 incoming
1826 followup_sent 2013-07-15 16:37:42 +1000 outgoing
1827 response 2013-07-15 16:38:00 +1000 incoming
1852 response 2013-07-19 11:02:40 +1000 internal_review 2013-07-23 10:22:43 +1000 internal_review incoming
2050 response 2013-08-07 13:40:22 +1000 rejected 2013-08-11 09:24:37 +1000 rejected 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.