> 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/works/reference-implementations/muktasoft-v2.2/deployment/configuration/master-data-templates.md).

# Master Data Templates

## Objective

This section is designed with the objective of helping implementation parties and end-users collect the required master data through minimal interaction and iterations and ensure the quality, consistency and shape of data needed to configure the system.

## Audience

This page is intended to help stakeholders as given below on data gathering activities.

1. State Team
2. eGov Onsite Team/ Implementation Team
3. ULB Team (Nodal and DEO)
4. Implementation Partners

## Output Artefacts

The artefacts of this document are the data template of a configurable entity, a page with content defining the entity template and helping on how to fill the template with required data.

## Data Entry

1. Download the data template attached to this page.
2. Find the meaning of the different headers in the Data Definition section on this page
3. Make sure all the headers, data type, field size and definition/ description are clear. In case of any doubt, please reach out to the person who has shared this document with you to discuss the same and clear out the doubts.
4. Identify the different types of user roles on the basis of ULB functions.
5. Start filling the data starting from serial no. and complete a record at once. Repeat this exercise until the entire data is filled into a template.
6. Verify the data once again by going through the checklist and taking care of each and every point mentioned in the checklist.

### Checklist

The checklist is a set of activities to be performed once the data is filled into a template to ensure data type, size, and format of data is as per the expectation. These activities have been divided into 2 groups as given below.

#### Common Checklist

This checklist covers all the activities which are common across the entities.

<table><thead><tr><th width="103.33333333333331">Sr. No</th><th>Checklist Parameter</th><th>Example</th></tr></thead><tbody><tr><td>1</td><td>Make sure that each and every point in this reference list has been taken care of</td><td><a href="https://urban.digit.org/platform/configure-digit/configuring-master-data-templates/module-setup/common-config/checklist">Checklist</a></td></tr></tbody></table>

#### Entity Specific Checklist

This checklist covers the activities specific to the entity.

<table><thead><tr><th width="115.33333333333331">Sr. No.</th><th width="238">Activity</th><th>Example</th></tr></thead><tbody><tr><td>1</td><td>The Code should be alphanumeric and unique</td><td>DR</td></tr><tr><td>2</td><td>The Name should not contain any special characters</td><td></td></tr></tbody></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://docs.digit.org/works/reference-implementations/muktasoft-v2.2/deployment/configuration/master-data-templates.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.