Reproducible Research Workflows


Level: Intermediate Status: Pre-Alpha

The Carpentries pre-alpha Stage

The lesson is in early design and development. Content is likely incomplete and subject to significant changes.
Start Lesson

About this Lesson

Focuses on helping librarians understand the concept of reproducibility and learn about both theoretical and practical aspects of reproducible research workflows across different disciplines.

Learning Objectives

  • Explain what research reproducibility is and list benefits/challenges.
  • Explain how different disciplines define reproducibility differently.
  • Provide examples of reproducible research workflows.
  • List and use tools for increasing research reproducibility.
  • Provide examples of how libraries can support research reproducibility.

Keywords

reproducibilityworkflowopen sciencetools

Help Improve this Curriculum

This lesson is currently in the pre-alpha phase. This curriculum is in its early stages. Keep an eye on this space for future updates.


For more on how to run a pilot, visit The Carpentries Handbook.

Instructor Specs
  • Duration: 90m - 3h (estimated)
  • Level: Intermediate
  • License: CC-BY 4.0
Cite this Lesson

APA Format:

Bochynska, A. (2026). Reproducible Research Workflows. UCLA IMLS Open Science. https://ucla-imls-open-sci.info/lessons/reproducible-research-workflows

BibTeX:

Show BibTeX
@misc{reproducible_research_workflows_2026,
  author = {Agata Bochynska},
  title = {Reproducible Research Workflows},
  year = {2026},
  publisher = {UCLA IMLS Open Science},
  url = {https://ucla-imls-open-sci.info/lessons/reproducible-research-workflows}
}
Repository Health
  • Last updated: May 2025
  • Contributors: 4 people
  • Open discussions: 3
What does this mean?

These signals come from the lesson's GitHub repository — the place where authors store and update the curriculum. Last updated tells you when the lesson materials were most recently changed. Contributors counts how many people have worked on it. Open discussions are questions, bug reports, or improvement suggestions that haven't been resolved yet — a higher number can mean active community interest or areas the lesson is still refining. Together they give a sense of whether the lesson is actively maintained.

Updated weekly from GitHub.

Authors

Agata Bochynska
Agata Bochynska
Open Research Coordinator