chapter”

Event history

This table shows the technical details of the internal events that happened to this request on FYI. 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 FYI. 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 OIA 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
13356	sent	2015-01-08 21:32:41 +1300	waiting_response	2015-01-08 21:32:41 +1300	waiting_response	outgoing
13914	followup_sent	2015-01-28 16:52:27 +1300				outgoing
13974	response	2015-01-30 10:24:09 +1300		2015-01-30 10:25:17 +1300	waiting_response	incoming
13976	status_update	2015-01-30 10:25:17 +1300	waiting_response	2015-01-30 10:25:17 +1300	waiting_response
14106	response	2015-02-04 11:45:11 +1300		2015-02-04 11:54:03 +1300	partially_successful	incoming
14108	status_update	2015-02-04 11:54:03 +1300	partially_successful	2015-02-04 11:54:03 +1300	partially_successful
14110	followup_sent	2015-02-04 12:59:33 +1300				outgoing
14111	response	2015-02-04 14:10:02 +1300		2015-02-04 14:25:20 +1300	partially_successful	incoming
14112	status_update	2015-02-04 14:25:20 +1300	partially_successful	2015-02-04 14:25:20 +1300	partially_successful
14351	followup_sent	2015-02-16 16:56:17 +1300				outgoing
15726	followup_sent	2015-05-15 15:24:16 +1200				outgoing
15761	response	2015-05-18 11:15:50 +1200				incoming
15762	response	2015-05-18 11:15:53 +1200		2015-05-18 11:22:09 +1200	waiting_response	incoming
15763	followup_sent	2015-05-18 11:22:01 +1200				outgoing
15764	status_update	2015-05-18 11:22:09 +1200	waiting_response	2015-05-18 11:22:09 +1200	waiting_response
16103	followup_sent	2015-06-01 16:38:19 +1200				outgoing
16104	response	2015-06-01 16:38:52 +1200		2015-06-01 16:39:57 +1200	waiting_response	incoming
16105	status_update	2015-06-01 16:39:57 +1200	waiting_response	2015-06-01 16:39:57 +1200	waiting_response
16220	comment	2015-06-07 13:21:03 +1200
16516	response	2015-06-18 14:34:05 +1200		2015-06-18 22:02:42 +1200	successful	incoming
16531	status_update	2015-06-18 22:02:42 +1200	successful	2015-06-18 22:02:42 +1200	successful
16532	comment	2015-06-18 22:07:09 +1200

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 FYI 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.