# Loading schemas

A UDP Loading schema represents a subset of the UCDM ontology that defines a context dataset that can be expected from a class of tools.

The purpose of a UDP Loading schema is to define a standard interface for context data to be imported into the UDP. If a learning tool or system produces a dataset that conforms with a UDP loading schema, its data can be imported into a UDP instance.

Unizin maintains a [catalog of UDP loading schemas](https://docs.udp.unizin.org/) that are used for different kinds of learning tools as well as the [Student Information System (SIS)](https://docs.udp.unizin.org/context-data/html/sis-2.0.html).

Unizin maintains a catalog of UDP Loading schemas in order to serve different kinds of learning tools. For example, some learning tools are designed to facilitate class discussions while others deliver video-based learning experiences. For each type of learning tool, it is valuable to make distinct loading schemas, since the types of context data available from each of these learning tools will differ. Rather than define a single data interface applicable to all learning tools, the UDP defines distinct data interfaces for classes of tools.

[Visit our full UCDM and UDP Loading schema documentation](https://docs.udp.unizin.org/index.html).

<figure><img src="https://3709019308-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKYwtHNGgdPXS3PWAlZUr%2Fuploads%2Fgit-blob-74721a649728f4eda85d7b61925a255410b061ec%2FComplete%20ERD%20-%20Loading%20schemas%20(4).png?alt=media&#x26;token=39693acf-c171-45ca-a4df-ac65906947fb" alt=""><figcaption></figcaption></figure>


---

# 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://resources.unizin.org/products/data-and-analytics/unizin-data-platform/key-concepts/loading-schemas.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.