{"action":"created","issue":{"url":"https://api.github.com/repos/digitalmethodsinitiative/dmi-tcat/issues/236","repository_url":"https://api.github.com/repos/digitalmethodsinitiative/dmi-tcat","labels_url":"https://api.github.com/repos/digitalmethodsinitiative/dmi-tcat/issues/236/labels{/name}","comments_url":"https://api.github.com/repos/digitalmethodsinitiative/dmi-tcat/issues/236/comments","events_url":"https://api.github.com/repos/digitalmethodsinitiative/dmi-tcat/issues/236/events","html_url":"https://github.com/digitalmethodsinitiative/dmi-tcat/issues/236","id":181189929,"number":236,"title":"imported tweets dated two hours earlier?","user":{"login":"arnoutponsioen","id":17899995,"avatar_url":"https://avatars.githubusercontent.com/u/17899995?v=3","gravatar_id":"","url":"https://api.github.com/users/arnoutponsioen","html_url":"https://github.com/arnoutponsioen","followers_url":"https://api.github.com/users/arnoutponsioen/followers","following_url":"https://api.github.com/users/arnoutponsioen/following{/other_user}","gists_url":"https://api.github.com/users/arnoutponsioen/gists{/gist_id}","starred_url":"https://api.github.com/users/arnoutponsioen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/arnoutponsioen/subscriptions","organizations_url":"https://api.github.com/users/arnoutponsioen/orgs","repos_url":"https://api.github.com/users/arnoutponsioen/repos","events_url":"https://api.github.com/users/arnoutponsioen/events{/privacy}","received_events_url":"https://api.github.com/users/arnoutponsioen/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2016-10-05T15:36:26Z","updated_at":"2016-10-11T07:56:04Z","closed_at":null,"body":"Hi,\r\n\r\nI am currently testing importing tweets using parse-csv.php and lookup.php based on tweet-urls.\r\nThat works fine (thanks @ErikBorra for helping me out).\r\n\r\nBut... when I look closely at the time stamps of imported tweets in TCAT, I find a two hour difference between the time stamp of imported tweets in TCAT, and the time stamps of tweets when you accessed manually in the browser. Eg. https://twitter.com/GoensEls/status/782513615370846210 is dated Oct 2, 11:32 (as can ben seen using a browser), but imported in TCAT it is dated on Oct, 9.32 (two hours earlier).\r\n\r\nThis time difference also accurs when tracking tweets with TCAT.\r\n\r\nAny idea why this time difference is accuring and what to do about it?\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/digitalmethodsinitiative/dmi-tcat/issues/comments/252839343","html_url":"https://github.com/digitalmethodsinitiative/dmi-tcat/issues/236#issuecomment-252839343","issue_url":"https://api.github.com/repos/digitalmethodsinitiative/dmi-tcat/issues/236","id":252839343,"user":{"login":"dentoir","id":5476482,"avatar_url":"https://avatars.githubusercontent.com/u/5476482?v=3","gravatar_id":"","url":"https://api.github.com/users/dentoir","html_url":"https://github.com/dentoir","followers_url":"https://api.github.com/users/dentoir/followers","following_url":"https://api.github.com/users/dentoir/following{/other_user}","gists_url":"https://api.github.com/users/dentoir/gists{/gist_id}","starred_url":"https://api.github.com/users/dentoir/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dentoir/subscriptions","organizations_url":"https://api.github.com/users/dentoir/orgs","repos_url":"https://api.github.com/users/dentoir/repos","events_url":"https://api.github.com/users/dentoir/events{/privacy}","received_events_url":"https://api.github.com/users/dentoir/received_events","type":"User","site_admin":false},"created_at":"2016-10-11T07:56:04Z","updated_at":"2016-10-11T07:56:04Z","body":"Hi @arnoutponsioen \r\n\r\nThe timestamps you see from tweets which you imported or tracked are currently _always_ in UTC. You will solely see UTC timestamps in the front-end panel and also in the export files. This explains the time difference of two hours, which is correct. There is no support yet unfortunately for using a different timezone on the visualization or the export side. This used to exist, but caused a bug. (Issue #197 fixed previous problems surrounding this.). Until we implement this again, you will need to be aware of this, and/or use some date transformation in Excel and other chained tools.\r\n\r\n"}}
{"actor":{"display_login":"dentoir"}}