This wiki is the central knowledge and documentation base of the SMO. The bleeding-edge, editable version can be found here, the less frequently updated, but better reviewed, ‘pretty’ version waits here.
If you want to learn more about us, or share this project with others, we have a landing page.
I want to contribute!
Yay! Here you will find instructions how to add or edit pages:
How to use and maintain the wiki
Any questions? Raise an Issue! :)
Code of Conduct
By contributing to this wiki you agree to follow our Code of Conduct.
Blank Spots in the Wiki
Because we’re just starting out, some sections are not much more than a heading. So here are some explanations what to expect there.
We are working on and invite contributions to this section, where we plan to collect advice on common issues when working with (social) media data.
Also, if you have basic, but crucial, social media knowledge to share (for example overall measurement baselines for certain platforms or demographics) or examples of instructive (un)successful case studies (not necessarily your own), feel free to create the first pages in the Knowledge Base section.
- Case Studies: Examples for data analytics in computational communication research
- Projects: A selection of current projects to be aware of
👏💫🏆 Wall of Fame 🏆💫👏
We have an ongoing authorship statistic that will be used to acknowledge authors in future publications based on this wiki (e.g. in form of a citations for a Figshare or OSF project):
🌟🌟🌟 The Wall of Fame 🌟🌟🌟
If you want to be properly acknowledged, make sure to use your clear name on Github when editing. Otherwise it’ll be hard for us to properly acknowledge you. However, pseudonymous contributions are always welcome and will be counted.
Please Cite as
Münch, F. V., Asli, M. L., Young, J., Khandoker Tanjim Ahammad, Wiedemann, G., Rau, J., Schmidt, J.-H., & Puschmann, C. (2021). SMO Wiki. https://doi.org/10.6084/M9.FIGSHARE.14465337
As this is a wiki, the citation will continuously change over time and versions regarding authors and their order, so please check back regularly and always state the date or commit hash at which you accessed it. We are in the process of working out the details of versioning this in the most appropriate way.