Details of request “Request for the Travel Characteristics Survey Data

Event history

This table shows the technical details of the internal events that happened to this request on accessinfo.hk. 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 accessinfo.hk. 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 created_at described_state last_described_at calculated_state link
19959  sent  2023-07-10 22:54:49 +0800  waiting_response  2023-07-10 22:54:49 +0800  waiting_response  outgoing  
19961  response  2023-07-11 09:51:27 +0800        incoming  
20015  response  2023-07-11 12:53:54 +0800    2023-07-15 04:40:12 +0800  waiting_response  incoming  
20055  status_update  2023-07-15 04:40:12 +0800  waiting_response  2023-07-15 04:40:12 +0800  waiting_response   
20075  response  2023-07-19 17:26:48 +0800    2023-07-20 10:54:06 +0800  waiting_response  incoming  
20076  status_update  2023-07-20 10:54:06 +0800  waiting_response  2023-07-20 10:54:06 +0800  waiting_response   
20109  followup_sent  2023-07-25 11:50:42 +0800        outgoing  
20120  response  2023-07-27 19:30:25 +0800    2023-08-02 01:15:21 +0800  waiting_response  incoming  
20170  status_update  2023-08-02 01:15:21 +0800  waiting_response  2023-08-02 01:15:21 +0800  waiting_response   
20171  followup_sent  2023-08-02 01:17:03 +0800        outgoing  
20321  response  2023-08-08 16:34:26 +0800    2023-08-08 20:38:03 +0800  waiting_response  incoming  
20322  status_update  2023-08-08 20:38:03 +0800  waiting_response  2023-08-08 20:38:03 +0800  waiting_response   
20329  followup_sent  2023-08-09 12:47:06 +0800        outgoing  
20336  response  2023-08-09 20:58:13 +0800    2023-08-17 09:05:13 +0800  successful  incoming  
20424  status_update  2023-08-17 09:05:13 +0800  successful  2023-08-17 09:05:13 +0800  successful   
25819  edit  2024-02-18 11:45:10 +0800         
25820  edit  2024-02-18 11:45:10 +0800         
25821  edit  2024-02-18 11:45:10 +0800         
25822  edit  2024-02-18 11:45:11 +0800         
25823  edit  2024-02-18 11:45:11 +0800         
25824  edit  2024-02-18 11:45:11 +0800         
25825  edit  2024-02-18 11:45:11 +0800         
25826  edit  2024-02-18 11:45:11 +0800         
25827  edit  2024-02-18 11:45:11 +0800         
25828  edit  2024-02-18 11:45:11 +0800         
25829  edit  2024-02-18 11:45:11 +0800         
25830  edit  2024-02-18 11:45:11 +0800         
25831  edit  2024-02-18 11:45:11 +0800         
25832  edit  2024-02-18 11:45:11 +0800         
25833  edit  2024-02-18 11:45:11 +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 accessinfo.hk 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.