Accessible

The Accessible principle requires that once data is found, users need to know how it can be accessed. This involves:

Making data retrievable by their identifier using a standardized communication protocol.
Ensuring the protocol is open, free, and universally implementable.
Supporting authentication and authorization where necessary.
Making metadata accessible even when the data itself is no longer available.

STAMPED supports accessibility through practices like using standard transfer protocols (HTTP, SSH), hosting data in established repositories, providing clear access documentation, and maintaining metadata independently of data availability. Tools like git-annex and DataLad enable flexible access to data across multiple storage backends while keeping a consistent interface.

From Script to STAMPED Research Object

20 February 2026·9 mins

Reproducibility Rigor Transparency Reusable Accessible Pattern S — Self-contained T — Tracked A — Actionable M — Modular P — Portable E — Ephemeral D — Distributable Shell Posix Awk Make Git Singularity Containers

Four scenarios showing how to incrementally add STAMPED properties to a shell-based analysis using git, make, and singularity.

Datasette and MVC Pattern for Actionable Data Exploration

19 February 2026·8 mins

Transparency Efficiency Accessible Interoperable Pattern A — Actionable S — Self-contained Datasette Mvc Data-Exploration Sqlite

Shows how datasette turns static datasets into interactive, queryable web applications following an MVC-like pattern.

Ephemeral Shell Scripts for Reproducing Issues

19 February 2026·6 mins

Reproducibility Rigor Transparency Reusable Accessible Pattern S — Self-contained A — Actionable E — Ephemeral P — Portable Shell Posix Reproducer Bug-Report Testing

Distills a common practice among open-source developers: writing throwaway shell scripts that set up a fresh environment, reproduce a problem, and can be shared as actionable bug reports or starting points for test cases.