Details of request “Overdoses or Possible Overdoses

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
22949  sent    2018-12-28 20:30:15 -0500  waiting_response  waiting_response  2018-12-28 20:30:15 -0500  outgoing  
22950  response    2018-12-28 20:30:29 -0500    waiting_response  2019-01-09 23:10:42 -0500  incoming  
24128  status_update    2019-01-09 23:10:41 -0500  waiting_response  waiting_response  2019-01-09 23:10:42 -0500   
24176  overdue    2019-01-10 00:00:00 -0500         
26624  very_overdue    2019-01-30 00:00:00 -0500         
26822  followup_sent    2019-01-31 20:29:00 -0500  internal_review  internal_review  2019-01-31 20:29:00 -0500  outgoing  
27434  response    2019-02-04 09:49:20 -0500    successful  2019-02-04 13:26:04 -0500  incoming  
27476  status_update  described_state  2019-02-04 13:26:04 -0500  successful  successful  2019-02-04 13:26:04 -0500   
40221  edit metadata  allow_new_responses_from  2019-05-05 03:45:08 -0400         
40222  edit metadata  allow_new_responses_from  2019-05-05 03:45:08 -0400         
40223  edit metadata  allow_new_responses_from  2019-05-05 03:45:08 -0400         
40224  edit metadata  allow_new_responses_from  2019-05-05 03:45:08 -0400         
40225  edit metadata  allow_new_responses_from  2019-05-05 03:45:08 -0400         
40226  edit metadata  allow_new_responses_from  2019-05-05 03:45:08 -0400         
40227  edit metadata  allow_new_responses_from  2019-05-05 03:45:08 -0400         
40228  edit metadata  allow_new_responses_from  2019-05-05 03:45:08 -0400         
102945  edit metadata  allow_new_responses_from  2020-02-05 03:45:09 -0500         
102946  edit metadata  allow_new_responses_from  2020-02-05 03:45:09 -0500         
102947  edit metadata  allow_new_responses_from  2020-02-05 03:45:09 -0500         
102948  edit metadata  allow_new_responses_from  2020-02-05 03:45:09 -0500         
102949  edit metadata  allow_new_responses_from  2020-02-05 03:45:09 -0500         
102950  edit metadata  allow_new_responses_from  2020-02-05 03:45:09 -0500         
102951  edit metadata  allow_new_responses_from  2020-02-05 03:45:09 -0500         
102952  edit metadata  allow_new_responses_from  2020-02-05 03:45:10 -0500         
102953  edit metadata  allow_new_responses_from  2020-02-05 03:45:10 -0500         
102954  edit metadata  allow_new_responses_from  2020-02-05 03:45:10 -0500         
102955  edit metadata  allow_new_responses_from  2020-02-05 03:45:10 -0500         
102956  edit metadata  allow_new_responses_from  2020-02-05 03:45:10 -0500         
102957  edit metadata  allow_new_responses_from  2020-02-05 03:45:10 -0500         
102958  edit metadata  allow_new_responses_from  2020-02-05 03:45:10 -0500         
102959  edit metadata  allow_new_responses_from  2020-02-05 03:45:10 -0500         
102960  edit metadata  allow_new_responses_from  2020-02-05 03:45:10 -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.