From Script to STAMPED Research Object
·9 mins
Four scenarios showing how to incrementally add STAMPED properties to a shell-based analysis using git, make, and singularity.
This section collects concrete, runnable examples that illustrate the STAMPED principles in action. Each example focuses on a specific practice or workflow and shows how it contributes to sound dataset version control.
Every example is tagged along four dimensions:
Most examples carry tags in several dimensions, because good practices tend to serve multiple goals at once.
You can explore the examples in several ways:
Examples are arranged to cover a spectrum of complexity:
Pick the level that matches your current setup and expand from there.
Each example has a state field in its front matter indicating its editorial status:
| State | Meaning |
|---|---|
uncurated-ai | AI-generated draft that has not yet been reviewed by a human. Details may be inaccurate or incomplete. |
wip | Work in progress — under active development, content may be incomplete or change significantly. |
final | Reviewed, curated, and ready for use. No banner is shown. |
Examples without a state field (or with state: final) are considered ready.