Details of request “Does Hong Kong Manipulate the Weather?

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
16697  sent    2022-12-09 06:45:45 +0800  waiting_response  waiting_response  2022-12-09 06:45:45 +0800  outgoing  
16698  response    2022-12-09 06:50:28 +0800    waiting_response  2022-12-12 15:26:09 +0800  incoming  
16782  status_update    2022-12-12 15:26:09 +0800  waiting_response  waiting_response  2022-12-12 15:26:09 +0800   
16830  response    2022-12-15 22:22:02 +0800    waiting_response  2022-12-26 16:25:26 +0800  incoming  
16956  status_update    2022-12-26 16:25:26 +0800  waiting_response  waiting_response  2022-12-26 16:25:26 +0800   
16964  response    2022-12-29 09:09:36 +0800    partially_successful  2023-01-03 09:02:29 +0800  incoming  
16979  status_update  described_state  2023-01-03 09:02:28 +0800  partially_successful  partially_successful  2023-01-03 09:02:29 +0800   
19881  edit metadata  allow_new_responses_from  2023-07-04 11:45:16 +0800         
19882  edit metadata  allow_new_responses_from  2023-07-04 11:45:17 +0800         
19883  edit metadata  allow_new_responses_from  2023-07-04 11:45:17 +0800         
19884  edit metadata  allow_new_responses_from  2023-07-04 11:45:17 +0800         
19885  edit metadata  allow_new_responses_from  2023-07-04 11:45:17 +0800         
19886  edit metadata  allow_new_responses_from  2023-07-04 11:45:17 +0800         
19887  edit metadata  allow_new_responses_from  2023-07-04 11:45:17 +0800         
31022  edit metadata  allow_new_responses_from  2025-05-02 11:46:13 +0800         
31023  edit metadata  allow_new_responses_from  2025-05-02 11:46:13 +0800         
31024  edit metadata  allow_new_responses_from  2025-05-02 11:46:13 +0800         
31025  edit metadata  allow_new_responses_from  2025-05-02 11:46:14 +0800         
31026  edit metadata  allow_new_responses_from  2025-05-02 11:46:14 +0800         
31027  edit metadata  allow_new_responses_from  2025-05-02 11:46:14 +0800         
31028  edit metadata  allow_new_responses_from  2025-05-02 11:46:14 +0800         
31029  edit metadata  allow_new_responses_from  2025-05-02 11:46:14 +0800         
31030  edit metadata  allow_new_responses_from  2025-05-02 11:46:14 +0800         
31031  edit metadata  allow_new_responses_from  2025-05-02 11:46:14 +0800         
31032  edit metadata  allow_new_responses_from  2025-05-02 11:46:14 +0800         
31033  edit metadata  allow_new_responses_from  2025-05-02 11:46:14 +0800         
31034  edit metadata  allow_new_responses_from  2025-05-02 11:46:14 +0800         
31035  edit metadata  allow_new_responses_from  2025-05-02 11:46:14 +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.