Hey everyone! Here's a quick demo of Part Two
of my project. Tweet ID. Let's start the
server. Okay, great Tweet ideas of web app
I made to help facilitate collaboration involving tweet collections.
All right, let's go ahead and upload a new
collection into tweet ID. First we click on either
the blue upload button or the upload tab in the
nav bar. Now we need to enter the information
about the collection. The reason I had the user
type the information rather than supply it in the file
like the tweets is because with the data I saw
the met information currently wasn't stored in a structured format
. Okay, that's all the meta info. Now
let's go ahead and select a file to upload.
Tweeted currently supports comma or tab separated values or Jason
files exported from your trapper keeper. I'm actually going
to skip submitting here since I've already loaded this collection
into tweet ID. Moving on the collections tab presents
a summary of the collections that are currently stored in
tweet id. As you can see the collections are
organized by organization in order to ensure there's a manageable
amount of information on the screen. Only one collection
pure organization is visible. If we click on the
title we can expand the other collections. Like so
one thing to notice here is that the first tweet
date in the last tweet date fields have been appended
to the collection. That information wasn't present before the
upload Tweet ID was designed to allow intelligent extraction of
collection level metadata in a very modular fashion. Only
the 1st 10 tweets are shown for each collection but
we can click on the more tweets but now we're
on the collection detail screen here. We see more
detailed information about the collection as well as the full
list of tweets as you can see the tweets have
been paginated. If we click on one of these
other pages we can browse through the tweets in this
collection. One additional benefit the collection detail page provides
is a unique Ural for a given collection. This
could potentially be used as an identify where in a
metadata format. All right, let's move on to
the tweets tab the tweets tab lists all of the
tweets that have been stored in tweet ID. One
important thing to note is that the body of the
tweets is not stored anywhere in tweet ID. Since
that would be against twitter's terms of service. As
you can see, we currently have about three million
tweets and tweets. I'd like the collection detail page
. The tweets page is also paginated. Another feature
of tweet ID is the tweet details page you may
have noticed on this screen or previous screens that tweet
IEDs are link Ified. If you click on one
of these links, you're taken to the unique ural
for that tweet tweet slash tweet ID. The tweet
details page goes into further detail about the tweet metadata
. At the bottom you can see the standard twitter
Jason which was generated from the input format. Name
spacing has been added for extensive bility reasons. Tweet
Id has one final important feature. You may have
noticed this merge toggle button earlier. If we select
at least two collections, we can merge them together
to get a more inclusive collection. Let's select use
your eyes and Virginia text collections about the Oklahoma tornado
. Then we just hit merge. The merging process
can take a little time since the collections are both
quite sizable. Okay. The merge is completed and
we can now see the newly emerged collections. The
new collection has almost three million tweets. The organizations
now list both qc ri and Virginia Tech. The
key words have been union and and the start and
end times have been modified. As you can see
all of the tweets are listed and paginated as on
other collection detail pages. The final page is just
to contact page, which currently just has links to
my linkedin and facebook. That's Tweet ID. Thanks
for watching.