Details of request “Adjournments in the Torture Claims Appeal Board

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
2600  sent    2019-06-28 17:05:17 +0800  waiting_response  waiting_response  2019-06-28 17:05:17 +0800  outgoing  
2640  response    2019-07-05 17:49:35 +0800    waiting_response  2019-07-08 09:41:46 +0800  incoming  
2642  status_update    2019-07-08 09:41:46 +0800  waiting_response  waiting_response  2019-07-08 09:41:46 +0800   
2702  response    2019-07-18 12:33:16 +0800    waiting_response  2019-07-19 17:16:58 +0800  incoming  
2725  status_update    2019-07-19 17:16:58 +0800  waiting_response  waiting_response  2019-07-19 17:16:58 +0800   
2788  followup_sent    2019-07-29 11:53:11 +0800  internal_review  internal_review  2019-07-29 11:53:11 +0800  outgoing  
2870  response    2019-08-06 07:06:08 +0800        incoming  
2911  response    2019-08-14 11:35:18 +0800    not_held  2020-01-20 00:33:22 +0800  incoming  
3324  status_update  described_state  2020-01-20 00:33:21 +0800  not_held  not_held  2020-01-20 00:33:22 +0800   
4149  edit metadata  allow_new_responses_from  2020-07-20 11:45:07 +0800         
4150  edit metadata  allow_new_responses_from  2020-07-20 11:45:07 +0800         
4151  edit metadata  allow_new_responses_from  2020-07-20 11:45:08 +0800         
4152  edit metadata  allow_new_responses_from  2020-07-20 11:45:08 +0800         
4153  edit metadata  allow_new_responses_from  2020-07-20 11:45:08 +0800         
4154  edit metadata  allow_new_responses_from  2020-07-20 11:45:08 +0800         
4155  edit metadata  allow_new_responses_from  2020-07-20 11:45:08 +0800         
4156  edit metadata  allow_new_responses_from  2020-07-20 11:45:08 +0800         
4157  edit metadata  allow_new_responses_from  2020-07-20 11:45:08 +0800         
10327  edit metadata  allow_new_responses_from  2022-01-20 11:45:14 +0800         
10328  edit metadata  allow_new_responses_from  2022-01-20 11:45:14 +0800         
10329  edit metadata  allow_new_responses_from  2022-01-20 11:45:14 +0800         
10330  edit metadata  allow_new_responses_from  2022-01-20 11:45:14 +0800         
10331  edit metadata  allow_new_responses_from  2022-01-20 11:45:14 +0800         
10332  edit metadata  allow_new_responses_from  2022-01-20 11:45:14 +0800         
10333  edit metadata  allow_new_responses_from  2022-01-20 11:45:14 +0800         
10334  edit metadata  allow_new_responses_from  2022-01-20 11:45:14 +0800         
10335  edit metadata  allow_new_responses_from  2022-01-20 11:45:14 +0800         
10336  edit metadata  allow_new_responses_from  2022-01-20 11:45:14 +0800         
10337  edit metadata  allow_new_responses_from  2022-01-20 11:45:14 +0800         
10338  edit metadata  allow_new_responses_from  2022-01-20 11:45:14 +0800         
10339  edit metadata  allow_new_responses_from  2022-01-20 11:45:14 +0800         
10340  edit metadata  allow_new_responses_from  2022-01-20 11:45:14 +0800         
10341  edit metadata  allow_new_responses_from  2022-01-20 11:45:14 +0800         
10342  edit metadata  allow_new_responses_from  2022-01-20 11:45:14 +0800         
10343  edit metadata  allow_new_responses_from  2022-01-20 11:45:14 +0800         
10344  edit metadata  allow_new_responses_from  2022-01-20 11:45:14 +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.