Details of request “Second request

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
17660  sent    2018-10-24 18:46:01 -0400  waiting_response  waiting_response  2018-10-24 18:46:01 -0400  outgoing  
17764  response    2018-10-25 07:55:52 -0400    waiting_response  2018-10-29 19:59:42 -0400  incoming  
18111  status_update    2018-10-29 19:59:42 -0400  waiting_response  waiting_response  2018-10-29 19:59:42 -0400   
18614  overdue    2018-11-03 00:00:00 -0400         
18619  followup_sent    2018-11-03 09:25:38 -0400  internal_review  internal_review  2018-11-03 09:25:38 -0400  outgoing  
18620  response    2018-11-03 10:42:29 -0400    successful  2018-11-03 12:07:12 -0400  incoming  
18623  status_update  described_state  2018-11-03 12:07:11 -0400  successful  successful  2018-11-03 12:07:12 -0400   
27375  edit metadata  allow_new_responses_from  2019-02-04 03:45:08 -0500         
27376  edit metadata  allow_new_responses_from  2019-02-04 03:45:08 -0500         
27377  edit metadata  allow_new_responses_from  2019-02-04 03:45:08 -0500         
27378  edit metadata  allow_new_responses_from  2019-02-04 03:45:08 -0500         
27379  edit metadata  allow_new_responses_from  2019-02-04 03:45:09 -0500         
27380  edit metadata  allow_new_responses_from  2019-02-04 03:45:09 -0500         
27381  edit metadata  allow_new_responses_from  2019-02-04 03:45:09 -0500         
78311  edit metadata  allow_new_responses_from  2019-11-04 03:45:08 -0500         
78312  edit metadata  allow_new_responses_from  2019-11-04 03:45:08 -0500         
78313  edit metadata  allow_new_responses_from  2019-11-04 03:45:08 -0500         
78314  edit metadata  allow_new_responses_from  2019-11-04 03:45:08 -0500         
78315  edit metadata  allow_new_responses_from  2019-11-04 03:45:08 -0500         
78316  edit metadata  allow_new_responses_from  2019-11-04 03:45:08 -0500         
78317  edit metadata  allow_new_responses_from  2019-11-04 03:45:08 -0500         
78318  edit metadata  allow_new_responses_from  2019-11-04 03:45:08 -0500         
78319  edit metadata  allow_new_responses_from  2019-11-04 03:45:08 -0500         
78320  edit metadata  allow_new_responses_from  2019-11-04 03:45:08 -0500         
78321  edit metadata  allow_new_responses_from  2019-11-04 03:45:08 -0500         
78322  edit metadata  allow_new_responses_from  2019-11-04 03:45:09 -0500         
78323  edit metadata  allow_new_responses_from  2019-11-04 03:45:09 -0500         
78324  edit metadata  allow_new_responses_from  2019-11-04 03:45:09 -0500         

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.