Details of request “2016-19 Triennium Planning Exercise

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
3397  sent    2020-01-23 17:33:31 +0800  waiting_response  waiting_response  2020-01-23 17:33:31 +0800  outgoing  
3398  response    2020-01-23 17:34:46 +0800    waiting_response  2020-01-23 17:35:44 +0800  incoming  
3399  status_update    2020-01-23 17:35:44 +0800  waiting_response  waiting_response  2020-01-23 17:35:44 +0800   
3417  response    2020-01-29 11:46:50 +0800    waiting_response  2020-01-29 15:47:37 +0800  incoming  
3418  status_update    2020-01-29 15:47:37 +0800  waiting_response  waiting_response  2020-01-29 15:47:37 +0800   
3532  response    2020-02-14 15:45:51 +0800    rejected  2020-02-20 03:39:37 +0800  incoming  
3569  status_update  described_state  2020-02-20 03:39:37 +0800  rejected  rejected  2020-02-20 03:39:37 +0800   
4486  edit metadata  allow_new_responses_from  2020-08-20 11:45:06 +0800         
4487  edit metadata  allow_new_responses_from  2020-08-20 11:45:06 +0800         
4488  edit metadata  allow_new_responses_from  2020-08-20 11:45:06 +0800         
4489  edit metadata  allow_new_responses_from  2020-08-20 11:45:06 +0800         
4490  edit metadata  allow_new_responses_from  2020-08-20 11:45:06 +0800         
4491  edit metadata  allow_new_responses_from  2020-08-20 11:45:06 +0800         
4492  edit metadata  allow_new_responses_from  2020-08-20 11:45:06 +0800         
11054  edit metadata  allow_new_responses_from  2022-02-20 11:45:06 +0800         
11055  edit metadata  allow_new_responses_from  2022-02-20 11:45:06 +0800         
11056  edit metadata  allow_new_responses_from  2022-02-20 11:45:06 +0800         
11057  edit metadata  allow_new_responses_from  2022-02-20 11:45:06 +0800         
11058  edit metadata  allow_new_responses_from  2022-02-20 11:45:06 +0800         
11059  edit metadata  allow_new_responses_from  2022-02-20 11:45:06 +0800         
11060  edit metadata  allow_new_responses_from  2022-02-20 11:45:06 +0800         
11061  edit metadata  allow_new_responses_from  2022-02-20 11:45:06 +0800         
11062  edit metadata  allow_new_responses_from  2022-02-20 11:45:06 +0800         
11063  edit metadata  allow_new_responses_from  2022-02-20 11:45:06 +0800         
11064  edit metadata  allow_new_responses_from  2022-02-20 11:45:06 +0800         
11065  edit metadata  allow_new_responses_from  2022-02-20 11:45:06 +0800         
11066  edit metadata  allow_new_responses_from  2022-02-20 11:45:06 +0800         
11067  edit metadata  allow_new_responses_from  2022-02-20 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.