> For the complete documentation index, see [llms.txt](https://ed.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ed.sunbird.org/older-versions/contribute/source-code/workflows/manage-learn/ml-core-service/data-model.md).

# Data Model

### DB Schema

The schema serves as a blueprint for creating and maintaining the database that supports the ML Core Services data storage and retrieval operations.

![ML-Core Service](https://ml-services-uploads.s3.ap-south-1.amazonaws.com/DBSchema/ML-Core.png)

#### Here are examples of sample data for each collection

#### [program](https://github.com/shikshalokam/ml-core-service/blob/master/DBSchema/programs.json)

Programs collection is tasked with housing high-level program information, encompassing program specifics, resource listings, and program categorizations.

#### [programUser](https://github.com/shikshalokam/ml-core-service/blob/master/DBSchema/programUsers.json)

The programUsers Collection holds user data of those who have become part of the program and have provided their consent status.

#### [certificateBaseTemplates](https://github.com/shikshalokam/ml-core-service/blob/master/DBSchema/certificateBaseTemplates.json)

The certificateBaseTemplates collection is utilized to store URLs and file paths indicating the storage location of certificate files, along with their corresponding certificate types.

#### [certificateTemplates](https://github.com/shikshalokam/ml-core-service/blob/master/DBSchema/certificateTemplates.json)

The certificateTemplates collection will be established for solutions and associated with certificate templates to facilitate the generation of certificates, incorporating predefined criteria.

#### [solutions](https://github.com/shikshalokam/ml-core-service/blob/master/DBSchema/solutions.json)

The solutions collection will serve as a repository for various types of resources, encompassing observations, improvement projects, and surveys, among others.

#### [userExtension](https://github.com/shikshalokam/ml-core-service/blob/master/DBSchema/userExtension.json)

The userExtension collection will be responsible for storing user information, including associated solutionsId and programId, indicating their roles as program managers or designers.

[Click here](https://ml-services-uploads.s3.ap-south-1.amazonaws.com/DBSchema/ML-Core.pdf) for DB schema and corresponding examples in a PDF format.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://ed.sunbird.org/older-versions/contribute/source-code/workflows/manage-learn/ml-core-service/data-model.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
