The repository contains an ongoing collection of tweets IDs associated with the novel coronavirus COVID-19 (SARS-CoV-2), which commenced on January 28, 2020. We used the Twitter’s search API to gather historical Tweets from the preceding 7 days, leading to the first Tweets in our dataset dating back to January 21, 2020. We leveraged Twitter’s streaming API to follow specified accounts and also collect in real-time tweets that mention specific keywords. To comply with Twitter’s Terms of Service, we are only publicly releasing the Tweet IDs of the collected Tweets. The data is released for non-commercial research use.
The associated paper to this repository can be found here: Tracking Social Media Discourse About the COVID-19 Pandemic: Development of a Public Coronavirus Twitter Data Set
The Tweet-IDs are organized as follows:
- Tweet-ID files are stored in folders that indicate the year and month of the collection (YEAR-MONTH).
- Individual Tweet-ID files contain a collection of Tweet IDs, and the file names all follow the same structure, with a prefix “coronavirus-tweet-id-” followed by the YEAR-MONTH-DATE-HOUR.
- Note that Twitter returns Tweets in UTC, and thus all Tweet ID folders and file names are all in UTC as well.
We have recently migrated our data collection to AWS. Because of our recent shift and upgrade of computing and network specifications, we're excited to announce that we are now able to collect (and consequently release) a significantly greater number of Tweet IDs. We will be continuing to leverage AWS for the foreseeable future - please be aware that from release v2.0 and onwards, there will be a significant increase in the number of Tweet-IDs contained in each hourly file. We are increasing the major version of the releases to reflect this change in collection infrastructure. No other parameters have changed (e.g. keywords tracked, accounts followed) that have not previously been documented, and there is not a gap in data collection as we switched to AWS, as we ensured that was an overlap in hours collected during the migration.
- We will be continuously maintaining this database for the foreseeable future, and will be uploading new data on a weekly basis.
- There may be a few hours of missing data due to technical difficulties. We have done our best to recover as many Tweets from those time frames by using Twitter’s search API.
- We will keep a running summary of basic statistics as we upload data in each new release.
- The file keywords.txt and accounts.txt contains the updated keywords and accounts respectively that we tracked in our data collection. Each keyword and account will be followed by the date we began tracking them, and date we removed them (if the keyword or account has been removed) from our tracking list.
- Consider using tools such as the Hydrator and Twarc to rehydrate the Tweet IDs. Instructions for both are in the next section.
- Hydrating may take a while, and Tweets may have been deleted since our initial collection. If that is the case, unfortunately you will not be able to get the deleted Tweets from querying Twitter's API. Ed Summers (edsu) hydrated the Tweets in release v1.0, taking approximately 25 hours to complete, and found that there was an approximate 6% of the Tweets that were deleted at the time of hydration, with final gzipped data size of 6.9 GB.
Hydrating using Hydrator (GUI)
Navigate to the Hydrator github repository and follow the instructions for installation in their README. As there are a lot of separate Tweet ID files in this repository, it might be advisable to first merge files from timeframes of interest into a larger file before hydrating the Tweets through the GUI.
Hydrating using Twarc (CLI)
Many thanks to Ed Summers (edsu) for writing this script that uses Twarc to hydrate all Tweet-IDs stored in their corresponding folders.
First install Twarc and tqdm
pip3 install twarc
pip3 install tqdm
Configure Twarc with your Twitter API tokens (note you must apply for a Twitter developer account first in order to obtain the needed tokens). You can also configure the API tokens in the script, if unable to configure through CLI.
twarc configure
Run the script. The hydrated Tweets will be stored in the same folder as the Tweet-ID file, and is saved as a compressed jsonl file
python3 hydrate.py
This dataset is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International Public License (CC BY-NC-SA 4.0). By using this dataset, you agree to abide by the stipulations in the license, remain in compliance with Twitter’s Terms of Service, and cite the following manuscript:
Chen E, Lerman K, Ferrara E Tracking Social Media Discourse About the COVID-19 Pandemic: Development of a Public Coronavirus Twitter Data Set JMIR Public Health Surveillance 2020;6(2):e19273 DOI: 10.2196/19273 PMID: 32427106
BibTeX:
@article{chen2020tracking,
title={Tracking social media discourse about the covid-19 pandemic: Development of a public coronavirus twitter data set},
author={Chen, Emily and Lerman, Kristina and Ferrara, Emilio},
journal={JMIR Public Health and Surveillance},
volume={6},
number={2},
pages={e19273},
year={2020},
publisher={JMIR Publications Inc., Toronto, Canada}
}Number of Tweets : 1,471,398,830
Language breakdown of top 10 most prevalent languages :
| Language | ISO | No. tweets | % total Tweets |
|---|---|---|---|
| English | en | 944,612,909 | 64.2% |
| Spanish | es | 190,216,727 | 12.93% |
| Portuguese | pt | 64,028,667 | 4.35% |
| French | fr | 44,746,214 | 3.04% |
| Undefined | und | 42,006,372 | 2.85% |
| Indonesian | in | 36,474,544 | 2.48% |
| German | de | 26,472,204 | 1.8% |
| Japanese | ja | 17,297,706 | 1.18% |
| Italian | it | 15,882,067 | 1.08% |
| Thai | th | 15,587,319 | 1.06% |
| Date | Time |
|---|---|
| 2/1/2020 | 4:00 - 9:00 UTC |
| 2/8/2020 | 6:00 - 7:00 UTC |
| 2/22/2020 | 21:00 - 24:00 UTC |
| 2/23/2020 | 0:00 - 24:00 UTC |
| 2/24/2020 | 0:00 - 4:00 UTC |
| 2/25/2020 | 0:00 - 3:00 UTC |
| 3/2/2020 | Intermittent Internet Connectivity Issues |
| 5/14/2020 | 7:00 - 8:00 UTC |
Please read through the README and the closed issues to see if your question has already been addressed first.
If you have technical questions about the data collection, please contact Emily Chen at echen920[at]usc[dot]edu.
If you have any further questions about this dataset please contact Dr. Emilio Ferrara at emiliofe[at]usc[dot]edu.