Details of request “Status of Section 33, Personal Data (Privacy) Ordinance

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
1911  sent    2018-10-12 21:41:33 +0800  waiting_response  waiting_response  2018-10-12 21:41:33 +0800  outgoing  
1927  response    2018-10-15 19:23:18 +0800    waiting_response  2018-10-16 03:28:35 +0800  incoming  
1928  status_update    2018-10-16 03:28:35 +0800  waiting_response  waiting_response  2018-10-16 03:28:35 +0800   
1950  response    2018-10-22 16:53:31 +0800    waiting_response  2018-10-24 15:08:39 +0800  incoming  
1956  status_update    2018-10-24 15:08:39 +0800  waiting_response  waiting_response  2018-10-24 15:08:39 +0800   
1964  response    2018-10-26 12:23:43 +0800    rejected  2018-11-02 00:31:41 +0800  incoming  
1974  status_update  described_state  2018-11-02 00:31:41 +0800  rejected  rejected  2018-11-02 00:31:41 +0800   
2401  edit metadata  allow_new_responses_from  2019-05-02 11:45:07 +0800         
2402  edit metadata  allow_new_responses_from  2019-05-02 11:45:07 +0800         
2403  edit metadata  allow_new_responses_from  2019-05-02 11:45:07 +0800         
2404  edit metadata  allow_new_responses_from  2019-05-02 11:45:07 +0800         
2405  edit metadata  allow_new_responses_from  2019-05-02 11:45:07 +0800         
2406  edit metadata  allow_new_responses_from  2019-05-02 11:45:07 +0800         
2407  edit metadata  allow_new_responses_from  2019-05-02 11:45:07 +0800         
5053  edit metadata  allow_new_responses_from  2020-11-02 11:45:05 +0800         
5054  edit metadata  allow_new_responses_from  2020-11-02 11:45:05 +0800         
5055  edit metadata  allow_new_responses_from  2020-11-02 11:45:05 +0800         
5056  edit metadata  allow_new_responses_from  2020-11-02 11:45:05 +0800         
5057  edit metadata  allow_new_responses_from  2020-11-02 11:45:05 +0800         
5058  edit metadata  allow_new_responses_from  2020-11-02 11:45:06 +0800         
5059  edit metadata  allow_new_responses_from  2020-11-02 11:45:06 +0800         
5060  edit metadata  allow_new_responses_from  2020-11-02 11:45:06 +0800         
5061  edit metadata  allow_new_responses_from  2020-11-02 11:45:06 +0800         
5062  edit metadata  allow_new_responses_from  2020-11-02 11:45:06 +0800         
5063  edit metadata  allow_new_responses_from  2020-11-02 11:45:06 +0800         
5064  edit metadata  allow_new_responses_from  2020-11-02 11:45:06 +0800         
5065  edit metadata  allow_new_responses_from  2020-11-02 11:45:06 +0800         
5066  edit metadata  allow_new_responses_from  2020-11-02 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.