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

# Data

In iMaps data refers to a file of some sort (or, occasionally, a folder). These can be reads files, FASTA files, log files - literally anything.

There are two ways to create data in iMaps:

1. You can upload data from your computer using the upload page. Some data has special labels associated with it, such as labels indicating that a file represents multiplexed reads, or is an annotation spreadsheet. The particular upload portal you use will handle this for you.
2. You can run a pipeline and generate data outputs.

Any data you generate is owned by you (whether by uploading it or by running the pipeline that generates it), with one crucial exception. If you run a pipeline which demultiplexes a multiplexed reads file into multiple demultiplexed reads files, each of those individual reads files (and data downstream of them) may have a different owner, specified in an associated annotation sheet.


---

# 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://docs.imaps.goodwright.com/fundamentals/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.