> For the complete documentation index, see [llms.txt](https://documentation.dnanexus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.dnanexus.com/faqs/importing-data.md).

# Importing Data

## How do I upload my data files?

### Through the web UI

From the **home screen**, click on any project to which you have **UPLOAD**, **CONTRIBUTE**, or **ADMINISTER** access, then click **Add Data**. Follow the instructions in the Add Data dialog.

### Through the command line

Download and run the [Upload Agent](/user/objects/uploading-and-downloading-files/batch/upload-agent.md) to upload your files. For example, the following command uploads a set of paired-end FASTQ files:

```shell
ua sample_1_left.fastq.gz sample_1_right.fastq.gz
```

## How do I upload data from my MiSeq instrument into DNAnexus?

Your MiSeq instrument produces run results in the folder `D:\Illumina\MiSeqOutput` or on a network path that you specify. After on-instrument secondary analysis is complete, the reads are available in `*.fastq.gz` files in the subfolder `/Data/Intensities/BaseCalls/` of the run folder. For example, the first file may be called `D:\Illumina\MiSeqOutput\Run1\Data\Intensities\BaseCalls\sample1_L001_R1_001.fastq.gz`.

To upload these files into DNAnexus, follow the instructions in [How do I upload my data files?](#how-do-i-upload-my-data-files).

## How do I import reads from the Sequence Read Archive (SRA)?

Visit the [European Nucleotide Archive (ENA)](https://www.ebi.ac.uk/ena/browser/) and find your SRA dataset (sequencing run) of choice. For example, if you search for "SRR001662", you reach the [result page for sequencing run SRR001662](https://www.ebi.ac.uk/ena/browser/view/SRR001662). On that page, the "Read Files" panel contains FTP links to FASTQ files (under the "FASTQ files (ftp)" column). To import these reads, in your project click "Add Data", choose "Transfer from another server" and supply these links.

## How do I import a track from the UCSC Genome Browser?

If the track has an associated BED, GTF, or WIG file, use the link to that file as input to the [URL Fetcher app](https://platform.dnanexus.com/app/url_fetcher). This app launches a job that downloads the file and uploads it to your DNAnexus project.

For example, the default UCSC Genome Browser view for hg19 includes a track called "Digital DNaseI Hypersensitivity Clusters from ENCODE". If you click on the gray rectangle to the left of the track to configure it, you find a "downloads" link that leads you to a gzipped BED file with the track data. The link to that file can be given as the input to the [URL Fetcher app](https://platform.dnanexus.com/app/url_fetcher).

Not all UCSC Genome Browser tracks include links to downloadable data. However, you can still export most tracks into BED using the UCSC "Table Browser". Select "Table Browser" from the "Tools" menu at the top, and choose the track of interest. In the "output format" select BED, and type in a filename. Click the "Get Output" button to download a BED file.


---

# 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 dynamically by asking a question.

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

```
GET https://documentation.dnanexus.com/faqs/importing-data.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.