Details of request “Request for Code Violation - Perth Amboy

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
588928  sent    2023-01-27 08:49:51 -0500  waiting_response  waiting_response  2023-01-27 08:49:51 -0500  outgoing  
588929  response    2023-01-27 08:50:12 -0500    waiting_response  2023-01-27 16:46:23 -0500  incoming  
589025  status_update    2023-01-27 16:46:23 -0500  waiting_response  waiting_response  2023-01-27 16:46:23 -0500   
590963  response    2023-01-31 09:59:50 -0500    successful  2023-02-07 10:08:03 -0500  incoming  
594184  status_update  described_state  2023-02-07 10:08:03 -0500  successful  successful  2023-02-07 10:08:03 -0500   
597551  response    2023-02-13 14:49:09 -0500    partially_successful  2023-02-16 08:37:07 -0500  incoming  
598837  status_update  described_state  2023-02-16 08:37:07 -0500  partially_successful  partially_successful  2023-02-16 08:37:07 -0500   
733273  edit metadata  allow_new_responses_from  2023-08-17 03:45:10 -0400         
733274  edit metadata  allow_new_responses_from  2023-08-17 03:45:10 -0400         
733275  edit metadata  allow_new_responses_from  2023-08-17 03:45:10 -0400         
733276  edit metadata  allow_new_responses_from  2023-08-17 03:45:10 -0400         
733277  edit metadata  allow_new_responses_from  2023-08-17 03:45:10 -0400         
733278  edit metadata  allow_new_responses_from  2023-08-17 03:45:10 -0400         
733279  edit metadata  allow_new_responses_from  2023-08-17 03:45:10 -0400         
1168905  edit metadata  allow_new_responses_from  2025-02-17 03:45:17 -0500         
1168906  edit metadata  allow_new_responses_from  2025-02-17 03:45:17 -0500         
1168907  edit metadata  allow_new_responses_from  2025-02-17 03:45:17 -0500         
1168908  edit metadata  allow_new_responses_from  2025-02-17 03:45:17 -0500         
1168909  edit metadata  allow_new_responses_from  2025-02-17 03:45:17 -0500         
1168910  edit metadata  allow_new_responses_from  2025-02-17 03:45:17 -0500         
1168911  edit metadata  allow_new_responses_from  2025-02-17 03:45:17 -0500         
1168912  edit metadata  allow_new_responses_from  2025-02-17 03:45:17 -0500         
1168913  edit metadata  allow_new_responses_from  2025-02-17 03:45:17 -0500         
1168914  edit metadata  allow_new_responses_from  2025-02-17 03:45:17 -0500         
1168915  edit metadata  allow_new_responses_from  2025-02-17 03:45:17 -0500         
1168916  edit metadata  allow_new_responses_from  2025-02-17 03:45:17 -0500         
1168917  edit metadata  allow_new_responses_from  2025-02-17 03:45:17 -0500         
1168918  edit metadata  allow_new_responses_from  2025-02-17 03:45:17 -0500         

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.