Details of request “Bid Tabulation Results for Dey Forest Park at Carlton Place Pedestrian Access Improvements to Transit Village

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
586593  set_embargo    2023-01-24 19:19:26 -0500         
586594  sent    2023-01-24 19:19:26 -0500  waiting_response  waiting_response  2023-01-24 19:19:26 -0500  outgoing  
586849  response    2023-01-25 08:43:26 -0500        incoming  
590989  response    2023-01-31 11:47:09 -0500    successful  2023-01-31 18:59:00 -0500  incoming  
591109  status_update  described_state  2023-01-31 18:59:00 -0500  successful  successful  2023-01-31 18:59:00 -0500   
630409  embargo_expiring    2023-04-18 00:00:00 -0400         
636273  expire_embargo    2023-04-26 00:00:07 -0400         
721854  edit metadata  allow_new_responses_from  2023-08-01 03:45:11 -0400         
721855  edit metadata  allow_new_responses_from  2023-08-01 03:45:11 -0400         
721856  edit metadata  allow_new_responses_from  2023-08-01 03:45:11 -0400         
721857  edit metadata  allow_new_responses_from  2023-08-01 03:45:11 -0400         
721858  edit metadata  allow_new_responses_from  2023-08-01 03:45:11 -0400         
721859  edit metadata  allow_new_responses_from  2023-08-01 03:45:11 -0400         
721860  edit metadata  allow_new_responses_from  2023-08-01 03:45:11 -0400         
1157248  edit metadata  allow_new_responses_from  2025-02-01 03:45:22 -0500         
1157249  edit metadata  allow_new_responses_from  2025-02-01 03:45:22 -0500         
1157250  edit metadata  allow_new_responses_from  2025-02-01 03:45:22 -0500         
1157251  edit metadata  allow_new_responses_from  2025-02-01 03:45:22 -0500         
1157252  edit metadata  allow_new_responses_from  2025-02-01 03:45:22 -0500         
1157253  edit metadata  allow_new_responses_from  2025-02-01 03:45:22 -0500         
1157254  edit metadata  allow_new_responses_from  2025-02-01 03:45:22 -0500         
1157255  edit metadata  allow_new_responses_from  2025-02-01 03:45:22 -0500         
1157256  edit metadata  allow_new_responses_from  2025-02-01 03:45:22 -0500         
1157257  edit metadata  allow_new_responses_from  2025-02-01 03:45:22 -0500         
1157258  edit metadata  allow_new_responses_from  2025-02-01 03:45:22 -0500         
1157259  edit metadata  allow_new_responses_from  2025-02-01 03:45:22 -0500         
1157260  edit metadata  allow_new_responses_from  2025-02-01 03:45:22 -0500         
1157261  edit metadata  allow_new_responses_from  2025-02-01 03:45:22 -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.