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

# Importing your data

The first stage in the process, importing your data is the most critical and key area when using EasyCatalog

By directly importing your data into InDesign, you eliminate re-keying errors and significantly reduce the amount of time required to produce your publication.

{% hint style="danger" %}
The quality of your source data has a direct impact on the quality of the results that can be achieved using EasyCatalog.
{% endhint %}

Once your data has been imported, it is shown in a spreadsheet-style panel that sits alongside your other InDesign panels. Multiple EasyCatalog panels can be open at any time, allowing you to work on publications that use data from multiple sources.


---

# 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://easycatalog.nousmedis.com/setting-up-your-data/2.-importing-your-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.