Details of request “Request for engineering conditions of the Hoi Hing Road Refuse Collection Point (GLA TW-502)

Event history

This table shows the technical details of the internal events that happened to this request on AccessInfoHongKong. 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.

Caveat emptor! To use this data in an honourable way, you will need a good internal knowledge of user behaviour on AccessInfoHongKong. 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
17504  sent    2023-01-30 16:34:07 +0800  waiting_response  waiting_response  2023-01-30 16:34:07 +0800  outgoing  
17511  response    2023-01-31 17:31:03 +0800    waiting_response  2023-02-06 12:24:02 +0800  incoming  
17570  status_update    2023-02-06 12:24:02 +0800  waiting_response  waiting_response  2023-02-06 12:24:02 +0800   
17802  response    2023-02-14 15:40:15 +0800    waiting_response  2023-02-14 16:02:01 +0800  incoming  
17803  followup_sent    2023-02-14 16:01:10 +0800        outgoing  
17804  status_update    2023-02-14 16:02:01 +0800  waiting_response  waiting_response  2023-02-14 16:02:01 +0800   
17805  response    2023-02-14 16:08:00 +0800        incoming  
17825  response    2023-02-17 10:45:20 +0800    successful  2023-02-21 09:13:28 +0800  incoming  
17859  status_update  described_state  2023-02-21 09:13:28 +0800  successful  successful  2023-02-21 09:13:28 +0800   
20585  edit metadata  allow_new_responses_from  2023-08-22 11:45:08 +0800         
20586  edit metadata  allow_new_responses_from  2023-08-22 11:45:08 +0800         
20587  edit metadata  allow_new_responses_from  2023-08-22 11:45:08 +0800         
20588  edit metadata  allow_new_responses_from  2023-08-22 11:45:08 +0800         
20589  edit metadata  allow_new_responses_from  2023-08-22 11:45:08 +0800         
20590  edit metadata  allow_new_responses_from  2023-08-22 11:45:08 +0800         
20591  edit metadata  allow_new_responses_from  2023-08-22 11:45:08 +0800         
20592  edit metadata  allow_new_responses_from  2023-08-22 11:45:08 +0800         
20593  edit metadata  allow_new_responses_from  2023-08-22 11:45:08 +0800         
31440  edit metadata  allow_new_responses_from  2025-05-02 11:46:26 +0800         
31441  edit metadata  allow_new_responses_from  2025-05-02 11:46:26 +0800         
31442  edit metadata  allow_new_responses_from  2025-05-02 11:46:26 +0800         
31443  edit metadata  allow_new_responses_from  2025-05-02 11:46:26 +0800         
31444  edit metadata  allow_new_responses_from  2025-05-02 11:46:26 +0800         
31445  edit metadata  allow_new_responses_from  2025-05-02 11:46:26 +0800         
31446  edit metadata  allow_new_responses_from  2025-05-02 11:46:26 +0800         
31447  edit metadata  allow_new_responses_from  2025-05-02 11:46:26 +0800         
31448  edit metadata  allow_new_responses_from  2025-05-02 11:46:26 +0800         
31449  edit metadata  allow_new_responses_from  2025-05-02 11:46:26 +0800         
31450  edit metadata  allow_new_responses_from  2025-05-02 11:46:27 +0800         
31451  edit metadata  allow_new_responses_from  2025-05-02 11:46:27 +0800         
31452  edit metadata  allow_new_responses_from  2025-05-02 11:46:27 +0800         
31453  edit metadata  allow_new_responses_from  2025-05-02 11:46:27 +0800         
31454  edit metadata  allow_new_responses_from  2025-05-02 11:46:27 +0800         
31455  edit metadata  allow_new_responses_from  2025-05-02 11:46:27 +0800         
31456  edit metadata  allow_new_responses_from  2025-05-02 11:46:27 +0800         
31457  edit metadata  allow_new_responses_from  2025-05-02 11:46:27 +0800         

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 AccessInfoHongKong 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.