Details of request “No. of Outstanding USM Claims

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
2912  sent    2019-08-14 18:29:02 +0800  waiting_response  waiting_response  2019-08-14 18:29:02 +0800  outgoing  
2942  response    2019-08-21 11:39:45 +0800    waiting_response  2019-08-21 11:41:15 +0800  incoming  
2943  status_update    2019-08-21 11:41:15 +0800  waiting_response  waiting_response  2019-08-21 11:41:15 +0800   
2961  response    2019-09-02 17:41:01 +0800    waiting_response  2019-09-02 18:01:24 +0800  incoming  
2962  status_update    2019-09-02 18:01:24 +0800  waiting_response  waiting_response  2019-09-02 18:01:24 +0800   
2973  response    2019-09-11 11:57:25 +0800    successful  2019-09-26 10:16:22 +0800  incoming  
3019  status_update  described_state  2019-09-26 10:16:22 +0800  successful  successful  2019-09-26 10:16:22 +0800   
3686  edit metadata  allow_new_responses_from  2020-03-27 11:45:07 +0800         
3687  edit metadata  allow_new_responses_from  2020-03-27 11:45:07 +0800         
3688  edit metadata  allow_new_responses_from  2020-03-27 11:45:07 +0800         
3689  edit metadata  allow_new_responses_from  2020-03-27 11:45:07 +0800         
3690  edit metadata  allow_new_responses_from  2020-03-27 11:45:07 +0800         
3691  edit metadata  allow_new_responses_from  2020-03-27 11:45:07 +0800         
3692  edit metadata  allow_new_responses_from  2020-03-27 11:45:07 +0800         
8022  edit metadata  allow_new_responses_from  2021-09-27 11:45:07 +0800         
8023  edit metadata  allow_new_responses_from  2021-09-27 11:45:07 +0800         
8024  edit metadata  allow_new_responses_from  2021-09-27 11:45:07 +0800         
8025  edit metadata  allow_new_responses_from  2021-09-27 11:45:07 +0800         
8026  edit metadata  allow_new_responses_from  2021-09-27 11:45:07 +0800         
8027  edit metadata  allow_new_responses_from  2021-09-27 11:45:07 +0800         
8028  edit metadata  allow_new_responses_from  2021-09-27 11:45:07 +0800         
8029  edit metadata  allow_new_responses_from  2021-09-27 11:45:08 +0800         
8030  edit metadata  allow_new_responses_from  2021-09-27 11:45:08 +0800         
8031  edit metadata  allow_new_responses_from  2021-09-27 11:45:08 +0800         
8032  edit metadata  allow_new_responses_from  2021-09-27 11:45:08 +0800         
8033  edit metadata  allow_new_responses_from  2021-09-27 11:45:08 +0800         
8034  edit metadata  allow_new_responses_from  2021-09-27 11:45:08 +0800         
8035  edit metadata  allow_new_responses_from  2021-09-27 11:45:08 +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.