要求「Collated air quality data」的詳情

過往活動

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
187  sent  2015-09-06 12:13:29 +0800  waiting_response  2015-09-06 12:13:29 +0800  waiting_response  outgoing  
188  response  2015-09-06 12:15:40 +0800    2015-09-06 12:45:07 +0800  waiting_response  incoming  
190  status_update  2015-09-06 12:45:07 +0800  waiting_response  2015-09-06 12:45:07 +0800  waiting_response   
203  response  2015-09-15 11:21:08 +0800    2015-09-15 16:03:50 +0800  waiting_clarification  incoming  
205  status_update  2015-09-15 16:03:50 +0800  waiting_clarification  2015-09-15 16:03:50 +0800  waiting_clarification   
206  followup_sent  2015-09-15 16:21:41 +0800  waiting_response  2015-09-15 16:21:41 +0800  waiting_response  outgoing  
209  comment  2015-09-15 16:40:36 +0800         
212  response  2015-09-16 18:20:56 +0800    2015-09-17 10:53:37 +0800  waiting_clarification  incoming  
213  status_update  2015-09-17 10:53:37 +0800  waiting_clarification  2015-09-17 10:53:37 +0800  waiting_clarification   
214  followup_sent  2015-09-17 11:07:53 +0800  waiting_response  2015-09-17 11:07:53 +0800  waiting_response  outgoing  
229  response  2015-09-25 17:35:40 +0800    2015-09-28 08:10:29 +0800  waiting_response  incoming  
232  followup_sent  2015-09-28 08:10:09 +0800        outgoing  
233  status_update  2015-09-28 08:10:29 +0800  waiting_response  2015-09-28 08:10:29 +0800  waiting_response   
234  followup_sent  2015-09-28 08:15:14 +0800  internal_review  2015-09-28 08:15:14 +0800  internal_review  outgoing  
238  response  2015-09-29 10:15:56 +0800    2015-09-29 14:24:00 +0800  internal_review  incoming  
241  status_update  2015-09-29 14:23:59 +0800  internal_review  2015-09-29 14:23:59 +0800  internal_review   
245  response  2015-09-30 12:26:01 +0800    2015-09-30 17:12:48 +0800  internal_review  incoming  
246  status_update  2015-09-30 17:12:48 +0800  internal_review  2015-09-30 17:12:48 +0800  internal_review   
255  response  2015-10-08 16:58:25 +0800    2015-10-15 09:59:15 +0800  internal_review  incoming  
260  status_update  2015-10-15 09:59:15 +0800  internal_review  2015-10-15 09:59:15 +0800  internal_review   
281  response  2015-10-20 11:10:00 +0800    2015-10-20 13:59:30 +0800  internal_review  incoming  
282  status_update  2015-10-20 13:59:30 +0800  internal_review  2015-10-20 13:59:30 +0800  internal_review   
301  response  2015-11-06 15:43:26 +0800    2015-11-10 19:32:04 +0800  rejected  incoming  
306  status_update  2015-11-10 19:32:04 +0800  rejected  2015-11-10 19:32:04 +0800  rejected   

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.