Details of request “Ivory stockpile data

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
479  sent    2016-07-21 02:39:06 +0800  waiting_response  waiting_response  2016-07-21 02:39:06 +0800  outgoing  
480  response    2016-07-21 02:43:03 +0800    waiting_response  2016-07-21 03:08:22 +0800  incoming  
481  status_update    2016-07-21 03:08:22 +0800  waiting_response  waiting_response  2016-07-21 03:08:22 +0800   
492  response    2016-07-28 14:27:30 +0800    waiting_response  2016-07-28 14:45:19 +0800  incoming  
494  followup_sent    2016-07-28 14:44:56 +0800        outgoing  
495  status_update    2016-07-28 14:45:18 +0800  waiting_response  waiting_response  2016-07-28 14:45:18 +0800   
505  response    2016-08-04 12:27:44 +0800        incoming  
510  followup_sent    2016-08-08 11:42:51 +0800  internal_review  internal_review  2016-08-08 11:42:51 +0800  outgoing  
528  response    2016-08-17 10:04:11 +0800    internal_review  2016-08-22 11:51:32 +0800  incoming  
535  status_update    2016-08-22 11:51:32 +0800  internal_review  internal_review  2016-08-22 11:51:32 +0800   
536  response    2016-08-29 09:56:24 +0800    not_held  2016-10-16 17:35:06 +0800  incoming  
712  status_update  described_state  2016-10-16 17:35:06 +0800  not_held  not_held  2016-10-16 17:35: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.