Details of request “丁屋的空間數據

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
17530  sent    2023-02-03 01:55:05 +0800  waiting_response  waiting_response  2023-02-03 01:55:05 +0800  outgoing  
17617  response    2023-02-08 18:28:52 +0800    waiting_response  2023-02-08 18:54:44 +0800  incoming  
17618  status_update    2023-02-08 18:54:44 +0800  waiting_response  waiting_response  2023-02-08 18:54:44 +0800   
17799  response    2023-02-14 11:41:42 +0800        incoming  
17809  followup_sent    2023-02-14 23:01:20 +0800        outgoing  
17810  response    2023-02-14 23:06:21 +0800    waiting_response  2023-02-14 23:07:11 +0800  incoming  
17811  status_update    2023-02-14 23:07:11 +0800  waiting_response  waiting_response  2023-02-14 23:07:11 +0800   
17817  response    2023-02-16 09:45:20 +0800    waiting_response  2023-02-16 15:49:58 +0800  incoming  
17821  status_update    2023-02-16 15:49:58 +0800  waiting_response  waiting_response  2023-02-16 15:49:58 +0800   
17888  response    2023-02-24 17:44:41 +0800    waiting_response  2023-02-28 00:16:17 +0800  incoming  
17893  status_update    2023-02-28 00:16:17 +0800  waiting_response  waiting_response  2023-02-28 00:16:17 +0800   
17949  response    2023-03-06 17:32:00 +0800    successful  2023-03-18 16:54:00 +0800  incoming  
18113  status_update  described_state  2023-03-18 16:54:00 +0800  successful  successful  2023-03-18 16:54:00 +0800   
21203  edit metadata  allow_new_responses_from  2023-09-19 11:45:08 +0800         
21204  edit metadata  allow_new_responses_from  2023-09-19 11:45:08 +0800         
21205  edit metadata  allow_new_responses_from  2023-09-19 11:45:08 +0800         
21206  edit metadata  allow_new_responses_from  2023-09-19 11:45:08 +0800         
21207  edit metadata  allow_new_responses_from  2023-09-19 11:45:09 +0800         
21208  edit metadata  allow_new_responses_from  2023-09-19 11:45:09 +0800         
21209  edit metadata  allow_new_responses_from  2023-09-19 11:45:09 +0800         
21210  edit metadata  allow_new_responses_from  2023-09-19 11:45:09 +0800         
21211  edit metadata  allow_new_responses_from  2023-09-19 11:45:09 +0800         
21212  edit metadata  allow_new_responses_from  2023-09-19 11:45:09 +0800         
21213  edit metadata  allow_new_responses_from  2023-09-19 11:45:09 +0800         
21214  edit metadata  allow_new_responses_from  2023-09-19 11:45:09 +0800         
21215  edit metadata  allow_new_responses_from  2023-09-19 11:45:09 +0800         
31496  edit metadata  allow_new_responses_from  2025-05-02 11:46:28 +0800         
31497  edit metadata  allow_new_responses_from  2025-05-02 11:46:28 +0800         
31498  edit metadata  allow_new_responses_from  2025-05-02 11:46:28 +0800         
31499  edit metadata  allow_new_responses_from  2025-05-02 11:46:28 +0800         
31500  edit metadata  allow_new_responses_from  2025-05-02 11:46:28 +0800         
31501  edit metadata  allow_new_responses_from  2025-05-02 11:46:28 +0800         
31502  edit metadata  allow_new_responses_from  2025-05-02 11:46:28 +0800         
31503  edit metadata  allow_new_responses_from  2025-05-02 11:46:28 +0800         
31504  edit metadata  allow_new_responses_from  2025-05-02 11:46:28 +0800         
31505  edit metadata  allow_new_responses_from  2025-05-02 11:46:28 +0800         
31506  edit metadata  allow_new_responses_from  2025-05-02 11:46:28 +0800         
31507  edit metadata  allow_new_responses_from  2025-05-02 11:46:28 +0800         
31508  edit metadata  allow_new_responses_from  2025-05-02 11:46:28 +0800         
31509  edit metadata  allow_new_responses_from  2025-05-02 11:46:28 +0800         
31510  edit metadata  allow_new_responses_from  2025-05-02 11:46:28 +0800         
31511  edit metadata  allow_new_responses_from  2025-05-02 11:46:28 +0800         
31512  edit metadata  allow_new_responses_from  2025-05-02 11:46:28 +0800         
31513  edit metadata  allow_new_responses_from  2025-05-02 11:46:28 +0800         
31514  edit metadata  allow_new_responses_from  2025-05-02 11:46:28 +0800         
31515  edit metadata  allow_new_responses_from  2025-05-02 11:46:28 +0800         
31516  edit metadata  allow_new_responses_from  2025-05-02 11:46:29 +0800         
31517  edit metadata  allow_new_responses_from  2025-05-02 11:46:29 +0800         
31518  edit metadata  allow_new_responses_from  2025-05-02 11:46:29 +0800         
31519  edit metadata  allow_new_responses_from  2025-05-02 11:46:29 +0800         
31520  edit metadata  allow_new_responses_from  2025-05-02 11:46:29 +0800         
31521  edit metadata  allow_new_responses_from  2025-05-02 11:46:29 +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.