Details of request “Shapefiles of 1982 DCCA and vote turnout 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
21913  sent    2023-10-13 10:01:02 +0800  waiting_response  waiting_response  2023-10-13 10:01:02 +0800  outgoing  
21914  response    2023-10-13 10:08:51 +0800    waiting_response  2023-10-16 15:16:12 +0800  incoming  
22040  status_update    2023-10-16 15:16:12 +0800  waiting_response  waiting_response  2023-10-16 15:16:12 +0800   
22137  response    2023-10-19 15:35:25 +0800        incoming  
22187  response    2023-10-20 15:14:10 +0800    waiting_response  2023-10-24 15:03:16 +0800  incoming  
22385  status_update    2023-10-24 15:03:16 +0800  waiting_response  waiting_response  2023-10-24 15:03:16 +0800   
22386  response    2023-10-24 15:16:10 +0800    not_held  2023-10-24 15:43:35 +0800  incoming  
22387  status_update  described_state  2023-10-24 15:43:35 +0800  not_held  not_held  2023-10-24 15:43:35 +0800   
22676  response    2023-10-31 15:27:48 +0800    partially_successful  2023-11-04 15:08:23 +0800  incoming  
22955  status_update  described_state  2023-11-04 15:08:23 +0800  partially_successful  partially_successful  2023-11-04 15:08:23 +0800   
27538  response    2024-05-03 11:33:09 +0800    attention_requested  2024-05-07 03:17:22 +0800  incoming  
27597  report_request  attention_requested  2024-05-07 03:17:22 +0800  attention_requested       
28175  response    2024-06-06 16:15:23 +0800        incoming  
29192  edit metadata  allow_new_responses_from  2025-05-02 11:45:13 +0800         
29193  edit metadata  allow_new_responses_from  2025-05-02 11:45:13 +0800         
29194  edit metadata  allow_new_responses_from  2025-05-02 11:45:13 +0800         
29195  edit metadata  allow_new_responses_from  2025-05-02 11:45:13 +0800         
29196  edit metadata  allow_new_responses_from  2025-05-02 11:45:13 +0800         
29197  edit metadata  allow_new_responses_from  2025-05-02 11:45:13 +0800         
29198  edit metadata  allow_new_responses_from  2025-05-02 11:45:13 +0800         
29199  edit metadata  allow_new_responses_from  2025-05-02 11:45:13 +0800         
29200  edit metadata  allow_new_responses_from  2025-05-02 11:45:13 +0800         
29201  edit metadata  allow_new_responses_from  2025-05-02 11:45:13 +0800         
29202  edit metadata  allow_new_responses_from  2025-05-02 11:45:13 +0800         
29203  edit metadata  allow_new_responses_from  2025-05-02 11:45:13 +0800         
29204  edit metadata  allow_new_responses_from  2025-05-02 11:45:13 +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.