User interface for Upload Reference Data tool


Create a mechanism for implementors to upload reference data CSV files during the initial setup of the OpenLMIS deployment.


  • Menu driven intuitive interface will enable new implementer to setup and configure OpenLMIS quickly and easily

  • Bulk upload will save time when loading sizable reference data such as facilities, products, geographic zones, etc.

  • UI will provide visual feedback (e.g. number of records processed)

  • Dependency on programmers will be reduced when this upload feature is made accessible with an easy to use user interface

User Interface (UI) added to Administration menu to enable users to initiate upload of reference data from CSV files.


The Reference Data Seed tool is a simple yet configurable tool that allows CSVs to be mapped to API calls of the Reference Data Service transforming the CSVs into Reference Data which a new instance of OpenLMIS can use.

Improving Reference Data Seed Tool

Adding a UI to accept the upload of the Reference Data Seed tool's CSVs and show a visual progress of the transformation of those CSVs into Reference Data created in the Reference Data Service is the primary approach.

This entails:

  • Writing a headless web UI which leverages the Reference Data Seed Tool.

  • Enhancing the Reference Data Seed Tool to accept data uploaded to it through HTTP

Leveraging Resource Map **

Resource Map is a graphical web-application which allows a nation to curate and visualize their resources (e.g. Facilities, services, etc) graphically. It also has bulk uploads via CSV however after the upload the data may be shown on a map and then refined as needed. Additionally Resource Map is the Reference Implementation of a National Facility Register, and is often found in countries (including Tanzania).

When starting an OpenLMIS instance, bulk uploading of Facilities (and administrative hierarchies), can be first done by launching Resource Map, uploading to Resource Map in its format (CSV), curating and refining the quality of the list using Resource Map's UI, and then finally as a last step launch a simple OpenLMIS tool to import the data from Resource Map, to OpenLMIS Reference Data.

This entails:

  • Writing OpenLMIS documentation to link to or describe how to launch Resource Map

  • Writing best practices / guidelines on importing Facilities and administrative hierarchies that OpenLMIS will find useful, into Resource Map.

  • Building an OpenLMIS ResourceMap Importer.

Component Architecture diagram.

Participants: JSI


  • Originally this was an epic on OpenLMIS 3.0.0 which was later de-prioritized.

  • Split out from epic OLMIS-566.

Query issues in this epic




Brandon Bowersox-Johnson




Epic Name

Upload Reference Data