> ## Documentation Index
> Fetch the complete documentation index at: https://docs.galileo.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Datasets overview

> Manage test sets and training sets across all your projects.

The **Datasets** page (sidebar → **Datasets**) is where you manage every dataset in your org. Datasets are **org-scoped** — once added, they're available across every project for any training run.

<Frame caption="Datasets page with the Test sets and Training sets tabs">
  <img src="https://mintcdn.com/v2galileo/-aQkdd7oOglUYIo1/images/luna-studio/datasets/datasets-home.png?fit=max&auto=format&n=-aQkdd7oOglUYIo1&q=85&s=34d9415cc46d27582c40c677ceb21266" alt="Datasets page" width="1024" height="659" data-path="images/luna-studio/datasets/datasets-home.png" />
</Frame>

## Test sets vs. training sets

Luna Studio splits datasets into two flavors, accessible via tabs on the page:

<CardGroup cols={2}>
  <Card title="Test sets" icon="database" href="/luna-studio/ui/datasets/test-sets">
    Small, human-labelled datasets used to evaluate fine-tuned metrics. Required for every run.
  </Card>

  <Card title="Training sets" icon="dumbbell" href="/luna-studio/ui/datasets/training-sets">
    Larger datasets used to fine-tune the base model. Often generated from a test set.
  </Card>
</CardGroup>

## How datasets relate to runs

Each [training run](/luna-studio/ui/runs/lifecycle) consumes exactly one test set and one training set. The same dataset can be reused across many runs.

```mermaid theme={null}
flowchart LR
  TestSet1["Test set: context-adherence-test"] --> Run1["Run 1: context-adherence-run-1"]
  TrainSet1["Training set: context-adherence-train-v1"] --> Run1
  TestSet1 --> Run2["Run 2: context-adherence-run-2"]
  TrainSet2["Training set: context-adherence-train-v2"] --> Run2
```

The **Used in metric** column on the datasets table shows you which metrics' fine-tuning depends on a dataset — useful before deleting one.

## Source types

| Source  | What it means                                                                      |
| ------- | ---------------------------------------------------------------------------------- |
| Upload  | You uploaded a `.csv` or `.jsonl` file from your machine.                          |
| URL     | Luna Studio fetched the dataset from an http/https/s3/gs URL.                      |
| Galileo | Luna Studio pulled the dataset from a project in your connected Galileo workspace. |

For training sets specifically, an additional source applies:

* **Generated** — produced by the [Generate from test set](/luna-studio/ui/runs/new-run/step-3-training-set#generate-from-test-set) flow inside the run creation flow.

## Where to go next

<CardGroup cols={2}>
  <Card title="Test sets" icon="database" href="/luna-studio/ui/datasets/test-sets">
    What test sets are, schema rules, and best practices.
  </Card>

  <Card title="Training sets" icon="dumbbell" href="/luna-studio/ui/datasets/training-sets">
    What training sets are and how to create or reuse them.
  </Card>

  <Card title="Add a dataset" icon="upload" href="/luna-studio/ui/datasets/add-a-dataset">
    Reference for the three dataset sources (Upload, URL, Galileo).
  </Card>

  <Card title="Dataset validation" icon="circle-check" href="/luna-studio/ui/datasets/validation">
    What Luna Studio checks when you add a dataset.
  </Card>
</CardGroup>