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
882026  set_embargo    2024-03-19 16:49:25 -0400         
882027  sent    2024-03-19 16:49:25 -0400  waiting_response  waiting_response  2024-03-19 16:49:25 -0400  outgoing  
882028  public_token    2024-03-19 16:49:28 -0400         
882029  response    2024-03-19 16:49:38 -0400        incoming  
882424  response    2024-03-20 09:48:00 -0400        incoming  
882542  followup_sent    2024-03-20 13:25:56 -0400        outgoing  
1189170  embargo_expiring    2025-03-11 00:00:00 -0400         
1194550  expire_embargo    2025-03-19 00:00:07 -0400         
1194588  edit metadata  allow_new_responses_from  2025-03-19 03:45:09 -0400         
1194589  edit metadata  allow_new_responses_from  2025-03-19 03:45:09 -0400         
1194590  edit metadata  allow_new_responses_from  2025-03-19 03:45:09 -0400         
1194591  edit metadata  allow_new_responses_from  2025-03-19 03:45:09 -0400         
1194592  edit metadata  allow_new_responses_from  2025-03-19 03:45:09 -0400         
1194593  edit metadata  allow_new_responses_from  2025-03-19 03:45:09 -0400         
1194594  edit metadata  allow_new_responses_from  2025-03-19 03:45:09 -0400         
1194595  edit metadata  allow_new_responses_from  2025-03-19 03:45:09 -0400         
1567845  edit metadata  allow_new_responses_from  2026-03-21 03:45:16 -0400         
1567846  edit metadata  allow_new_responses_from  2026-03-21 03:45:17 -0400         
1567847  edit metadata  allow_new_responses_from  2026-03-21 03:45:17 -0400         
1567848  edit metadata  allow_new_responses_from  2026-03-21 03:45:17 -0400         
1567849  edit metadata  allow_new_responses_from  2026-03-21 03:45:17 -0400         
1567850  edit metadata  allow_new_responses_from  2026-03-21 03:45:17 -0400         
1567851  edit metadata  allow_new_responses_from  2026-03-21 03:45:17 -0400         
1567852  edit metadata  allow_new_responses_from  2026-03-21 03:45:17 -0400         
1567853  edit metadata  allow_new_responses_from  2026-03-21 03:45:17 -0400         
1567854  edit metadata  allow_new_responses_from  2026-03-21 03:45:17 -0400         
1567855  edit metadata  allow_new_responses_from  2026-03-21 03:45:17 -0400         
1567856  edit metadata  allow_new_responses_from  2026-03-21 03:45:17 -0400         
1567857  edit metadata  allow_new_responses_from  2026-03-21 03:45:17 -0400         
1567858  edit metadata  allow_new_responses_from  2026-03-21 03:45:17 -0400         
1567859  edit metadata  allow_new_responses_from  2026-03-21 03:45:17 -0400         
1567860  edit metadata  allow_new_responses_from  2026-03-21 03:45:17 -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.