Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Network analysis of retweets #19

Open
colditzjb opened this issue Aug 15, 2020 · 2 comments
Open

Network analysis of retweets #19

colditzjb opened this issue Aug 15, 2020 · 2 comments

Comments

@colditzjb
Copy link
Member

Several scripts that format tweet data for social network analysis have been developed for project-specific use cases but these are not broadly generalizable or consistent with newer RITHM conventions for handling input and output procedures. It will be beneficial to develop a script for consistent implementation of basic network analysis within the RITHM framework.

This will start with a procedure that (1) links retweet IDs to original tweet IDs that are present in existing metadata. Continued work will include (2) linking tweet response IDs to original tweet IDs and (3) linking quoted tweet IDs to original tweet IDs. This process should be flexible enough that these various relationships (1-3) can be handled separately and so that output can be aggregated for user-level analysis. Output should include well-formed dictionary objects (pickle format) that can be updated as new data are added, as well as node and edge files (TSV format) that can be used in third-party analysis software.

@wbaker23
Copy link
Contributor

wbaker23 commented Dec 6, 2020

@colditzjb Could you expand upon this in our meeting tomorrow? I'd like to start developing this for my final project in Justin Zhan's Data Mining class I am taking this semester.

@colditzjb
Copy link
Member Author

colditzjb commented Dec 7, 2020

@wbaker23 Sure thing! The most recent script that I had developed for this is: /home/jcolditz/twitter/RITHM/parser/network.py

It's not ready for deployment, but it is a good starting point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants