Details of request “C.P. vs Berkeley Township

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
14277  sent    2018-08-15 14:14:27 -0400  waiting_response  waiting_response  2018-08-15 14:14:27 -0400  outgoing  
14530  response    2018-08-23 15:53:25 -0400        incoming  
14531  followup_sent    2018-08-23 16:47:56 -0400  internal_review  internal_review  2018-08-23 16:47:57 -0400  outgoing  
14551  response    2018-08-24 11:42:12 -0400    not_held  2018-08-24 19:35:09 -0400  incoming  
14567  status_update  described_state  2018-08-24 19:35:08 -0400  not_held  not_held  2018-08-24 19:35:09 -0400   
14634  response    2018-08-28 11:13:11 -0400    successful  2018-08-31 21:37:56 -0400  incoming  
14734  status_update  described_state  2018-08-31 21:37:56 -0400  successful  successful  2018-08-31 21:37:56 -0400   
20835  edit metadata  allow_new_responses_from  2018-12-02 03:45:09 -0500         
20836  edit metadata  allow_new_responses_from  2018-12-02 03:45:09 -0500         
20837  edit metadata  allow_new_responses_from  2018-12-02 03:45:09 -0500         
20838  edit metadata  allow_new_responses_from  2018-12-02 03:45:09 -0500         
20839  edit metadata  allow_new_responses_from  2018-12-02 03:45:09 -0500         
20840  edit metadata  allow_new_responses_from  2018-12-02 03:45:09 -0500         
20841  edit metadata  allow_new_responses_from  2018-12-02 03:45:09 -0500         
66334  edit metadata  allow_new_responses_from  2019-09-02 03:45:09 -0400         
66335  edit metadata  allow_new_responses_from  2019-09-02 03:45:09 -0400         
66336  edit metadata  allow_new_responses_from  2019-09-02 03:45:09 -0400         
66337  edit metadata  allow_new_responses_from  2019-09-02 03:45:09 -0400         
66338  edit metadata  allow_new_responses_from  2019-09-02 03:45:09 -0400         
66339  edit metadata  allow_new_responses_from  2019-09-02 03:45:09 -0400         
66340  edit metadata  allow_new_responses_from  2019-09-02 03:45:09 -0400         
66341  edit metadata  allow_new_responses_from  2019-09-02 03:45:09 -0400         
66342  edit metadata  allow_new_responses_from  2019-09-02 03:45:09 -0400         
66343  edit metadata  allow_new_responses_from  2019-09-02 03:45:09 -0400         
66344  edit metadata  allow_new_responses_from  2019-09-02 03:45:09 -0400         
66345  edit metadata  allow_new_responses_from  2019-09-02 03:45:09 -0400         
66346  edit metadata  allow_new_responses_from  2019-09-02 03:45:09 -0400         
66347  edit metadata  allow_new_responses_from  2019-09-02 03:45:10 -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.