Studies and experiments
How studies and experiments relate to projects in the current product.
Status: Partially available (no Study UI; experiments exist in data/API layers)
Studies
OVAITY does not currently provide a first-class Study entity or /studies routes in the application UI.
Closest researcher-facing concepts:
- Project — the workspace boundary
- Samples — shared units across assays on the project overview
- Datasets — data assets linked to samples and analyses
Marketing or onboarding copy may mention “studies”; treat that as product language for structured project work, not a separate object type.
Experiments
Experiments are stored and used when the product generates reports and Ovaitions. They are not a project tab, and there is no partner tool that retrieves them.
What this means for users today:
- Day-to-day experiment tracking in the UI is through project samples, datasets, the notebook, analyses, and memory.
- Reports and Ovaitions can draw on stored experiment records. That is not a separate Experiments screen.
Where related content lives
| Content | Location |
|---|---|
| Samples / sample map | Project overview |
| Dataset files and metadata | Files / Library / datasets surfaces |
| Analysis outputs | Analysis Studio / analysis runs / artifacts |
| Narrative context | Project labbook and memory |
| Reports | Project reports |
Current limitations
- No Study screen
- No Experiments tab under a project
- Experiment records are used behind reports and Ovaitions, not as their own page