Details of request “Scheduling of Thymosin Beta 4 and Tb500

Event history

This table shows the technical details of the internal events that happened to this request on Right To Know. 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 Right To Know. 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
39608 sent 2019-04-17 10:59:38 +1000 waiting_response 2019-04-17 10:59:38 +1000 waiting_response outgoing
39613 response 2019-04-17 15:54:44 +1000 2019-04-29 11:04:59 +1000 waiting_response incoming
39618 status_update 2019-04-17 17:19:05 +1000 waiting_response 2019-04-17 17:19:05 +1000 waiting_response
39638 followup_sent 2019-04-18 22:01:42 +1000 outgoing
39639 status_update 2019-04-18 22:05:24 +1000 waiting_clarification 2019-04-18 22:05:24 +1000 waiting_clarification
39815 edit 2019-04-29 11:04:59 +1000 waiting_response 2019-04-29 11:04:59 +1000 waiting_response
40114 response 2019-05-16 14:29:31 +1000 2019-05-16 19:33:15 +1000 waiting_clarification incoming
40116 followup_sent 2019-05-16 19:32:53 +1000 outgoing
40117 status_update 2019-05-16 19:33:15 +1000 waiting_clarification 2019-05-16 19:33:15 +1000 waiting_clarification
40316 response 2019-05-29 15:27:31 +1000 incoming
40317 followup_sent 2019-05-29 16:50:05 +1000 waiting_response 2019-05-29 16:50:05 +1000 waiting_response outgoing
40343 response 2019-05-31 19:18:32 +1000 2019-06-01 00:01:38 +1000 waiting_clarification incoming
40344 followup_sent 2019-06-01 00:01:07 +1000 outgoing
40345 status_update 2019-06-01 00:01:38 +1000 waiting_clarification 2019-06-01 00:01:38 +1000 waiting_clarification
40371 followup_sent 2019-06-04 09:37:33 +1000 waiting_response 2019-06-04 09:37:33 +1000 waiting_response outgoing
40438 response 2019-06-11 16:47:06 +1000 2019-06-11 20:16:13 +1000 waiting_clarification incoming
40441 followup_sent 2019-06-11 20:15:57 +1000 outgoing
40442 status_update 2019-06-11 20:16:13 +1000 waiting_clarification 2019-06-11 20:16:13 +1000 waiting_clarification
40444 response 2019-06-12 11:18:52 +1000 incoming
40446 followup_sent 2019-06-12 15:04:05 +1000 waiting_response 2019-06-12 15:04:05 +1000 waiting_response outgoing
40447 response 2019-06-12 15:59:54 +1000 2019-06-12 18:24:38 +1000 waiting_clarification incoming
40450 followup_sent 2019-06-12 17:56:49 +1000 outgoing
40451 status_update 2019-06-12 18:24:38 +1000 waiting_clarification 2019-06-12 18:24:38 +1000 waiting_clarification
40453 response 2019-06-13 10:06:28 +1000 incoming
40454 followup_sent 2019-06-13 10:10:01 +1000 waiting_response 2019-06-13 10:10:02 +1000 waiting_response outgoing
40803 response 2019-07-16 10:56:15 +1000 2019-07-16 20:19:05 +1000 waiting_response incoming
40815 followup_sent 2019-07-16 20:18:33 +1000 outgoing
40816 status_update 2019-07-16 20:19:05 +1000 waiting_response 2019-07-16 20:19:05 +1000 waiting_response
40818 response 2019-07-17 09:30:22 +1000 2019-07-17 10:10:23 +1000 waiting_response incoming
40820 followup_sent 2019-07-17 10:10:01 +1000 outgoing
40821 status_update 2019-07-17 10:10:22 +1000 waiting_response 2019-07-17 10:10:22 +1000 waiting_response
40824 response 2019-07-17 12:48:59 +1000 2019-07-18 08:43:03 +1000 successful incoming
40835 status_update 2019-07-18 08:43:03 +1000 successful 2019-07-18 08:43:03 +1000 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 Right To Know 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.