> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/platform/build/core-services/mdms-v2-master-data-management-service/adopt-new-mdms-steps.md).

# Adopt New MDMS - Steps

Follow the steps below to adopt the new MDMS -

1. Define the schema for the master that you want to promote to MDMS v2.
2. Ensure that the schema has a unique field (a unique field can also be composite) to enforce data integrity.
3. In case the data does not have unique identifiers e.g. complex masters like the one [mentioned here](https://github.com/egovernments/health-campaign-mdms/blob/QA/data/default/health/project-task-configuration.json), consider adding a redundant field which can serve as the unique identifier.
4. Use the following API endpoint to create a schema - */mdms-v2/schema/v1/\_create*
5. Search and verify the created schema using the following API endpoint - */mdms-v2/schema/v1/\_search*
6. Once the schema is in place, add the data using the following API endpoint - */mdms-v2/v2/\_create/{schemaCode}*
7. Verify the data by using the following API endpoint - */mdms-v2/v2/\_search*


---

# 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://docs.digit.org/platform/build/core-services/mdms-v2-master-data-management-service/adopt-new-mdms-steps.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.
