Getting started
Build a first workbook — wages in Yerevan, as a chart — commit it, and share it.
ARMID Lab Reference
How ARMID Lab works, and the YAML language its workbooks are written in.
ARMID Lab is where a problem about Armenia is worked through on the data ARMID (Armenia In Data) already collects, from a description of the problem to charts, maps and a shareable result, with little or no code.
This reference describes how the Lab is organised and defines the workbook language completely. It is written for analysts, researchers and teams who use the Lab in Ridgital’s console or in their organisation’s dashboard.
How the Lab is organised
| Concept | What it is |
|---|---|
| Problem | A title and a Markdown description of what is being worked out, and who it serves. |
| Workbook | A YAML file of named nodes; each node reads ARMID data or other nodes and produces a table. |
| Commit | A saved version of the workbook, with a message. Nothing is ever overwritten. |
| Dashboard | The outputs of a problem that matter, pinned and laid out, with the workbook’s parameters as controls. |
| Artifact | A snapshot of a problem at one commit — description, every node’s output, dashboard and YAML — behind a link of its own, shared with yourself, chosen people, your team or anyone with the link. |
Where to start
- New to the Lab: follow Getting started, which builds a small workbook from nothing in ten minutes.
- Writing a workbook: the Workbook language section lists every key, step, option and function, with examples.
- Sharing results: read Artifacts and sharing.
The data is always ARMID's
A workbook reads series that ARMID collects, by concept and place. It never names a source or a collector, cannot upload files and has no network access. Data that ARMID does not have yet becomes an ARMID collector first.