Details of request “Bid Tabulation Results for Improvements to Sickles 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
865701  set_embargo    2024-02-28 10:00:07 -0500         
865702  sent    2024-02-28 10:00:08 -0500  waiting_response  waiting_response  2024-02-28 10:00:08 -0500  outgoing  
865703  public_token    2024-02-28 10:00:29 -0500         
865704  public_token    2024-02-28 10:00:29 -0500         
875725  overdue    2024-03-09 00:00:00 -0500         
886728  very_overdue    2024-03-28 00:00:00 -0400         
1170520  embargo_expiring    2025-02-19 00:00:00 -0500         
1177369  expire_embargo    2025-02-27 00:00:08 -0500         
1177611  edit metadata  allow_new_responses_from  2025-02-27 03:45:10 -0500         
1177612  edit metadata  allow_new_responses_from  2025-02-27 03:45:10 -0500         
1177613  edit metadata  allow_new_responses_from  2025-02-27 03:45:10 -0500         
1177614  edit metadata  allow_new_responses_from  2025-02-27 03:45:10 -0500         
1177615  edit metadata  allow_new_responses_from  2025-02-27 03:45:10 -0500         
1177616  edit metadata  allow_new_responses_from  2025-02-27 03:45:10 -0500         
1177617  edit metadata  allow_new_responses_from  2025-02-27 03:45:10 -0500         
1177618  edit metadata  allow_new_responses_from  2025-02-27 03:45:10 -0500         
1551487  edit metadata  allow_new_responses_from  2026-03-01 03:45:32 -0500         
1551488  edit metadata  allow_new_responses_from  2026-03-01 03:45:32 -0500         
1551489  edit metadata  allow_new_responses_from  2026-03-01 03:45:32 -0500         
1551490  edit metadata  allow_new_responses_from  2026-03-01 03:45:32 -0500         
1551491  edit metadata  allow_new_responses_from  2026-03-01 03:45:32 -0500         
1551492  edit metadata  allow_new_responses_from  2026-03-01 03:45:32 -0500         
1551493  edit metadata  allow_new_responses_from  2026-03-01 03:45:32 -0500         
1551494  edit metadata  allow_new_responses_from  2026-03-01 03:45:32 -0500         
1551495  edit metadata  allow_new_responses_from  2026-03-01 03:45:32 -0500         
1551496  edit metadata  allow_new_responses_from  2026-03-01 03:45:32 -0500         
1551497  edit metadata  allow_new_responses_from  2026-03-01 03:45:32 -0500         
1551498  edit metadata  allow_new_responses_from  2026-03-01 03:45:32 -0500         
1551499  edit metadata  allow_new_responses_from  2026-03-01 03:45:32 -0500         
1551500  edit metadata  allow_new_responses_from  2026-03-01 03:45:33 -0500         
1551501  edit metadata  allow_new_responses_from  2026-03-01 03:45:33 -0500         
1551502  edit metadata  allow_new_responses_from  2026-03-01 03:45:33 -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.