Details of request “Human rights in Taiwan”

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
113	sent	2012-11-28 21:07:50 +1100	waiting_response	2012-11-28 21:07:50 +1100	waiting_response	outgoing
128	response	2012-11-30 10:10:24 +1100				incoming
130	followup_sent	2012-11-30 12:14:17 +1100	waiting_response	2012-11-30 13:10:26 +1100	waiting_response	outgoing
178	response	2012-12-14 11:45:41 +1100				incoming
179	followup_sent	2012-12-14 13:05:27 +1100	waiting_response	2012-12-14 13:05:45 +1100	waiting_response	outgoing
189	response	2012-12-18 09:52:37 +1100				incoming
194	followup_sent	2012-12-18 13:38:37 +1100	waiting_response	2012-12-18 13:38:52 +1100	waiting_response	outgoing
202	response	2012-12-19 17:17:30 +1100	waiting_clarification	2012-12-19 20:29:06 +1100	waiting_clarification	incoming
203	followup_sent	2012-12-19 20:41:31 +1100	waiting_response	2012-12-19 20:41:31 +1100	waiting_response	outgoing
204	response	2012-12-20 09:39:28 +1100	waiting_response	2012-12-20 11:30:04 +1100	waiting_response	incoming
294	response	2013-01-14 09:06:46 +1100				incoming
305	followup_sent	2013-01-15 11:06:46 +1100	waiting_response	2013-01-15 11:07:01 +1100	waiting_response	outgoing
331	response	2013-01-18 16:53:10 +1100				incoming
52767	overdue	2013-01-19 00:00:00 +1100
336	followup_sent	2013-01-21 10:44:05 +1100	waiting_response	2013-01-21 10:45:34 +1100	waiting_response	outgoing
356	response	2013-01-24 16:28:39 +1100				incoming
360	followup_sent	2013-01-24 16:51:44 +1100	waiting_response	2013-01-24 16:52:30 +1100	waiting_response	outgoing
373	response	2013-01-29 15:14:45 +1100	waiting_response	2013-01-29 21:31:17 +1100	waiting_response	incoming
55137	very_overdue	2013-02-19 00:00:00 +1100
520	followup_sent	2013-02-19 10:35:56 +1100				outgoing
558	response	2013-02-27 10:53:26 +1100				incoming
559	followup_sent	2013-02-27 11:15:28 +1100	waiting_response	2013-02-27 11:15:36 +1100	waiting_response	outgoing
562	comment	2013-02-28 08:47:33 +1100
563	response	2013-02-28 09:02:15 +1100		2013-02-28 15:03:36 +1100	waiting_response	incoming
565	comment	2013-02-28 10:35:56 +1100	waiting_response
569	followup_sent	2013-03-03 14:06:23 +1100				outgoing
586	followup_sent	2013-03-05 18:16:35 +1100				outgoing
588	response	2013-03-06 09:34:37 +1100	waiting_response	2013-03-06 16:01:39 +1100	waiting_response	incoming
591	followup_sent	2013-03-06 16:06:21 +1100				outgoing
596	response	2013-03-07 09:38:34 +1100	waiting_response	2013-03-07 11:15:45 +1100	waiting_response	incoming
598	comment	2013-03-07 12:11:27 +1100
605	response	2013-03-07 16:35:52 +1100	successful	2013-03-07 21:22:13 +1100	successful	incoming
612	response	2013-03-08 11:34:37 +1100	successful	2013-03-08 12:32:42 +1100	successful	incoming
635	comment	2013-03-16 13:40:18 +1100

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.