Details of request “OPRA Requests”

Event history

This table shows the technical details of the internal events that happened to this request on OPRAmachine. 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.

Be careful! To use this data in an honourable way, you will need a good internal knowledge of user behaviour on OPRAmachine. 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	details	created_at	described_state	calculated_state	last_described_at	link
888	sent		2017-11-20 23:19:15 -0500	waiting_response	waiting_response	2017-11-20 23:19:15 -0500	outgoing
907	status_update	described_state	2017-11-21 00:21:42 -0500	error_message	error_message	2017-11-21 00:21:42 -0500
1571	destroy_incoming		2017-11-23 10:43:34 -0500
1572	resent		2017-11-23 10:43:49 -0500	waiting_response			outgoing
3340	followup_sent		2017-12-05 23:52:49 -0500				outgoing
3345	overdue		2017-12-06 00:00:00 -0500
5904	very_overdue		2017-12-22 00:00:00 -0500
48912	status_update	described_state	2019-06-13 20:21:24 -0400	rejected	rejected	2019-06-13 20:21:24 -0400

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