Details of request “Process to follow to get access to CCTV footage of Train carriage for specific Date and time.”

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
38264	sent	2019-02-01 16:08:17 +1100	waiting_response	2019-02-01 16:08:17 +1100	waiting_response	outgoing
38265	response	2019-02-01 16:08:39 +1100				incoming
38356	response	2019-02-04 11:34:58 +1100		2019-02-08 12:10:32 +1100	partially_successful	incoming
38439	status_update	2019-02-08 12:10:32 +1100	partially_successful	2019-02-08 12:10:32 +1100	partially_successful
38463	response	2019-02-11 10:25:56 +1100				incoming
38464	followup_sent	2019-02-11 12:12:13 +1100				outgoing
38465	response	2019-02-11 12:12:36 +1100				incoming
38521	response	2019-02-11 17:06:28 +1100		2019-03-08 10:03:49 +1100	successful	incoming
38866	status_update	2019-03-08 10:03:49 +1100	successful	2019-03-08 10:03:49 +1100	successful

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.