Data Management

The Data Management step includes two substeps: Population Upload and Facility Upload, enabling users to upload essential data for the microplan.

---

Population Upload

Description: This substep allows users to upload population data for the campaign.

• Download Template: Download the template for population data.

• Boundary Dependency: The boundaries appearing in the population template are dependent on the boundaries selected in the previous Boundary Selection screen. Tabs in the template will correspond to the districts selected in that screen.

• File Upload: Drag and drop or browse to upload the filled Excel file.

Guidelines:

• Mandatory Fields: The Total Population and Target Population columns are mandatory and must be provided as whole numbers.

• Latitude & Longitude: These fields must be in Degree Decimal or Degree Minute Seconds format.

---

Facility Upload

Description: This substep allows users to upload facility or point-of-service information.

• Download Template: Download the template for facility data.

• Boundary Codes: The facility template will include boundary codes for the villages selected in the previous Boundary Selection screen in a single Boundary Code sheet.

• File Upload: Drag and drop or browse to upload the filled Excel file.

Guidelines:

• All fields are mandatory except for Latitude and Longitude.

• Latitude & Longitude must be in Degree Decimal or Degree Minute Seconds format.

---

Error Handling

Validation Process: After the file is uploaded, the system will validate the data. If any errors are found, the system will populate an Error column in the sheet, showing the errors next to the corresponding rows.

Error Preview: Clicking the View Error button will show a preview of the uploaded Excel file, highlighting the errors in the Error column next to the corresponding row.

Re-upload Process: Once the errors are corrected, users can download the validated file, make the necessary changes, and re-upload the file.

Proceeding with Valid Data: Processing will only proceed if a valid sheet with no errors is uploaded. If the sheet is valid, the system will continue to the next step.

---

Boundary Selection Screen Navigation Warning:

• Warning: If the user navigates back to the Boundary Selection screen, the current uploaded templates for Population and Facility will be discarded. A warning message will appear on the UI to inform the user before they proceed.

---

Generation and Validation from MDMS Schema

Both the generation and validation of facility and boundary data are based on a schema provided by MDMS.

• Generation: From this schema, fields are converted into columns in the respective upload templates.

• Validation: Validation is performed based on the schema, ensuring that the data adheres to the defined structure.

• Additionally, custom validations are applied to ensure data integrity.

---

Localization & User Interface

• Localization: All labels, instructions, and error messages are translatable into multiple languages.

• File Upload: The interface supports drag-and-drop or browse-to-upload file options.

• Validation: Validation ensures all required fields are completed and data is properly formatted. Processing will proceed only if a valid sheet with no errors is uploaded.

Here is the updated table with the adjustments:

Endpoint	Method	Payload
/project-factory/v1/project-type/search	POST	{ "tenantId": "mz", "ids": [ "2a2491a7" ], "pagination": {}, "RequestInfo": {} }
/plan-service/config/_search	POST	{ "PlanConfigurationSearchCriteria": { "tenantId": "mz", "id": "660fb389-5e60-4c43-b6ce-b1c109b23f54" } ,"RequestInfo": {} }
/project-factory/v1/data/_create	POST	{ "ResourceDetails": { "type": "boundaryWithTarget", "hierarchyType": "MICROPLAN", "tenantId": "mz", "fileStoreId": "29e31558-24ce-4efb-8102-cfa92961efdd", "action": "validate", "campaignId": "8c413d61-c411-4c33-b6eb-76ea005a84c9", "additionalDetails": { "source": "microplan" } }, "RequestInfo": {} }
/project-factory/v1/data/_search	POST	{ "SearchCriteria": { "id": ["08bb247d-364a-4b44-b0a9-d8efeee5a6a4"], "tenantId": "mz", "type": "boundaryWithTarget" }, "RequestInfo": {} }
/project-factory/v1/project-type/update	POST	{ "CampaignDetails":{"id":"8c413d61-c411-4c33-b6eb-76ea005a84c9","tenantId":"mz","status":"drafted","action":"draft","campaignNumber":"CMP-2024-12-03-006616","isActive":true,"parentId":null,"campaignName":"Malaria-Bednet Campaign-Fixed Popp0099","projectType":"LLIN-mz","hierarchyType":"MICROPLAN","boundaryCode":"MICROPLAN_MO","projectId":null,"startDate":1735810905674,"endDate":0,"additionalDetails":{"source":"microplan","disease":"MALARIA","resourceDistributionStrategy":"MIXED"},"resources":[],"boundaries":[],"deliveryRules":[],"auditDetails":{"createdBy":"f4f36858-0e9e-4150-a37f-444b90995e7c","lastModifiedBy":"f4f36858-0e9e-4150-a37f-444b90995e7c","createdTime":1733218905816,"lastModifiedTime":1733218919304}},"RequestInfo":{}}
/plan-service/config/_update	POST	`{"PlanConfiguration":{"id":"660fb389-5e60-4c43-b6ce-b1c109b23f54","tenantId":"mz","name":"Malaria-Bednet Campaign-Fixed Popp0099","campaignId":"8c413d61-c411-4c33-b6eb-76ea005a84c9","status":"DRAFT","files":[],"assumptions":[],"operations":[],"resourceMapping":[],"auditDetails":{"createdBy":"f4f36858-0e9e-4150-a37f-444b90995e7c","lastModifiedBy":"f4f36858-0e9e-4150-a37f-444b90995e7c","createdTime":1733218906001,"lastModifiedTime":1733218924572},"additionalDetails":{"key":"2"},"workflow":null},"RequestInfo": {} }