Master Data Templates

Configure master data templates for MuktaSoft

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.

Sr. No	Checklist Parameter	Example
1	Make sure that each and every point in this reference list has been taken care of	Checklist

Entity Specific Checklist

This checklist covers the activities which are specific to the entity.

Sr. No.	Activity	Example
1	The Code should be alphanumeric and unique	DR
2	The Name should not contain any special characters