Details of request “M.W. 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
14278  sent    2018-08-15 14:15:57 -0400  waiting_response  waiting_response  2018-08-15 14:15:57 -0400  outgoing  
14529  response    2018-08-23 15:53:24 -0400        incoming  
14532  followup_sent    2018-08-23 16:48:40 -0400  internal_review  internal_review  2018-08-23 16:48:40 -0400  outgoing  
14550  response    2018-08-24 11:40:29 -0400    not_held  2018-08-24 19:35:30 -0400  incoming  
14568  status_update  described_state  2018-08-24 19:35:29 -0400  not_held  not_held  2018-08-24 19:35:30 -0400   
14633  response    2018-08-28 11:13:11 -0400    successful  2018-08-31 21:38:14 -0400  incoming  
14735  status_update  described_state  2018-08-31 21:38:14 -0400  successful  successful  2018-08-31 21:38:14 -0400   
20842  edit metadata  allow_new_responses_from  2018-12-02 03:45:09 -0500         
20843  edit metadata  allow_new_responses_from  2018-12-02 03:45:10 -0500         
20844  edit metadata  allow_new_responses_from  2018-12-02 03:45:10 -0500         
20845  edit metadata  allow_new_responses_from  2018-12-02 03:45:10 -0500         
20846  edit metadata  allow_new_responses_from  2018-12-02 03:45:10 -0500         
20847  edit metadata  allow_new_responses_from  2018-12-02 03:45:10 -0500         
20848  edit metadata  allow_new_responses_from  2018-12-02 03:45:10 -0500         
66348  edit metadata  allow_new_responses_from  2019-09-02 03:45:10 -0400         
66349  edit metadata  allow_new_responses_from  2019-09-02 03:45:10 -0400         
66350  edit metadata  allow_new_responses_from  2019-09-02 03:45:10 -0400         
66351  edit metadata  allow_new_responses_from  2019-09-02 03:45:10 -0400         
66352  edit metadata  allow_new_responses_from  2019-09-02 03:45:10 -0400         
66353  edit metadata  allow_new_responses_from  2019-09-02 03:45:10 -0400         
66354  edit metadata  allow_new_responses_from  2019-09-02 03:45:10 -0400         
66355  edit metadata  allow_new_responses_from  2019-09-02 03:45:10 -0400         
66356  edit metadata  allow_new_responses_from  2019-09-02 03:45:10 -0400         
66357  edit metadata  allow_new_responses_from  2019-09-02 03:45:10 -0400         
66358  edit metadata  allow_new_responses_from  2019-09-02 03:45:10 -0400         
66359  edit metadata  allow_new_responses_from  2019-09-02 03:45:10 -0400         
66360  edit metadata  allow_new_responses_from  2019-09-02 03:45:10 -0400         
66361  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.