> 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/analyzing-cite-seq-data/importing-feature-barcoding-data.md).

# Importing Feature Barcoding Data

* [Create a new Project](#create-a-new-project)
* [Import data](#import-data)

## Create a new Project

Let's start by creating a new project.

* On the *Home page*, click **New project** (Figure 1)
* Give the project a name
* Click **Create project**

![Figure 1. Create a new project and give it a meaningful name (e.g. CITE-Seq tutorial)](https://1384254481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJVEESmJAPppJ3ijFq5aR%2Fuploads%2Fgit-blob-e562f8d1f4f32bee5517fa5d2b105836254f8fd3%2Fcreate-a-new-project-cite-seq-tutorial.png?alt=media)

## Import data

* In the Analyses tab, click **Add data**
* Click **10x Genomics Cell Ranger counts h5** (Figure 2)
* Choose the filtered HDF5 file for the MALT sample produced by Cell Ranger

![Figure 2. Import options for CITE-Seq tutorial data](https://1384254481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJVEESmJAPppJ3ijFq5aR%2Fuploads%2Fgit-blob-982df94d0df9077dcf1967505331bc6135ce46d0%2Fimport-options-for-cite-seq-tutorial.png?alt=media)

Move the .h5 file to where Partek Flow is installed using ![](https://1384254481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJVEESmJAPppJ3ijFq5aR%2Fuploads%2Fgit-blob-24b65d67d7ed3d406b8154aeb2520bfd999562ca%2Ftransfer-files-green.png?alt=media), then browse to its location.

![Figure 3. Import options for CITE-Seq tutorial data](https://1384254481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJVEESmJAPppJ3ijFq5aR%2Fuploads%2Fgit-blob-7ed5e79a96081f3c01a6d4c93708fde76b53b357%2Fimport-options-for-cite-seq-tutorial-2.png?alt=media)

Note that Partek Flow also supports the feature-barcode matrix output (barcodes.tsv, features.tsv, matrix.mtx) from Cell Ranger. The import steps for a feature-barcode matrix are identical to this tutorial.

* Click **Next**
* Name the sample **MALT** (the default is the file name)
* Specify the annotation used for the gene expression data (here, we choose **Homo sapiens (human) - hg38** and **Ensembl Transcripts release 109**). If Ensembl 109 is not available from the drop-down list, choose **Add annotation** and download it.
* Check **Features with non-zero values across all samples** in the *Report* section
* Click **Finish** (Figure 3)

![Figure 4. File format options for MALT data set](https://1384254481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJVEESmJAPppJ3ijFq5aR%2Fuploads%2Fgit-blob-d559d4d915012ba4a1023473cb61444630efc33c%2Ffile-formats-options-for-malt-data-set.png?alt=media)

A *Single cell counts* data node will be created under the *Analyses* tab after the file has been imported. We can move on to processing the data.

## 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/analyzing-cite-seq-data/importing-feature-barcoding-data.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.