Details of request “Establishment and strength

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
15073  sent    2022-09-12 12:49:37 +0800  waiting_response  waiting_response  2022-09-12 12:49:37 +0800  outgoing  
15075  response    2022-09-12 12:55:16 +0800        incoming  
15118  response    2022-09-16 17:47:58 +0800    error_message  2022-09-21 11:20:23 +0800  incoming  
15176  status_update  described_state  2022-09-21 11:20:23 +0800  error_message  error_message  2022-09-21 11:20:23 +0800   
15177  followup_sent    2022-09-21 11:22:02 +0800        outgoing  
15253  response    2022-09-22 18:04:24 +0800    successful  2022-09-23 15:56:29 +0800  incoming  
15280  status_update  described_state  2022-09-23 15:56:29 +0800  successful  successful  2022-09-23 15:56:29 +0800   
18188  edit metadata  allow_new_responses_from  2023-03-24 11:45:10 +0800         
18189  edit metadata  allow_new_responses_from  2023-03-24 11:45:10 +0800         
18190  edit metadata  allow_new_responses_from  2023-03-24 11:45:10 +0800         
18191  edit metadata  allow_new_responses_from  2023-03-24 11:45:10 +0800         
18192  edit metadata  allow_new_responses_from  2023-03-24 11:45:10 +0800         
18193  edit metadata  allow_new_responses_from  2023-03-24 11:45:10 +0800         
18194  edit metadata  allow_new_responses_from  2023-03-24 11:45:10 +0800         
30226  edit metadata  allow_new_responses_from  2025-05-02 11:45:47 +0800         
30227  edit metadata  allow_new_responses_from  2025-05-02 11:45:47 +0800         
30228  edit metadata  allow_new_responses_from  2025-05-02 11:45:47 +0800         
30229  edit metadata  allow_new_responses_from  2025-05-02 11:45:47 +0800         
30230  edit metadata  allow_new_responses_from  2025-05-02 11:45:47 +0800         
30231  edit metadata  allow_new_responses_from  2025-05-02 11:45:47 +0800         
30232  edit metadata  allow_new_responses_from  2025-05-02 11:45:47 +0800         
30233  edit metadata  allow_new_responses_from  2025-05-02 11:45:47 +0800         
30234  edit metadata  allow_new_responses_from  2025-05-02 11:45:47 +0800         
30235  edit metadata  allow_new_responses_from  2025-05-02 11:45:47 +0800         
30236  edit metadata  allow_new_responses_from  2025-05-02 11:45:47 +0800         
30237  edit metadata  allow_new_responses_from  2025-05-02 11:45:47 +0800         
30238  edit metadata  allow_new_responses_from  2025-05-02 11:45:47 +0800         
30239  edit metadata  allow_new_responses_from  2025-05-02 11:45:47 +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.