Details of request “Bid Tabulation Results for Piney Hollow Preservation Trail Improvements

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
874737  set_embargo    2024-03-08 08:57:52 -0500         
874738  sent    2024-03-08 08:57:52 -0500  waiting_response  waiting_response  2024-03-08 08:57:52 -0500  outgoing  
874739  public_token    2024-03-08 08:57:54 -0500         
874740  response    2024-03-08 08:58:10 -0500        incoming  
874773  response    2024-03-08 09:02:18 -0500        incoming  
1179586  embargo_expiring    2025-02-28 00:00:00 -0500         
1186128  expire_embargo    2025-03-08 00:00:08 -0500         
1186318  edit metadata  allow_new_responses_from  2025-03-08 03:45:10 -0500         
1186319  edit metadata  allow_new_responses_from  2025-03-08 03:45:10 -0500         
1186320  edit metadata  allow_new_responses_from  2025-03-08 03:45:10 -0500         
1186321  edit metadata  allow_new_responses_from  2025-03-08 03:45:10 -0500         
1186322  edit metadata  allow_new_responses_from  2025-03-08 03:45:10 -0500         
1186323  edit metadata  allow_new_responses_from  2025-03-08 03:45:10 -0500         
1186324  edit metadata  allow_new_responses_from  2025-03-08 03:45:10 -0500         
1557398  edit metadata  allow_new_responses_from  2026-03-09 03:45:28 -0400         
1557399  edit metadata  allow_new_responses_from  2026-03-09 03:45:28 -0400         
1557400  edit metadata  allow_new_responses_from  2026-03-09 03:45:28 -0400         
1557401  edit metadata  allow_new_responses_from  2026-03-09 03:45:28 -0400         
1557402  edit metadata  allow_new_responses_from  2026-03-09 03:45:28 -0400         
1557403  edit metadata  allow_new_responses_from  2026-03-09 03:45:28 -0400         
1557404  edit metadata  allow_new_responses_from  2026-03-09 03:45:28 -0400         
1557405  edit metadata  allow_new_responses_from  2026-03-09 03:45:28 -0400         
1557406  edit metadata  allow_new_responses_from  2026-03-09 03:45:28 -0400         
1557407  edit metadata  allow_new_responses_from  2026-03-09 03:45:28 -0400         
1557408  edit metadata  allow_new_responses_from  2026-03-09 03:45:28 -0400         
1557409  edit metadata  allow_new_responses_from  2026-03-09 03:45:28 -0400         
1557410  edit metadata  allow_new_responses_from  2026-03-09 03:45:28 -0400         
1557411  edit metadata  allow_new_responses_from  2026-03-09 03:45:28 -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.