|
| 1 | +--- |
| 2 | +layout: nl |
| 3 | +title: CODECHECK-NL Workshop for Digital Humanities |
| 4 | +permalink: /nl/workshop4 |
| 5 | +--- |
| 6 | + |
| 7 | +## CALL FOR PAPERS/PRE-PRINT/CODE: Contribute to improving reproducibility in the Digital Humanities! |
| 8 | + |
| 9 | +**Are you from the Digital Humanities and interested in reproducible code and open science? We have the perfect opportunity for you!** |
| 10 | + |
| 11 | +As part of our NWO project [CHECK-NL](https://codecheck.org.uk/nl), **we are looking for researchers from the Digital Humanities at a Dutch knowledge or university who would like their papers or projects to be “codechecked” during a live, one-day code-checking workshop on 14 February 2025**. A [codecheck](https://codecheck.org.uk/process/) is a light-touch independent peer review to check that your code and data can generate the computational results in your paper or project. |
| 12 | + |
| 13 | +You can participate as (a) by submitting your own work to be checked, (b) a codechecker (i.e., a person reviewing code as a participant in the workshop), or (c) both, if you are up for it! Read on to see how… |
| 14 | + |
| 15 | + |
| 16 | +## How do I submit my code, and what do I get? |
| 17 | +- A codechecker will work with you during the session to check whether your code and data can be run by others to generate the same or similar results. |
| 18 | +- The codechecker will work with you to resolve any issues found during the code check, and make your code as reproducible as possible! |
| 19 | +- Upon completion, your paper will receive a codecheck certificate that confirms your results could be reproduced. This can be shared, e.g., with potential journal editors, to enhance the visibility and reproducibility of your work. |
| 20 | + |
| 21 | +By participating, you contribute towards making science more open and transparent AND increase the visibility of your own research! |
| 22 | + |
| 23 | +## Sounds good! What should I do? |
| 24 | + |
| 25 | +Are you interested in participating in this event, and contributing to promoting code reproducibility? Send an email to [email protected] **by 24 January 2025 ** with a brief description of your paper/project, and links to your code and data. This could be code related to: |
| 26 | +- A paper that you have recently published |
| 27 | +- A preprint that is publicly available |
| 28 | +- Code and results files that have been or will be deposited in a repository, preferably GitHub or GitLab |
| 29 | + |
| 30 | +In each case, the code and data underlying the paper should be openly available, or you plan to make them available once the paper is published. |
| 31 | + |
| 32 | +*Selected papers/projects will be notified in early February 2025. All code authors are invited to join the workshop.* |
| 33 | + |
| 34 | +## What if I want to participate as a codechecker instead? |
| 35 | + |
| 36 | +You can register to participate in the workshop on the [registration page], and join us as a codechecker on 14 February. The event will be held in person in Leiden (see event page for details). |
| 37 | + |
| 38 | +What you can expect during the workshop: |
| 39 | +- An introduction to CODECHECK and a live demo |
| 40 | +- Beakout groups to CODECHECK a project yourself |
| 41 | +- A reflection session to share with us what you thought of CODECHECK and the workshop |
| 42 | +- Coffee, lunch, and snacks! |
| 43 | + |
| 44 | +## Why would I volunteer my time to code check other people's work? |
| 45 | +- You will learn how others ensure reproducibility of their work (and pick up tips for yourself!) |
| 46 | +- You will gain hands-on experience in peer reviewing code |
| 47 | +- You will be contributing to more transparent science |
| 48 | + |
| 49 | +Interested but still have questions? Ask us! |
| 50 | +Write to us at [email protected], we are happy to answer any questions! |
0 commit comments