STRATA
Skip to study
XLVII

X.12 / SHARED INSTRUMENTS

Data, code, licenses, and executable research records

Which data, software versions and permissions does a reader need to repeat a published computation?

A source-led introduction1 source references0 related experiments

Start with the question.

Executable research records join data, code, parameters, environment information, and an explanation of how the result was produced. FAIR principles provide a useful framework for making these objects discoverable and reusable. A complete record also identifies the stated license and access conditions for each component. The goal is a result another reader can inspect and rerun with a clear account of its dependencies.

Package one figure as a reproducible record.

Take a small plot and include its input file, transformation script, parameter values, dependency versions, and expected output. Add a checksum for the input and a short explanation of the axes. Run it in a clean environment when feasible, recording the actual result separately from the instructions and expected behavior.

What would you inspect?

  • Stable identifiers, data provenance, dependency versions, parameters, and stated licenses.
  • The observed rerun result and any differences from the archived output.

Take the next step.

Prepare one complete research bundle for a site visualization and record a real execution before labeling it reproduced.

Read the supporting material.

  1. The FAIR Guiding Principles for scientific data management and stewardship

    Mark D. Wilkinson and coauthors · Findable, accessible, interoperable, and reusable research data and metadata.

Continue through the versioned study records.

Follow the comparisons.

Read the neighboring questions.