> 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.58-expanded-events-table.md).

# 2.0.58

## Expanded events table

| Version      | 2.0.58            |
| ------------ | ----------------- |
| Release Date | February 26, 2021 |

## Key Features

The "expanded" event store table increases convenience, performance, and cost-effectiveness of large-scale behavioral queries.

## Details <a href="#id-2.0.58expandedeventstable-details" id="id-2.0.58expandedeventstable-details"></a>

All UDP instances now contain a new table in the [UDP Event store](/products/data-and-analytics/unizin-data-platform/data-stores/data-lake/udp-event-store.md), called "expanded," that aggressively expands its representation of a Caliper event in tabular form.\
\
The new "expanded" table lives alongside the "events" table in the "event\_store" dataset of each UDP instance. The "expanded" table explodes the contents of Caliper events –including the JSON blob and JSON nodes– into separate columns of a single Caliper event record.

Additional features of the new "expanded" table include:

* A more complete representation of a Caliper event's identifiers for Person and Course offering using the [STRUCT data type](https://cloud.google.com/bigquery/docs/reference/standard-sql/data-types#struct_type). The "expanded" tables will make it easier to use the given identifiers in an Event and the learning tool identifiers that are parsed from an event's IRIs or retrieved from the [enrichment process](/products/data-and-analytics/unizin-data-platform/system-overview/event-data-pipeline/udp-event-enricher.md).
* The date and time (e.g., "16:00") components of the event's timestamp are now separated into distinct columns.
* Canvas events now have a consistent, singular "ed\_app" value, making it easier to identify Canvas events.

Please visit our [docs site for full documentation on the new "expanded" table](/products/data-and-analytics/unizin-data-platform/data-stores/data-lake/udp-event-store/expanded-table.md), where you can also find information about how to [access your institution's UDP event store](/products/data-and-analytics/unizin-data-platform/data-stores/data-lake/udp-event-store/accessing-the-event-store.md).\
\
We also provide a [brief migration guide to move from using the events table to the expanded table](https://gitlab.com/unizin/products-docs-site/-/blob/master/docs/products/data-and-analytics/unizin-data-platform/release-notes/broken-reference/README.md).

## Known Issues <a href="#id-2.0.58expandedeventstable-knownissues" id="id-2.0.58expandedeventstable-knownissues"></a>

The data in the "expanded" table begins on 2/26/2021. In a forthcoming release, Unizin will backfill behavioral data from each institution's "events" table into its "expanded" table.


---

# 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.58-expanded-events-table.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.