Twitter data: Using the tweet variables

13.07.2018, 16:24

What is the best way to expose the fields in imported Twitter data as variables in order to perform analysis and observing statistical associations?

When Twitter data is imported, it comes with 16 variables:
1: Date/Time
2: Tweet
3: Hashtags
4: Author
5: Author’s real name
6: Author's location
7: Author’s timezone
8: Author’s URL
9: Author’s description
10: Followers
11: Follows
12: Tweets
13: Profile verified
14: Profile created
15: Retweets
16: Likes

If one wanted to check associations or correspondence between, say a code derived from the hashtag (3) and Author's location (6) or Author’s timezone (7), how would that be done in the best way?

The autocode feature only works for author and hashtag, and the other 14 tweet variables do not seem readily accessible for use as MaxQDA variables or codes.

It seems like a good way is to export the tweets as a spreadsheet, and then reimport and allow the 16 tweet variables to be seen as MaxQDA variables or codes. Is there a better way maybe?

-Matthew

Version: MAXQDA 2018
System: Windows 7
mloxton
 
Posts: 117
Joined: 28.02.2014, 19:38
Location: Washington DC & Denver Colorado

Re: Twitter data: Using the tweet variables

16.07.2018, 10:07

Hi Matthew,

thanks for the question! I also think the survey-import is the best/only way to make the twitter-data usable for all the major features. Maybe it would be a good idea to create a new project file for this.
Kind regards,

Andreas
MAXQDA Support Team
Andreas V.
 
Posts: 272
Joined: 13.04.2017, 16:23

Re: Twitter data: Using the tweet variables

17.07.2018, 17:00

Thanks Andreas, much appreciated
mloxton
 
Posts: 117
Joined: 28.02.2014, 19:38
Location: Washington DC & Denver Colorado

Return to Technical Questions

Who is online

Users browsing this forum: Bing [Bot] and 5 guests

We use cookies to improve your experience on our website. By clicking OK or by continuing to browse the website, we’ll assume that you are happy with their use. Click here to review our Cookie Policy. OK