| Target release | Release name or number |
|---|---|
| Epic | Configuration |
| Document status | |
| Priority | |
| eLMIS Status | Implemented |
| OpenLMIS Status | Partially Implemented |
| PATH | - |
| OpenLMIS | Mary Jo Kochendorfer (Deactivated) |
| JSI | Ashraf Islam (Unlicensed) |
|
Ability to upload district boundaries in GeoJSON format
Status in eLMIS: Implemented.
Status in OpenLMIS: Partially implemented (in the backend), need front end and potentially addition small features
Priority: High priority for Tanzania, Zanzibar, Zambia
Dashboard, reporting rate and other reports and dashlets needs to visualize indicators data as overlays on map for that country
Version 3 has the ability to upload single geographic polygons (and nested polygons). Need for discussion around if there is a need for
| # | Title | User Story | Label | Importance | Notes | JIRA Tickets |
|---|---|---|---|---|---|---|
| 1 | Map | As an administrator I want to be able to upload district boundaries encoded in GeoJSON format and use the map on reports and dashboards indicators color coding different regions with different status and on click display additional logistics data as popup dialog | Map | Must have | See Figure 1 | |
| 2 | Geographic zone uploads | As an administrator I want to be able to associate districts from eLMIS with specific boundaries coming from GeoJSON | Map | Must have | See Figure 2 | |
Include any business process mapping, mockups, diagrams or visual designs relating to these requirements. Describes the tasks and the personas who perform those activities. The diagram provides the context for the user stories and serves as a focal point for achieving clarity and agreement among stakeholders. Looks like a standard flow chart.
Figure 1: Maps with boundaries and overlays
Figure 2: GeoJSON upload feature
Identify initial dependencies that are on the critical path for this functionality and may affect the delivery time and serving of business goals. Include links to stories.
| Description | Link |
|---|---|
| Name of story or release | Link to JIRA |
Initial communication between stakeholders and the development team to help understand scope and estimates.
Below is a list of questions to be addressed as a result of this requirements document:
| # | Question | Outcome | Status |
|---|---|---|---|
| 1 | Need clarification around multi-polygon requirements and associations. | ||
| 2 | Need to discuss how the approach to implementation as we believe many of these could be addressed in Tableau and third party reporting tables versus within OpenLMIS. |