Details of request “ABC decision to apologise and reprimand Jon Faine”

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
507	sent	2013-02-15 14:09:11 +1100	waiting_response	2013-02-15 14:09:12 +1100	waiting_response	outgoing
550	response	2013-02-25 17:42:15 +1100		2013-02-26 09:49:13 +1100	waiting_clarification	incoming
551	comment	2013-02-26 09:08:43 +1100	waiting_clarification
552	followup_sent	2013-02-26 12:29:58 +1100	waiting_response	2013-02-26 12:29:59 +1100	waiting_response	outgoing
555	response	2013-02-26 15:02:17 +1100	waiting_clarification	2013-02-26 16:04:53 +1100	waiting_clarification	incoming
568	followup_sent	2013-03-02 14:38:48 +1100	waiting_response	2013-03-02 14:38:48 +1100	waiting_response	outgoing
577	response	2013-03-04 15:09:50 +1100	waiting_clarification	2013-03-04 15:13:10 +1100	waiting_clarification	incoming
579	followup_sent	2013-03-04 15:24:02 +1100	waiting_response	2013-03-04 15:24:03 +1100	waiting_response	outgoing
52781	overdue	2013-04-04 00:00:00 +1100
717	followup_sent	2013-04-04 11:52:26 +1100				outgoing
746	response	2013-04-09 17:38:33 +1000	waiting_clarification	2013-04-09 17:48:51 +1000	waiting_clarification	incoming
747	followup_sent	2013-04-09 17:53:19 +1000	waiting_response	2013-04-09 17:53:19 +1000	waiting_response	outgoing
776	followup_sent	2013-04-15 16:42:38 +1000				outgoing
806	response	2013-04-26 14:33:15 +1000	waiting_response	2013-04-26 18:09:48 +1000	waiting_response	incoming
808	followup_sent	2013-04-26 18:13:09 +1000				outgoing
814	response	2013-04-29 13:16:09 +1000	waiting_response	2013-04-29 15:31:42 +1000	waiting_response	incoming
52792	overdue	2013-05-10 00:00:00 +1000
931	response	2013-05-22 10:04:24 +1000	waiting_response	2013-05-26 09:41:50 +1000	waiting_response	incoming
55150	very_overdue	2013-06-11 00:00:00 +1000
1376	response	2013-06-26 11:49:11 +1000				incoming
1496	response	2013-07-01 14:47:09 +1000				incoming
1553	followup_sent	2013-07-04 17:31:34 +1000				outgoing
1575	response	2013-07-05 10:27:52 +1000				incoming
1579	followup_sent	2013-07-05 11:18:57 +1000				outgoing
1582	response	2013-07-05 12:00:24 +1000	successful	2013-07-30 08:23:14 +1000	successful	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.