> For the complete documentation index, see [llms.txt](https://docs.plumvoice.com/insight/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plumvoice.com/insight/metadata-manager/formatting-metadatabase-csv.md).
# Formatting Metadatabase CSV
CSV files uploaded to Insight for use as a metadatabase must be properly formatted.
The first row of the CSV file must **only** contain the column names. If actual data is in the first row, Insight will recognize that data as the column names. An example header is:\
“userID”,“FirstName”,“LastName”
Every row afterwards should contain the actual data. To match the above header, we could have the following sample rows:
```
“1”,“Jerry”,“Garcia”
“2”,“Harry”,“Nilsson”
“3”,“David”,“Bowie”
“4”,“Paul”,“Simon”
“5”,“George”,“Harrison”
```
Compiled together the complete CSV file looks like:
```
“userID”,“FirstName”,“LastName”
“1”,“Jerry”,“Garcia”
“2”,“Harry”,“Nilsson”
“3”,“David”,“Bowie”
“4”,“Paul”,“Simon”
“5”,“George”,“Harrison”
```
If you have difficulty formatting a metadatabase, one workaround is to create a new, empty metadatabase in Insight. Then, populate a single row with data. This does not need to be any specific data as this is simply for formatting purposes. Next, download the CSV using the “Download CSV” button. Open the CSV file and modify it as necessary.
To convert a pre-existing .XLX or .XLSX to a CSV, be sure to select “save as” when saving the file and changing the file type to CSV.
---
# 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.plumvoice.com/insight/metadata-manager/formatting-metadatabase-csv.md?ask=&goal=
```
`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.