Details of request “Hottest 100 voting dataset”

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
7714	sent	2015-02-05 11:52:44 +1100	waiting_response	2015-02-05 11:52:44 +1100	waiting_response	outgoing
7722	comment	2015-02-05 17:05:26 +1100
7921	response	2015-02-15 15:29:33 +1100		2015-03-09 18:49:14 +1100	waiting_response	incoming
8443	status_update	2015-03-09 18:49:14 +1100	waiting_response	2015-03-09 18:49:14 +1100	waiting_response
8489	followup_sent	2015-03-10 19:03:13 +1100				outgoing
53050	overdue	2015-03-11 00:00:00 +1100
8777	response	2015-03-24 17:04:48 +1100		2015-04-13 13:59:59 +1000	rejected	incoming
8872	comment	2015-03-29 12:16:30 +1100
9051	status_update	2015-04-13 13:59:59 +1000	rejected	2015-04-13 13:59:59 +1000	rejected
9052	comment	2015-04-13 14:08:04 +1000
9061	comment	2015-04-14 22:04:37 +1000
9062	comment	2015-04-14 22:10:51 +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.