Details of request “Non-refoulement claimants whose claims have been finally determined, Jun 2018

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
1810  sent    2018-08-23 16:29:42 +0800  waiting_response  waiting_response  2018-08-23 16:29:42 +0800  outgoing  
1813  response    2018-08-24 17:19:59 +0800        incoming  
1848  response    2018-09-10 15:37:04 +0800    waiting_response  2018-09-17 16:50:29 +0800  incoming  
1862  status_update    2018-09-17 16:50:29 +0800  waiting_response  waiting_response  2018-09-17 16:50:29 +0800   
1895  response    2018-10-03 15:35:28 +0800    partially_successful  2018-10-22 16:36:28 +0800  incoming  
1948  status_update  described_state  2018-10-22 16:36:28 +0800  partially_successful  partially_successful  2018-10-22 16:36:28 +0800   
1949  followup_sent    2018-10-22 16:37:36 +0800        outgoing  
2376  edit metadata  allow_new_responses_from  2019-04-23 11:45:07 +0800         
2377  edit metadata  allow_new_responses_from  2019-04-23 11:45:07 +0800         
2378  edit metadata  allow_new_responses_from  2019-04-23 11:45:07 +0800         
2379  edit metadata  allow_new_responses_from  2019-04-23 11:45:07 +0800         
2380  edit metadata  allow_new_responses_from  2019-04-23 11:45:07 +0800         
2381  edit metadata  allow_new_responses_from  2019-04-23 11:45:07 +0800         
2382  edit metadata  allow_new_responses_from  2019-04-23 11:45:07 +0800         
4989  edit metadata  allow_new_responses_from  2020-10-23 11:45:05 +0800         
4990  edit metadata  allow_new_responses_from  2020-10-23 11:45:05 +0800         
4991  edit metadata  allow_new_responses_from  2020-10-23 11:45:05 +0800         
4992  edit metadata  allow_new_responses_from  2020-10-23 11:45:05 +0800         
4993  edit metadata  allow_new_responses_from  2020-10-23 11:45:05 +0800         
4994  edit metadata  allow_new_responses_from  2020-10-23 11:45:06 +0800         
4995  edit metadata  allow_new_responses_from  2020-10-23 11:45:06 +0800         
4996  edit metadata  allow_new_responses_from  2020-10-23 11:45:06 +0800         
4997  edit metadata  allow_new_responses_from  2020-10-23 11:45:06 +0800         
4998  edit metadata  allow_new_responses_from  2020-10-23 11:45:06 +0800         
4999  edit metadata  allow_new_responses_from  2020-10-23 11:45:06 +0800         
5000  edit metadata  allow_new_responses_from  2020-10-23 11:45:06 +0800         
5001  edit metadata  allow_new_responses_from  2020-10-23 11:45:06 +0800         
5002  edit metadata  allow_new_responses_from  2020-10-23 11:45:06 +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.