Details of request “200 Country Club Blvd

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
33106  set_embargo    2019-03-19 16:02:32 -0400         
33107  sent    2019-03-19 16:02:33 -0400  waiting_response  waiting_response  2019-03-19 16:02:33 -0400  outgoing  
33713  response    2019-03-26 13:06:57 -0400    waiting_clarification  2019-03-26 14:40:59 -0400  incoming  
33720  followup_sent    2019-03-26 14:40:55 -0400  waiting_clarification      outgoing  
33721  response    2019-03-26 14:45:49 -0400  successful  successful  2019-03-27 15:51:47 -0400  incoming  
48347  embargo_expiring    2019-06-11 00:00:00 -0400         
49838  expire_embargo    2019-06-19 00:00:13 -0400         
51765  edit metadata  allow_new_responses_from  2019-06-28 03:45:09 -0400         
51766  edit metadata  allow_new_responses_from  2019-06-28 03:45:09 -0400         
51767  edit metadata  allow_new_responses_from  2019-06-28 03:45:09 -0400         
51768  edit metadata  allow_new_responses_from  2019-06-28 03:45:09 -0400         
51769  edit metadata  allow_new_responses_from  2019-06-28 03:45:09 -0400         
51770  edit metadata  allow_new_responses_from  2019-06-28 03:45:09 -0400         
51771  edit metadata  allow_new_responses_from  2019-06-28 03:45:09 -0400         
122876  edit metadata  allow_new_responses_from  2020-03-28 03:45:14 -0400         
122877  edit metadata  allow_new_responses_from  2020-03-28 03:45:15 -0400         
122878  edit metadata  allow_new_responses_from  2020-03-28 03:45:15 -0400         
122879  edit metadata  allow_new_responses_from  2020-03-28 03:45:15 -0400         
122880  edit metadata  allow_new_responses_from  2020-03-28 03:45:15 -0400         
122881  edit metadata  allow_new_responses_from  2020-03-28 03:45:15 -0400         
122882  edit metadata  allow_new_responses_from  2020-03-28 03:45:15 -0400         
122883  edit metadata  allow_new_responses_from  2020-03-28 03:45:15 -0400         
122884  edit metadata  allow_new_responses_from  2020-03-28 03:45:15 -0400         
122885  edit metadata  allow_new_responses_from  2020-03-28 03:45:15 -0400         
122886  edit metadata  allow_new_responses_from  2020-03-28 03:45:15 -0400         
122887  edit metadata  allow_new_responses_from  2020-03-28 03:45:15 -0400         
122888  edit metadata  allow_new_responses_from  2020-03-28 03:45:15 -0400         
122889  edit metadata  allow_new_responses_from  2020-03-28 03:45:15 -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.