Difference between revisions of "AY1516 T2 Team AP Analysis"
| Line 38: | Line 38: | ||
==<div style="background: #232AE8; line-height: 0.3em; font-family:helvetica; border-left: #6C7A89 solid 15px;"><div style="border-left: #FFFFFF solid 5px; padding:15px;font-size:15px;"><font color= "#ffffff"><strong>Twitter API Exploration</strong></font></div></div>== | ==<div style="background: #232AE8; line-height: 0.3em; font-family:helvetica; border-left: #6C7A89 solid 15px;"><div style="border-left: #FFFFFF solid 5px; padding:15px;font-size:15px;"><font color= "#ffffff"><strong>Twitter API Exploration</strong></font></div></div>== | ||
| + | |||
| + | <p></p> | ||
Revision as of 16:43, 25 February 2016
| Data Retrieval | Data Manipulation | Findings |
|---|
Initial Dataset provided by SGAG
During our initial meeting with SGAG, they provided several data files with information regarding their social media accounts. Upon further inspection, we realised that the data provided were largely aggregate data, and even if we attempted to load it into data analysis tools like Gephi/Graphwiz to analyse SGAG's social network, it would not be a correct representation. In addition, the Tweet Activity Metrics could not show how popular each post was to specific users, rendering the data fairly unusable.
Hence, we decided to retrieve the data ourselves from Twitter, in attempt to visualise SGAG's social network that included specific users, instead of aggregated data. We attempted this by leveraging on the Twitter public API, to tailor to our data collection needs.
