New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TweetUtils - support fulltext #192

Closed
ruebot opened this Issue Apr 6, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@ruebot
Member

ruebot commented Apr 6, 2018

Since the expanded tweet move in early 2017, and the move to 280 characters, the text of tweet will be found in .full_text instead of .text.

https://developer.twitter.com/en/docs/tweets/tweet-updates

@greebie

This comment has been minimized.

Show comment
Hide comment
@greebie

greebie Apr 6, 2018

Contributor

Going through the twitter ingestion script, it might be nice to include a few other things if possible from the api. Retweet_count for instance. Possibly things like "location" and "in_reply_to" depending on how far we want to go with that and ethical considerations.

Here's a short list from my perspective and maybe we can check the things we want to include, and then we can fix things all together:

  • in_reply_to_status_id
  • in_reply_to_user_id
  • source (mobile or web interface)
  • entities/user_mentions
  • entities/urls
  • entities/hashtags (could replace the hashtag extractor we have in aut)
  • retweeted (true / false)
  • place
  • retweet_count
  • retweet_status { provides another tweet object so maybe not }
  • user/profile_image
  • user/description
  • user/time_zone
  • user/location
  • user/name
  • user/url

This is just a rough list of possible candidates. Not necessarily suggesting we should ingest them all or even one. Just think it's worth looking at while we fix TweetUtils.

Contributor

greebie commented Apr 6, 2018

Going through the twitter ingestion script, it might be nice to include a few other things if possible from the api. Retweet_count for instance. Possibly things like "location" and "in_reply_to" depending on how far we want to go with that and ethical considerations.

Here's a short list from my perspective and maybe we can check the things we want to include, and then we can fix things all together:

  • in_reply_to_status_id
  • in_reply_to_user_id
  • source (mobile or web interface)
  • entities/user_mentions
  • entities/urls
  • entities/hashtags (could replace the hashtag extractor we have in aut)
  • retweeted (true / false)
  • place
  • retweet_count
  • retweet_status { provides another tweet object so maybe not }
  • user/profile_image
  • user/description
  • user/time_zone
  • user/location
  • user/name
  • user/url

This is just a rough list of possible candidates. Not necessarily suggesting we should ingest them all or even one. Just think it's worth looking at while we fix TweetUtils.

@ruebot

This comment has been minimized.

Show comment
Hide comment
@ruebot

ruebot Apr 6, 2018

Member

@greebie sounds like a separate issue. Can you create one?

Member

ruebot commented Apr 6, 2018

@greebie sounds like a separate issue. Can you create one?

@greebie greebie referenced this issue Apr 6, 2018

Open

More complete Twitter Ingestion #194

10 of 16 tasks complete

@ruebot ruebot self-assigned this Aug 10, 2018

ruebot added a commit to ruebot/aut that referenced this issue Aug 10, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment