Details of request “28 Bayberry CT

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
29530  set_embargo    2019-02-20 15:41:03 -0500         
29531  sent    2019-02-20 15:41:04 -0500  waiting_response  waiting_response  2019-02-20 15:41:04 -0500  outgoing  
29888  response    2019-02-22 15:36:29 -0500        incoming  
30257  followup_sent    2019-02-27 13:57:20 -0500  waiting_response  waiting_response  2019-02-27 13:57:27 -0500  outgoing  
30886  overdue    2019-03-02 00:00:00 -0500         
30892  followup_sent    2019-03-02 09:58:33 -0500  partially_successful  internal_review  2019-03-02 09:58:33 -0500  outgoing  
43274  embargo_expiring    2019-05-15 00:00:00 -0400         
44566  expire_embargo    2019-05-23 00:00:09 -0400         
47586  edit metadata  allow_new_responses_from  2019-06-08 03:45:15 -0400         
47587  edit metadata  allow_new_responses_from  2019-06-08 03:45:15 -0400         
47588  edit metadata  allow_new_responses_from  2019-06-08 03:45:15 -0400         
47589  edit metadata  allow_new_responses_from  2019-06-08 03:45:15 -0400         
47590  edit metadata  allow_new_responses_from  2019-06-08 03:45:15 -0400         
47591  edit metadata  allow_new_responses_from  2019-06-08 03:45:15 -0400         
47592  edit metadata  allow_new_responses_from  2019-06-08 03:45:15 -0400         
47593  edit metadata  allow_new_responses_from  2019-06-08 03:45:15 -0400         
115781  edit metadata  allow_new_responses_from  2020-03-08 03:45:22 -0400         
115782  edit metadata  allow_new_responses_from  2020-03-08 03:45:22 -0400         
115783  edit metadata  allow_new_responses_from  2020-03-08 03:45:22 -0400         
115784  edit metadata  allow_new_responses_from  2020-03-08 03:45:22 -0400         
115785  edit metadata  allow_new_responses_from  2020-03-08 03:45:22 -0400         
115786  edit metadata  allow_new_responses_from  2020-03-08 03:45:22 -0400         
115787  edit metadata  allow_new_responses_from  2020-03-08 03:45:23 -0400         
115788  edit metadata  allow_new_responses_from  2020-03-08 03:45:23 -0400         
115789  edit metadata  allow_new_responses_from  2020-03-08 03:45:23 -0400         
115790  edit metadata  allow_new_responses_from  2020-03-08 03:45:23 -0400         
115791  edit metadata  allow_new_responses_from  2020-03-08 03:45:23 -0400         
115792  edit metadata  allow_new_responses_from  2020-03-08 03:45:23 -0400         
115793  edit metadata  allow_new_responses_from  2020-03-08 03:45:23 -0400         
115794  edit metadata  allow_new_responses_from  2020-03-08 03:45:23 -0400         
115795  edit metadata  allow_new_responses_from  2020-03-08 03:45:23 -0400         
115796  edit metadata  allow_new_responses_from  2020-03-08 03:45:23 -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.