> 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/release-notes/2.0.110-report-schema.md).

# 2.0.110

## Report schema

| Version      | 2.0.110      |
| ------------ | ------------ |
| Release Date | July 1, 2022 |

## Key Features

The UDP now supports a new `report` schema in the context store for metadata tables.

## Details <a href="#id-2.0.110reportschema-details" id="id-2.0.110reportschema-details"></a>

Unizin released a new `report` schema for the UDP context store. This schema provides the most recent run dates for keymap and entity tables. The creation of this table is intended to help spur the effort of additional forthcoming releases intended to allow institutions to migrate from a MyLA dependency that currently requires the UDW. In future releases, Unizin plans to add a timestamp value to the run dates, and additional fields related to the reporting metadata tables affiliated with MyLA.

Additional documentation on the `report` schema can be found on our [Resources Site](/products/data-and-analytics/unizin-data-platform/data-stores/data-lake/udp-context-store.md).

## Known Issues

None.


---

# 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/release-notes/2.0.110-report-schema.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.