# Core concepts

To organize data for labeling and neural net training is not an easy task. If there is no structure, things get messy pretty quick. Learn those essentials to organize your efficiently. ☝️

## 🗂️ Projects

Project is a combination of datasets and related meta information (like classes and tags) and it's a major building block of data organization in Supervisely.

{% content-ref url="/pages/-M54fC5kfcVDMQPT05GQ" %}
[Broken mention](broken://pages/-M54fC5kfcVDMQPT05GQ)
{% endcontent-ref %}

## 📂 Datasets

This is where your labeled and unlabeled images, videos and point clouds live. A dataset is some sort of data folder with stuff to annotate.

{% hint style="success" %}
You can upload images multiple times, but only one copy will be stored inside Supervisely. This approach allows us to effectively work with cloud storage. Also this has a good effect on system performance and backup speed.
{% endhint %}

{% content-ref url="/pages/-M54fC5lCGh1KuU-VTCW" %}
[Broken mention](broken://pages/-M54fC5lCGh1KuU-VTCW)
{% endcontent-ref %}

## 📖 Definitions

Definitions tab is for managing the classes and tags used in the project. This tab allows you to create, edit and delete object classes and tags.

### 🎨 Classes

Classes are pre-defined types of your annotations, for example `Person` or `Background`. Thus, every label you create has defined class.

### 🏷️ Tags

To associate some extra information with annotations (or images, or videos, ...) you can define a Tag, for example `Needs review`.

{% content-ref url="/pages/bjYPjkKuRAhywYT2m24B" %}
[Broken mention](broken://pages/bjYPjkKuRAhywYT2m24B)
{% endcontent-ref %}

## Example

For instance, in [Team](/collaboration/teams.md) "Driving Division" you can have a **Workspace** "Pre-Labeling". In this Workspace you can have a Project "Cityscapes" with two Datasets: "Zurich" and "Stuttgart".

There are several classes defined in this Project (and, thus, in every Dataset): a building, a traffic light, a vehicle and so on. All classes are set to the "bitmap" shape, so that there is no way someone will accidentally create some "Cars" with polygon tool (a set of points), and some "Cars" with bitmap tool (a set of pixels).

Also, there are two tags defined: a "vehicle\_type" of several pre-defined options ("Bus", "Bicycle", "Train") and a "color" that accepts any string value.

Datasets are used to split data into a "subfolders" to make data management easier. For example, you can then define a [Labeling Job](/labeling/jobs.md) to label all Vehicles in Zurich.

{% hint style="info" %}
This is just an example, experiment! Maybe you would like to have projects like "Data from Data from 14 august" or "From Mike" or even "To train v2 (final) (2)" 😃
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.supervisely.com/data-organization/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.