# Metadata

Per each entry collected, Epicollect5 add some metadata automatically.

| name                     | description                                                                                                                                                                         |
| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| ec5\_uuid                | The unique identifier of the row of data.                                                                                                                                           |
| ec5\_parent\_uuid        | For child forms only, the unique identifier of the parent row of data.                                                                                                              |
| ec5\_branch\_owner\_uuid | For branch forms only, the unique identifier of the form entry that owns the branch row of data.                                                                                    |
| ec5\_branch\_ref         | The name of the column in your main form that lists how many branches you have for each entry.                                                                                      |
| updated\_at              | UTC timestamp when the entry is uploaded to the server. Subsequent uploads, due to editing for example, will update this value.                                                     |
| created\_at              | UTC timestamp when the entry was created.                                                                                                                                           |
| created\_by              | **Private projects only**, the email of the user who created the entry (if available, if a project was initially set as public, those public entries will not have any user linked. |

## Location questions

Each location question is split into six parts, with the prefixes:

* **lat\_** (latitude)
* **long\_** (longitude)
* **accuracy\_** (accuracy)
* **UTM\_Northing\_** (UTM Northing)
* **UTM\_Easting\_** (UTM Easting)
* **UTM\_zone\_** (UTM Zone)

{% hint style="success" %}
The location data are provided in both [**decimal degrees**](https://en.wikipedia.org/wiki/Decimal_degrees) (to 6 decimal places precision) and [**UTM**](https://en.wikipedia.org/wiki/Universal_Transverse_Mercator_coordinate_system) format.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.epicollect.net/web-application/metadata.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.