[Dataset] Analysis of ego-networks of two CS-related Twitter accounts
<p><strong>Explanation/Overview:</strong></p>
<p>This is the dataset for the analyses and results on Twitter Ego-Networks of two CS-related accounts (<a href="https://twitter.com/EuCitSci">@EuCitSci</a> & <a href="https://twitter.com/SciStarter">@SciStarter</a>). The username have been anonymised.</p>
<p><strong>Purpose:</strong></p>
<p>The purpose of this dataset is to provide the basis to reproduce the results reported in the associated deliverable. As such, it <strong>does not</strong> represent <strong>raw data</strong>, but rather files that already include certain analysis steps (like calculated degrees or other SNA-related measures), ready for analysis, visualisation and interpretation with R or any other network visualisation software (e.g., Gephi). The edges represent the follow relation and were retrieved using the Twitter API. All usernames except those of the two ego-accounts were anonymised by assigning a random number to each node. Due to the size of the network, we do not include any <code>.gexf </code>or <code>.gml </code>files in this upload, but rather resort to node and edge lists in the <code>.json</code> format</p>
<p><strong>Relatedness:</strong></p>
<p>The networks are the ego-networks for two related public accounts that are associated with citizen science (<a href="https://twitter.com/EuCitSci">@EuCitSci</a> & <a href="https://twitter.com/SciStarter">@SciStarter</a>).</p>
<p><strong>Content:</strong></p>
<p>In this Zenodo entry, two files can be found.</p>
<ul>
<li><code>edges.json</code></li>
</ul>
<p>Represents the edge list, with the columns:</p>
<table>
<tbody>
<tr>
<td><code>source</code></td>
<td><code>target</code></td>
<td><code>wherefrom</code></td>
<td><code>account</code></td>
</tr>
<tr>
<td>EuCitSci</td>
<td>23929</td>
<td>friendslist</td>
<td>EuCitSci</td>
</tr>
</tbody>
</table>
<p><code>Source</code> and <code>target</code> are the necessary columns for the network creation and in this example indicate that EuCitSci follows 23929. <code>wherefrom </code>indicates the origin of this relation in the crawling (i.e., whether it was retrieved using the friends or follower list) and <code>account </code>indicates the ego-account it belongs to. Thus, the edges can also be separated using this <code>account </code>attribute as they represent two distinct networks.</p>
<ul>
<li><code>nodes.json</code></li>
</ul>
<p>Represents the nodes in the networks. The following data fields are contained:</p>
<table>
<tbody>
<tr>
<td><code>username</code></td>
<td><code>CS</code></td>
<td><code>followers_count</code></td>
<td><code>friends_count</code></td>
<td>...</td>
</tr>
<tr>
<td>1116</td>
<td>CS</td>
<td>689</td>
<td>514</td>
<td>...</td>
</tr>
</tbody>
</table>
<table>
<tbody>
<tr>
<td>...</td>
<td><code>favourites_count</code></td>
<td><code>listed_count</code></td>
<td><code>statuses_count</code></td>
<td>...</td>
</tr>
<tr>
<td>...</td>
<td>2601</td>
<td>18</td>
<td>2141</td>
<td>...</td>
</tr>
</tbody>
</table>
<table>
<tbody>
<tr>
<td>...</td>
<td><code>degree</code></td>
<td><code>in_degree</code></td>
<td><code>out_degree</code></td>
<td>...</td>
</tr>
<tr>
<td>...</td>
<td>21</td>
<td>5</td>
<td>16</td>
<td>...</td>
</tr>
</tbody>
</table>
<table>
<tbody>
<tr>
<td>...</td>
<td><code>reciprocity</code></td>
<td><code>account</code></td>
</tr>
<tr>
<td>...</td>
<td>0.48</td>
<td>EuCitSci</td>
</tr>
</tbody>
</table>
<p> </p>
<p><code>Username </code>represents the numerical and anonymised username, <code>CS</code> the community-membership. The different counts (e.g., <code>followers_count</code>) indicate the number of followers the user had at the time of the retrieval by the Twitter API. <code>degree</code> refers to the degree in the network (similarly the <code>in-</code> and <code>out_degree</code>), while <code>reciprocity</code> refers to the number of mutual edges in respect to the total number of edges per node (see <a href="https://networkx.org/documentation/stable/reference/algorithms/generated/networkx.algorithms.reciprocity.reciprocity.html">here</a>). <code>Account</code> is similar as described above.</p>
<p> </p>
<p><strong>Grouping:</strong></p>
<p>The data is grouped according the ego-account it is associated to, as can be read above (i.e., the <code>account</code> attribute).</p>
opencc-by-4.0Nov 2022View details →