Details of request “Request for access of TCS 2011 data

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
24240  sent    2023-12-22 14:56:56 +0800  waiting_response  waiting_response  2023-12-22 14:56:56 +0800  outgoing  
24241  response    2023-12-22 17:49:42 +0800    waiting_response  2023-12-26 15:01:32 +0800  incoming  
24566  status_update    2023-12-26 15:01:32 +0800  waiting_response  waiting_response  2023-12-26 15:01:32 +0800   
24626  response    2023-12-29 17:15:36 +0800    waiting_response  2024-01-02 15:01:18 +0800  incoming  
24641  status_update    2024-01-02 15:01:18 +0800  waiting_response  waiting_response  2024-01-02 15:01:18 +0800   
24811  response    2024-01-11 17:57:22 +0800    waiting_response  2024-08-05 20:52:14 +0800  incoming  
28724  edit metadata  allow_new_responses_from  2024-07-12 11:45:11 +0800         
28725  edit metadata  allow_new_responses_from  2024-07-12 11:45:11 +0800         
28726  edit metadata  allow_new_responses_from  2024-07-12 11:45:11 +0800         
28727  edit metadata  allow_new_responses_from  2024-07-12 11:45:11 +0800         
28728  edit metadata  allow_new_responses_from  2024-07-12 11:45:11 +0800         
28729  edit metadata  allow_new_responses_from  2024-07-12 11:45:11 +0800         
29159  status_update    2024-08-05 20:52:14 +0800  waiting_response  waiting_response  2024-08-05 20:52:14 +0800   
29161  followup_sent    2024-09-01 17:37:19 +0800        outgoing  
29225  edit metadata  allow_new_responses_from  2025-05-02 11:45:14 +0800         
29226  edit metadata  allow_new_responses_from  2025-05-02 11:45:14 +0800         
29227  edit metadata  allow_new_responses_from  2025-05-02 11:45:14 +0800         
29228  edit metadata  allow_new_responses_from  2025-05-02 11:45:14 +0800         
29229  edit metadata  allow_new_responses_from  2025-05-02 11:45:14 +0800         
29230  edit metadata  allow_new_responses_from  2025-05-02 11:45:14 +0800         
29231  edit metadata  allow_new_responses_from  2025-05-02 11:45:14 +0800         
29232  edit metadata  allow_new_responses_from  2025-05-02 11:45:14 +0800         
29233  edit metadata  allow_new_responses_from  2025-05-02 11:45:14 +0800         
29234  edit metadata  allow_new_responses_from  2025-05-02 11:45:14 +0800         
29235  edit metadata  allow_new_responses_from  2025-05-02 11:45:14 +0800         
29236  edit metadata  allow_new_responses_from  2025-05-02 11:45:14 +0800         
29237  edit metadata  allow_new_responses_from  2025-05-02 11:45:14 +0800         
29238  edit metadata  allow_new_responses_from  2025-05-02 11:45: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.