The document is a Twitter data deposit form detailing the collection of tweets related to the Egyptian Revolution from January 30 to March 8, 2011. It reports capturing 420,000 tweets from approximately 40,000 unique users, with data displayed on the Hypercities platform, and confirms that the data set contains only public tweets. The researcher sought university guidance on potential risks and adhered to Twitter's geo developer guidelines in handling location data.

1. Sample Twitter Data Deposit Form
Kris Kasianovitz. November, 2011
P.I. Name Todd Presner
University/College Affiliation UCLA Germanic Languages
Address BOX 951539, 212 RH, Los Angeles, CA 90095-1539
Email presner@ucla.edu
Phone 310-794-6051
Research Assistant (if primary contact)
Use of Twitter in Egyptian Revolution merited some form of documentation. Wanted to
Reason for Capture capture Tweets in order to have long-term as well as to display via HyperCities Platform to
show where and what people were tweeting.
Currently being displayed via HyperCities, http://egypt.hypercities.com/ that enables one to
Researcher’s use of captured data
search captured tweets by keyword or display by date on a Google earth base map.
Includes Protected Accounts? No
If Yes, explain any steps taken to keep these
N/A
Tweets protected in your dataset.
Did you contact Twitter or the Twitter users to
No
inform them of data capture?
If yes, please upload all related documentation. N/A
Did you contact campus counsel, or receive any
university guidance about potential risks involved Yes
in making this data set available?
If yes, please upload all related documentation N/A
 Open, no restrictions
 Portions of data are restricted, contact PI
Restrictions on re-use/redistribution
 Restricted, contact PI
 Do not release. Archiving data only, not allowing re-use.
 REST API
 Search API (will be deprecated)
Capture Methods  Streaming API
 Licensed Data Set
 Other
Location = Center of Cairo within 200 miles
Capture Parameters AND
hashtag = (#jan25 OR #egypt OR #tahrir)
Capture Dates January 30-March 8, 2011
Capture Frequency
Daily within Twitter Rate Limits
(Daily, Weekly, Monthly, etc.)
Please note any anomalies or issues encountered On February 28, when setting up the captures, ran into a rate limit issue; was not able to
with capture. download data until the next day. Duplicate Tweets were removed.
Total Number of Tweets 420,000
Total Number of Unique User IDs approximately 40,000
Does the data set contain Latitude/Longitude
Yes.
Data? Y/N
If yes,
1. Lat/Lon and Twitter Location fields were captured
1. state specific fields captured
2. The majority of Tweets did not contain any data in the Lat/Long fields.
2. how many tweets contain these fields,
3. For display purposes in HyperCities, all locations are aggregated at the city level. We
3. did you recode, aggregate, or delete these
did not remove any Lat/Long Data from this data set.
fields from the data set being deposited?
Have you handled the Location data as required
in the Twitter Geo Developer Guideslines?
Yes/No
Yes.
If you are unsure, please review these guidelines
https://dev.twitter.com/terms/geo-developer-
guidelines
Does the data set contain ONLY public tweets?
Yes.
Y/N
Did you capture image files locally? No.