Details of request “Visits to TGCI

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
13057  sent    2022-05-12 12:22:04 +0800  waiting_response  waiting_response  2022-05-12 12:22:04 +0800  outgoing  
13146  response    2022-05-18 16:24:30 +0800        incoming  
13175  response    2022-05-20 14:21:22 +0800    waiting_response  2022-05-20 16:36:35 +0800  incoming  
13184  followup_sent    2022-05-20 16:36:30 +0800        outgoing  
13185  status_update    2022-05-20 16:36:35 +0800  waiting_response  waiting_response  2022-05-20 16:36:35 +0800   
13345  response    2022-06-01 09:42:04 +0800    successful  2022-06-10 04:01:53 +0800  incoming  
13581  status_update  described_state  2022-06-10 04:01:53 +0800  successful  successful  2022-06-10 04:01:53 +0800   
16748  edit metadata  allow_new_responses_from  2022-12-10 11:45:10 +0800         
16749  edit metadata  allow_new_responses_from  2022-12-10 11:45:10 +0800         
16750  edit metadata  allow_new_responses_from  2022-12-10 11:45:10 +0800         
16751  edit metadata  allow_new_responses_from  2022-12-10 11:45:10 +0800         
16752  edit metadata  allow_new_responses_from  2022-12-10 11:45:10 +0800         
16753  edit metadata  allow_new_responses_from  2022-12-10 11:45:10 +0800         
16754  edit metadata  allow_new_responses_from  2022-12-10 11:45:11 +0800         
28379  edit metadata  allow_new_responses_from  2024-06-10 11:45:09 +0800         
28380  edit metadata  allow_new_responses_from  2024-06-10 11:45:09 +0800         
28381  edit metadata  allow_new_responses_from  2024-06-10 11:45:09 +0800         
28382  edit metadata  allow_new_responses_from  2024-06-10 11:45:09 +0800         
28383  edit metadata  allow_new_responses_from  2024-06-10 11:45:09 +0800         
28384  edit metadata  allow_new_responses_from  2024-06-10 11:45:09 +0800         
28385  edit metadata  allow_new_responses_from  2024-06-10 11:45:09 +0800         
28386  edit metadata  allow_new_responses_from  2024-06-10 11:45:09 +0800         
28387  edit metadata  allow_new_responses_from  2024-06-10 11:45:10 +0800         
28388  edit metadata  allow_new_responses_from  2024-06-10 11:45:10 +0800         
28389  edit metadata  allow_new_responses_from  2024-06-10 11:45:10 +0800         
28390  edit metadata  allow_new_responses_from  2024-06-10 11:45:10 +0800         
28391  edit metadata  allow_new_responses_from  2024-06-10 11:45:10 +0800         
28392  edit metadata  allow_new_responses_from  2024-06-10 11:45:10 +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.