> For the complete documentation index, see [llms.txt](https://resources.unizin.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://resources.unizin.org/products/data-and-analytics/unizin-data-platform/data-stores/data-lake.md).

# Data lake

<figure><img src="/files/dZVrn2ZTsnqS8sQfuQD2" alt=""><figcaption></figcaption></figure>

The Unizin Data Platform's [event data pipeline](/products/data-and-analytics/unizin-data-platform/system-overview/event-data-pipeline.md) and [context data pipeline](/products/data-and-analytics/unizin-data-platform/system-overview/context-data-pipeline.md) maintain a data lake that serves as a foundational store for ad hoc inquiry.

The purpose of the UDP Data lake is to act as a comprehensive store for all data imported by a UDP instance for all time. The data lake is composed of two major components:

1. The UDP Context store, which hosts all context data in a single, relational database
2. The UDP Event store, which hosts all event data in a single table

In this section, we cover the design of the UDP data lake and, for Unizin consortium members, document how they can access each in their SaaS implementation.


---

# 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://resources.unizin.org/products/data-and-analytics/unizin-data-platform/data-stores/data-lake.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.