# Project Structure

All Panomics projects share a common structure that makes collaborative analysis straightforward.

### Project Metadata

The project metadata can be split into 2 categories, each serving a specific purpose.

#### Direct Metadata

This helps team members understand what the project is all about. It includes:

* title
* external ID (e.g.: GEO identifier)
* description
* overall design
* tags

#### Inherited Metadata

This is the metadata inherited from the samples associated with the project. It can include information about the tissue, disease, treatment compounds, etc. Projects can be filtered using any of the [metadata fields](/documentation/administration/metadata-fields.md) configured at the organization level.

### Analyses

This is where all project analyses reside. From this section, users can:

* list and filter all project analyses
* mark analyses as done
* publish or unpublish analyses
* view audit trail
* export analyses as cell atlases (applicable only to single cell analyses)
* delete analyses

<figure><img src="/files/AI1LvmT7sTKgl5EpugkM" alt=""><figcaption><p>Analysis list</p></figcaption></figure>

For more details, visit the [dedicated pages](#analyses).

### Samples

This is where all project samples reside.

{% hint style="info" %}
Samples can be associated with more than one project.
{% endhint %}

From this section, users can:

* list and filter all project samples
* import new samples
* remove samples from the project
* upload/edit metadata
* change the samples' status (see [sample lifecycle](/documentation/samples/sample-lifecycle.md))
* create new analyses

<figure><img src="/files/k4AEekd0t0OzgrWxf8rH" alt=""><figcaption><p>Sample list</p></figcaption></figure>

For more details, visit the [dedicated pages](#samples).

### Assets

The **Assets** page functions as a versatile file explorer within Panomics. It allows users to manage project files by creating folders, uploading, downloading, and moving files.&#x20;

For compute results, it offers a read-only view, with the option to copy analysis results to the JupyterLab or RStudio mounts.&#x20;

The JupyterLab and RStudio mounts connect directly to the runtime’s shared drive, providing a secure way to transfer files to or from the project.

{% embed url="<https://www.loom.com/share/e4243444c9d14472aac8b14096e77881>" %}

### Readme

The readme is a collaborative document used to describe the analytical decisions made, write down hypothesis, or ask for feedback.

{% embed url="<https://www.loom.com/share/ec0e8ec4cf0a49e2af20b79f01d6a915?sid=7312e304-95e9-4e03-b27a-c35562f5f3b3>" %}


---

# 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://documentation.panomics.bio/documentation/projects/project-structure.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.
