Step 3: Send a dataset
What this step is
This step is recommended. Send a dataset, and the workflow of the workshop runs on it before the conference. I build a data package from it for you, you review it, and I publish it with a website and a DOI before the day. How much time you put in is up to you. One file is enough for me to work from, and you can add as much context as you like. Where I have questions, I ask them on the issue of your submission, so the answers stay documented. You see on data you know what the workflow asks of you and what comes out, so you can judge it for your own work. In the workshop we then spend less time on the mechanics and more on the elements of a published dataset and on the open questions.
Two kinds of dataset work:
- Your own data, or your group’s, that you may publish under CC BY 4.0.
- A published dataset by others under CC BY 4.0 or CC0 that you pick, for example from Zenodo or from the supplement of an article.
No dataset?
The survey of step 1 asks whether you plan to send a dataset. If you are not sure, or you have no data you can share, say so there and add a few words on what holds you back. I write back to you before the due date. Often there is a way in, for example a published dataset from your field. Your survey answer is not final, and you can submit until the due date. If you stay with no, you explore the packages of the other participants in the workshop.
How to submit
Submit by Friday, 11 December 2026. The form opens an issue on the repository of your workshop (sign in to GitHub first).
The form asks for a name, whose data it is, where it comes from, a brief description of the rows and the columns, and the data itself (a CSV, XLSX or ZIP file up to 25 MB dragged into the form, or the link to the published dataset). A brief description is enough. The data dictionary is built from it and comes back to you in the review. Three tick boxes confirm the conditions below. The issue and the attached file are public from the moment you submit, and the issue is where you follow the progress of your package.
Conditions
- The data holds no personal data, which means no names, addresses, GPS points of households or other details that identify a person.
- The data may be published under CC BY 4.0 or CC0, because it is yours or because its published licence says so. Check with your co-authors or your data owner if you are unsure.
- One dataset per submission. Small is fine. A few hundred rows show the workflow as well as a large file. Every submission is built, in the order it arrives.
Who is named on the package
- Your own data. You are an author of the package, together with the people who collected the data.
- A published dataset by others. You are an author of the package, because you chose the dataset and review its documentation. The original authors are listed as data contributors. I write to the corresponding author with the draft package and ask whether the original authors want to be authors of the package as well. They have three weeks to answer or to object before it is published. The licence allows the reuse, so the email is a courtesy and an invitation.
- The maintainer. I am the maintainer of every package and an author of none. The maintainer is the person responsible for keeping the package available. I answer the issues people open on it and fix what breaks. If the package is ever archived, I leave a note on it that says why and where the data went.
What you get
Each item links to the same part of a published example, guluswm, a household waste survey from Gulu City, Uganda.
- A public repository in the rawtoweb organisation (example) with the processed data, the code that processed it and a data dictionary.
- A website for the package with the documentation of every variable, the data as CSV and Excel downloads and an article with plots built from the data.
- A DOI on Zenodo and a citation that names the authors.
- A review round on the issue before anything goes public. Your own data is published only with your yes, and a republished dataset after the three weeks.
The website of your package is online first, for the review. The release and the DOI follow once you have said yes.