> For the complete documentation index, see [llms.txt](https://docs.perigee.software/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perigee.software/transforms/utilities/file-identification.md).

# File Identification

Transforms is able to identify and auto-map files when no map is present. This uses recursive subset algorithm to determine the file type based on it's name and columns (it's thousands of iterative calculated passes to do this!)

While impressive and useful it cannot always be accurate. Here's a few ways you can increase the auto detection of files if you regular are creating new maps from known map types.

* Use the "[TransformGroup](/transforms/the-mapping-document.md#transformgroup)" and then an underscore as the first part of the file name.
  * Example: <mark style="color:purple;">**FinJournals\_**</mark>**file002.csv**
* Use the "[DataObjectID](/transforms/the-mapping-document.md#dataobjectid)" and then an unscore as the first part of the file name.
  * Example: <mark style="color:purple;">**43\_**</mark>**file002.csv**
* Change the input columns to more closely match the mapping files target names.&#x20;
  * While not always possible, or even required, if this is ever an option from a generated system, definitely speeds up the process of identifying, and mapping a new 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://docs.perigee.software/transforms/utilities/file-identification.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.