Submissions

Author Guidelines

Please follow the instructions below when submitting yor manuscript. Feel free to contact us at info@computationalcommunication.org for any questions about scope, format, or procedures around submissions.

Note that our journal uses LaTeX for typesetting. After acceptance, we expect authors to use our LaTeX template:

For initial submissions, using APA7 style (e.g., produced with Word or LibreOffice) instead of the LaTeX template is acceptable.

• Use our LaTeX template (see above).
• Initial submissions can alternatively follow APA style (7th edition) for manuscript, references, and figures. In case of acceptance, you should re-format your manuscript using aforementioned LaTeX template, though.
• Include an abstract that should generally not exceed 200 words.
• Use American English.
• Submissions should not contain information that identifies the author. Self-citations are permitted, but where obvious replace by (Author, 2017).   External links to identifiable resources such as authors’ github repositories should be removed from the initial submission. Please make sure the filename and file properties do not contain your name.
• Research articles should be at most 9,000 words in length (including bibliography and tables)
• Research notes should be at most 4,000 words and should focus on describing empirical results. They should contain a short theoretical introduction to link the research with the relevant communication science theory, but references and theoretical discussion should be kept to a minimum.
• Descriptions of novel tools and data sets should be at most 4,000 words and describe a publicly accessible and novel (or major revision of a) tool or data set relevant to the communication science community. The manuscript should contain a link to the tool or data in question and describe the relevance and intended working and purpose of the tool or data. For tools, code examples or screenshots describing common use cases are encouraged.
• For publishing software tools, please refer to the Nature editorial “Does your code stand up to scrutiny?” (Nature 555, 142, 2018) and checklist.
• For publishing data, please archive the data in a repository that guarantees persistence.
• For both tools and data, the repository or archive may be kept private until acceptance, but should be publicly accessible on publication of the description. If the tool or data cannot be made accessible due to business, legal, or ethical constraints, please contact the editor before submitting the manuscript.