Platform
How EpistaBase organizes your work
The lab-facing hierarchy behind projects, experiments, runs, samples, and data entries.
EpistaBase uses a hierarchy that mirrors wet-lab work:
Workspace Your lab or program boundary.
Project A research goal or campaign.
Experiment One scientific question and its record.
Run One execution of the assay.
Sample Biological material from that run.
Data entry An analyzable file or parsed dataset.Terms you will see
| Term | Plain meaning |
|---|---|
| Workspace | The lab or organization space you are working in. |
| Project | A group of related experiments and collaborators. |
| Experiment | The question, protocol snapshot, runs, samples, data, analyses, notes, and figures. |
| Run | One execution, such as one acquisition, plate, sequencing batch, or protocol attempt. |
| Sample | Biological material from a run. |
| File | The uploaded object and processing state. |
| Data entry | What a file means inside an experiment. |
| Catalog asset | A governed data or analysis object that can be searched, opened, queried, and traced. |
Why File and Data entry are separate
A File is storage and processing state: original bytes, checksum, preview, parser metadata, and upload status.
A Data entry is scientific meaning: this FCS file belongs to this experiment, run, sample, and assay context.
That separation is what lets EpistaBase keep raw files, parsed tables, viewers, and lineage connected without making users manage storage details.
Programs are optional
Programs can group work at a higher level, but Projects and Experiments are the main product path. Treat a Program like a label or portfolio grouping, not the place where assay data lives.