Details of request “Grade distribution for HUMS301 2024

Event history

This table shows the technical details of the internal events that happened to this request on FYI. 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 FYI. 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 OIA 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
201309 sent 2024-06-13 20:10:17 +1200 waiting_response 2024-06-13 20:10:17 +1200 waiting_response outgoing
201530 response 2024-06-17 10:21:26 +1200 2024-07-04 16:39:23 +1200 waiting_response incoming
203189 status_update 2024-07-04 16:39:23 +1200 waiting_response 2024-07-04 16:39:23 +1200 waiting_response
203708 response 2024-07-10 10:57:32 +1200 incoming
203710 followup_sent 2024-07-10 11:00:12 +1200 outgoing
204181 response 2024-07-15 14:36:31 +1200 2024-07-25 15:52:08 +1200 waiting_response incoming
205558 status_update 2024-07-25 15:52:08 +1200 waiting_response 2024-07-25 15:52:08 +1200 waiting_response
206637 response 2024-08-06 16:03:31 +1200 2024-08-06 16:12:34 +1200 waiting_response incoming
206639 followup_sent 2024-08-06 16:12:28 +1200 outgoing
206640 status_update 2024-08-06 16:12:34 +1200 waiting_response 2024-08-06 16:12:34 +1200 waiting_response
206641 response 2024-08-06 16:33:31 +1200 2024-09-02 17:04:06 +1200 waiting_response incoming
209418 status_update 2024-09-02 17:04:06 +1200 waiting_response 2024-09-02 17:04:06 +1200 waiting_response
209556 response 2024-09-03 16:35:20 +1200 2024-09-03 16:37:38 +1200 waiting_response incoming
209557 followup_sent 2024-09-03 16:37:33 +1200 outgoing
209558 status_update 2024-09-03 16:37:38 +1200 waiting_response 2024-09-03 16:37:38 +1200 waiting_response
209559 response 2024-09-03 16:55:20 +1200 incoming
212648 response 2024-10-01 16:39:09 +1300 2024-10-01 17:01:57 +1300 not_held incoming
212652 followup_sent 2024-10-01 17:01:47 +1300 outgoing
212653 status_update 2024-10-01 17:01:57 +1300 not_held 2024-10-01 17:01:57 +1300 not_held
212820 response 2024-10-02 16:59:09 +1300 incoming
215932 response 2024-10-29 16:51:23 +1300 2024-10-29 16:52:48 +1300 waiting_response incoming
215934 followup_sent 2024-10-29 16:52:39 +1300 outgoing
215935 status_update 2024-10-29 16:52:47 +1300 waiting_response 2024-10-29 16:52:48 +1300 waiting_response
216167 response 2024-10-30 16:41:23 +1300 2024-11-04 15:34:12 +1300 waiting_response incoming
216656 status_update 2024-11-04 15:34:12 +1300 waiting_response 2024-11-04 15:34:12 +1300 waiting_response
219242 response 2024-11-25 09:41:21 +1300 incoming
219952 followup_sent 2024-11-29 07:59:45 +1300 outgoing
220222 response 2024-12-02 10:01:47 +1300 incoming

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 FYI 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.