Details of request “Real-time energy consumption data

Event history

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
2280  sent  2019-03-26 01:01:23 +0800  waiting_response  2019-03-26 01:01:24 +0800  waiting_response  outgoing  
2290  response  2019-03-28 15:40:24 +0800    2020-01-22 01:23:42 +0800  not_held  incoming  
3035  edit  2019-09-29 11:45:07 +0800         
3036  edit  2019-09-29 11:45:07 +0800         
3365  status_update  2020-01-22 01:23:42 +0800  not_held  2020-01-22 01:23:42 +0800  not_held   
10646  edit  2022-01-22 11:45:06 +0800         
10647  edit  2022-01-22 11:45:06 +0800         
10648  edit  2022-01-22 11:45:06 +0800         
10649  edit  2022-01-22 11:45:06 +0800         
10650  edit  2022-01-22 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 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.