Details of request “Bid Tabulation Results for Vegetation Management & Site Restoration at Huber Woods Park

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
831738  set_embargo    2024-01-05 09:55:15 -0500         
831739  sent    2024-01-05 09:55:16 -0500  waiting_response  waiting_response  2024-01-05 09:55:16 -0500  outgoing  
831740  public_token    2024-01-05 09:55:18 -0500         
840758  overdue    2024-01-18 00:00:00 -0500         
853131  very_overdue    2024-02-06 00:00:00 -0500         
1121350  embargo_expiring    2024-12-27 00:00:00 -0500         
1129720  expire_embargo    2025-01-04 00:00:06 -0500         
1129740  edit metadata  allow_new_responses_from  2025-01-04 03:45:08 -0500         
1129741  edit metadata  allow_new_responses_from  2025-01-04 03:45:08 -0500         
1129742  edit metadata  allow_new_responses_from  2025-01-04 03:45:08 -0500         
1129743  edit metadata  allow_new_responses_from  2025-01-04 03:45:08 -0500         
1129744  edit metadata  allow_new_responses_from  2025-01-04 03:45:09 -0500         
1129745  edit metadata  allow_new_responses_from  2025-01-04 03:45:09 -0500         
1129746  edit metadata  allow_new_responses_from  2025-01-04 03:45:09 -0500         
1502803  edit metadata  allow_new_responses_from  2026-01-06 03:45:15 -0500         
1502804  edit metadata  allow_new_responses_from  2026-01-06 03:45:15 -0500         
1502805  edit metadata  allow_new_responses_from  2026-01-06 03:45:15 -0500         
1502806  edit metadata  allow_new_responses_from  2026-01-06 03:45:15 -0500         
1502807  edit metadata  allow_new_responses_from  2026-01-06 03:45:15 -0500         
1502808  edit metadata  allow_new_responses_from  2026-01-06 03:45:15 -0500         
1502809  edit metadata  allow_new_responses_from  2026-01-06 03:45:15 -0500         
1502810  edit metadata  allow_new_responses_from  2026-01-06 03:45:15 -0500         
1502811  edit metadata  allow_new_responses_from  2026-01-06 03:45:15 -0500         
1502812  edit metadata  allow_new_responses_from  2026-01-06 03:45:16 -0500         
1502813  edit metadata  allow_new_responses_from  2026-01-06 03:45:16 -0500         
1502814  edit metadata  allow_new_responses_from  2026-01-06 03:45:16 -0500         
1502815  edit metadata  allow_new_responses_from  2026-01-06 03:45:16 -0500         
1502816  edit metadata  allow_new_responses_from  2026-01-06 03:45:16 -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.