要求「Request for statistics on data charges and revenue」的詳情

過往活動

This table shows the technical details of the internal events that happened to this request on accessinfo.hk. 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 accessinfo.hk. 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 created_at described_state last_described_at calculated_state link
419  sent  2016-05-11 23:33:21 +0800  waiting_response  2016-05-11 23:33:21 +0800  waiting_response  outgoing  
420  response  2016-05-11 23:34:16 +0800    2016-05-12 14:26:15 +0800  waiting_response  incoming  
421  status_update  2016-05-12 14:26:15 +0800  waiting_response  2016-05-12 14:26:15 +0800  waiting_response   
442  response  2016-05-20 14:12:38 +0800        incoming  
451  response  2016-05-26 17:52:39 +0800    2016-05-30 17:57:32 +0800  partially_successful  incoming  
461  status_update  2016-05-30 17:57:32 +0800  partially_successful  2016-05-30 17:57:32 +0800  partially_successful   
464  followup_sent  2016-06-09 18:22:08 +0800        outgoing  
465  response  2016-06-09 18:23:13 +0800    2016-06-09 18:24:05 +0800  waiting_response  incoming  
466  status_update  2016-06-09 18:24:04 +0800  waiting_response  2016-06-09 18:24:05 +0800  waiting_response   
467  response  2016-06-13 17:52:09 +0800    2016-06-14 21:04:59 +0800  waiting_response  incoming  
468  status_update  2016-06-14 21:04:59 +0800  waiting_response  2016-06-14 21:04:59 +0800  waiting_response   
469  response  2016-06-16 20:12:24 +0800    2016-07-21 02:33:33 +0800  waiting_response  incoming  
476  followup_sent  2016-07-21 02:33:08 +0800        outgoing  
477  status_update  2016-07-21 02:33:33 +0800  waiting_response  2016-07-21 02:33:33 +0800  waiting_response   
478  response  2016-07-21 02:34:13 +0800        incoming  
493  response  2016-07-28 14:36:35 +0800    2016-07-28 14:49:49 +0800  waiting_response  incoming  
496  status_update  2016-07-28 14:49:49 +0800  waiting_response  2016-07-28 14:49:49 +0800  waiting_response   
514  response  2016-08-08 16:56:23 +0800    2016-08-10 15:16:58 +0800  waiting_response  incoming  
515  followup_sent  2016-08-10 15:16:46 +0800        outgoing  
516  status_update  2016-08-10 15:16:58 +0800  waiting_response  2016-08-10 15:16:58 +0800  waiting_response   
517  response  2016-08-10 15:17:54 +0800    2016-08-10 15:20:54 +0800  waiting_response  incoming  
518  status_update  2016-08-10 15:20:54 +0800  waiting_response  2016-08-10 15:20:54 +0800  waiting_response   
522  response  2016-08-12 18:21:59 +0800        incoming  
537  response  2016-08-30 18:56:11 +0800    2016-09-08 11:11:29 +0800  partially_successful  incoming  
539  status_update  2016-09-08 11:11:29 +0800  partially_successful  2016-09-08 11:11:29 +0800  partially_successful   

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 accessinfo.hk 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.