> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/partek/partek-flow/tutorials/bulk-rna-seq/adding-sample-attributes.md).

# Adding sample attributes

Attributes describe samples. Examples of sample attributes include treatment group, age, sex, and time point. Attributes can be added individually in the Metadata tab or in bulk [using a text file](/partek/partek-flow/quick-start-guide.md#the-metadata-tab). In this tutorial, we will add one attribute, 5-AZA Dose, manually.

* Click the **Metadata** tab
* Click **Manage** under Sample attributes (Figure 1)

<figure><img src="https://1384254481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJVEESmJAPppJ3ijFq5aR%2Fuploads%2Fgit-blob-6eea25ffc4ccbad6891ecb0770eb407a1afbafc1%2Fmanage%20sample%20attr.png?alt=media" alt=""><figcaption><p><em>Figure 1. Adding sample attributes manually</em></p></figcaption></figure>

* Click **Add new attribute** (Figure 2)

<figure><img src="https://1384254481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJVEESmJAPppJ3ijFq5aR%2Fuploads%2Fgit-blob-56d847b66fd46588c91b86336deecfa0882cc1ba%2Fadd%20new%20attr.png?alt=media" alt=""><figcaption><p><em>Figure 2. Adding a new attribute</em></p></figcaption></figure>

* To configure a new attribute, at Name, type in **5-AZA Dose** as the name of the attribute
* Click **Add** to add 5-AZA Dose as a categorical, project-specific attribute (Figure 3)

<figure><img src="https://1384254481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJVEESmJAPppJ3ijFq5aR%2Fuploads%2Fgit-blob-b80f688c7081900cdb055325d2165a0210c0defe%2Fadd%20new%20attr%20dialog.png?alt=media" alt=""><figcaption><p><em>Figure 3. Configuring a new attribute</em></p></figcaption></figure>

* Name the first New category **0uM**
* Click the plus icon to add category (Figure 4)
* Repeat for two additional categories, **5uM** and **10uM** (Figure 5)

<figure><img src="https://1384254481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJVEESmJAPppJ3ijFq5aR%2Fuploads%2Fgit-blob-466224167431aeb0feba8a094c41eee277fece51%2Fadd%20attribute%20category.png?alt=media" alt=""><figcaption><p><em>Figure 4. Creating attribute category</em></p></figcaption></figure>

<figure><img src="https://1384254481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJVEESmJAPppJ3ijFq5aR%2Fuploads%2Fgit-blob-3c8589c14b14074e2d138857262c940f62b86d68%2F5aza%20three%20category.png?alt=media" alt=""><figcaption><p><em>Figure 5. All category attributes for 5-AZA Dose</em></p></figcaption></figure>

* Click **Back to metadata tab**

The data table now includes an Attribute column for 5-AZA Dose (Figure 6). Next, we need to assign samples attribute categories for 5-AZA Dose.

<figure><img src="https://1384254481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJVEESmJAPppJ3ijFq5aR%2Fuploads%2Fgit-blob-0013e63ed786c974c7662276f17f5e7e5f1b210a%2Fattribute%20added%20to%20sample%20table.png?alt=media" alt=""><figcaption><p><em>Figure 6. Data table updated with column for 5-AZA Dose</em></p></figcaption></figure>

* Select Assign values

The option to edit the 5-AZA Dose field for each sample will appear as a drop-down menu (Figure 7).

<figure><img src="https://1384254481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJVEESmJAPppJ3ijFq5aR%2Fuploads%2Fgit-blob-c46398aba6902de29a7cd7ae9eef91d24386577e%2Fassign%20value%20drop-down.png?alt=media" alt=""><figcaption><p><em>Figure 7. Dropdown menu to select treatment for each sample</em></p></figcaption></figure>

* Select the 5-AZA Dose text box for a sample to bring up a drop-down menu with the 5-AZA Dose attribute categories (0uM, 5uM, 10uM)
* Use the drop-down menus to add a treatment group for each sample

The first three samples (SRR592573-5) should be **0uM**, the next three samples (SRR592576-8) should be **5uM**, and the final three samples (SRR592579-81) should be 10uM (Figure 8).

* Click **Apply changes**

<figure><img src="https://1384254481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJVEESmJAPppJ3ijFq5aR%2Fuploads%2Fgit-blob-bcfa57ac98c591f74b7db842e722797a59e8d8b4%2Fassign%20value%20for%20all%20samples.png?alt=media" alt=""><figcaption><p><em>Figure 8. Add 5-AZA dose to each sample as shown</em></p></figcaption></figure>

The data table will now show each a 5-AZA Dose attribute for each sample.

## Additional Assistance

If you need additional assistance, please visit [our support page](http://www.partek.com/support) to submit a help ticket or find phone numbers for regional support.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.bioinsight.illumina.com/partek/partek-flow/tutorials/bulk-rna-seq/adding-sample-attributes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
