Details of request “Berkeley Township Recreation Department

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
31591  sent    2019-03-07 08:59:01 -0500  waiting_response  waiting_response  2019-03-07 08:59:01 -0500  outgoing  
31594  response    2019-03-07 09:20:47 -0500        incoming  
31595  response    2019-03-07 09:23:46 -0500        incoming  
31633  followup_sent    2019-03-07 17:55:10 -0500  internal_review  internal_review  2019-03-07 17:55:10 -0500  outgoing  
31634  followup_sent    2019-03-07 17:58:56 -0500  internal_review  internal_review  2019-03-07 17:58:56 -0500  outgoing  
31838  response    2019-03-08 09:42:49 -0500    waiting_response  2019-03-13 18:28:38 -0400  incoming  
32509  status_update  described_state  2019-03-13 18:28:38 -0400  waiting_response  waiting_response  2019-03-13 18:28:38 -0400   
33034  overdue    2019-03-19 00:00:00 -0400         
35081  very_overdue    2019-04-05 00:00:00 -0400         
49078  edit metadata  allow_new_responses_from  2019-06-14 03:45:17 -0400         
49079  edit metadata  allow_new_responses_from  2019-06-14 03:45:17 -0400         
49080  edit metadata  allow_new_responses_from  2019-06-14 03:45:17 -0400         
49081  edit metadata  allow_new_responses_from  2019-06-14 03:45:17 -0400         
49082  edit metadata  allow_new_responses_from  2019-06-14 03:45:17 -0400         
49083  edit metadata  allow_new_responses_from  2019-06-14 03:45:17 -0400         
49084  edit metadata  allow_new_responses_from  2019-06-14 03:45:17 -0400         
49085  edit metadata  allow_new_responses_from  2019-06-14 03:45:17 -0400         
49086  edit metadata  allow_new_responses_from  2019-06-14 03:45:17 -0400         
119723  edit metadata  allow_new_responses_from  2020-03-14 03:45:21 -0400         
119724  edit metadata  allow_new_responses_from  2020-03-14 03:45:21 -0400         
119725  edit metadata  allow_new_responses_from  2020-03-14 03:45:21 -0400         
119726  edit metadata  allow_new_responses_from  2020-03-14 03:45:21 -0400         
119727  edit metadata  allow_new_responses_from  2020-03-14 03:45:21 -0400         
119728  edit metadata  allow_new_responses_from  2020-03-14 03:45:21 -0400         
119729  edit metadata  allow_new_responses_from  2020-03-14 03:45:21 -0400         
119730  edit metadata  allow_new_responses_from  2020-03-14 03:45:21 -0400         
119731  edit metadata  allow_new_responses_from  2020-03-14 03:45:21 -0400         
119732  edit metadata  allow_new_responses_from  2020-03-14 03:45:21 -0400         
119733  edit metadata  allow_new_responses_from  2020-03-14 03:45:21 -0400         
119734  edit metadata  allow_new_responses_from  2020-03-14 03:45:21 -0400         
119735  edit metadata  allow_new_responses_from  2020-03-14 03:45:21 -0400         
119736  edit metadata  allow_new_responses_from  2020-03-14 03:45:21 -0400         
119737  edit metadata  allow_new_responses_from  2020-03-14 03:45:21 -0400         
119738  edit metadata  allow_new_responses_from  2020-03-14 03:45:21 -0400         
119739  edit metadata  allow_new_responses_from  2020-03-14 03:45:21 -0400         
119740  edit metadata  allow_new_responses_from  2020-03-14 03:45:22 -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.