> For the complete documentation index, see [llms.txt](https://uci.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://uci.sunbird.org/use/developer/uci-basics/schema-overview/uci-core-schema/assessment-db-schema.md).

# Assessment DB Schema

UCI uses postgreSQL for storing data of conversations. ODK transformer uses this database to store its assessment data for each question & answer.

## Schema

Assessment data consists of 4 tables, which are listed below.

### Question

This table keeps the details of question asked to user. 

| Field          | Type         | Description                     |
| -------------- | ------------ | ------------------------------- |
| id             | uuid         |                                 |
| form\_id       | varchar(100) | odk form id                     |
| form\_version  | varchar(10)  | odk form version                |
| x\_path        | varchar(500) | odk question xpath              |
| question\_type | varchar(500) |                                 |
| meta           | jsonb        | extra meta data in form of json |
| created        | timestamp    |                                 |
| updated        | timestamp    |                                 |

### Assessment

This table keeps the details of answer submitted by user for a specific question.

| Field      | Type      | Description                       |
| ---------- | --------- | --------------------------------- |
| id         | uuid      |                                   |
| question   | uuid      | id of table question              |
| answer     | text      | answer given by user for question |
| bot\_id    | uuid      | bot id                            |
| user\_id   | uuid      | fusion auth returned user id      |
| device\_id | uuid      | fusion auth returned user id      |
| meta       | jsondb    | extra meta data in form of json   |
| created    | timestamp |                                   |
| updated    | timestamp |                                   |

### Xmessage

This table keeps the records of messages sent to user against his/her phone number.

| Field             | Type          | Description          |
| ----------------- | ------------- | -------------------- |
| id                | bigint        |                      |
| phone\_no         | varchar(15)   | phone number of user |
| updated\_at       | timestamp     |                      |
| message           | varchar(1000) | message sent to user |
| is\_last\_message | boolean       |                      |

### XMessage State

This table keeps the odk instance xml state against the user phone number and form name. 

| Field           | Type         | Description               |
| --------------- | ------------ | ------------------------- |
| id              | bigint       |                           |
| phone\_no       | varchar(15)  | phone number of user      |
| state           | text         | current xml state of form |
| previous\_path  | varchar(100) | previous question xpath   |
| bot\_form\_name | varchar(50)  | odk form name             |
| updated\_at     | timestamp    |                           |


---

# 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://uci.sunbird.org/use/developer/uci-basics/schema-overview/uci-core-schema/assessment-db-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.