Sprint 1: 15 Feb - 28 Feb 2018 OpenSRP Integration Backlog Grooming

Goal: Develop a Nifi integration with OpenLMIS to create order and receive shipment. Also develop OpenSRP server data models to request an order and receive a shipment. Light design and development in Android client to support development in Sprint 2.

Dates: Feb 15, 2018 - Feb 28, 2018 

Nifi

• EPIC: Develop a flow to create an order in OpenLMIS (@Antonate Maritim (Unlicensed) or Kelvin)
  Dependency: This task is dependent on defining the OpenSRP API endpoint 

  • Get a sample representation of the OpenLMIS order for the demo to request a resupply based in ISAs (@Craig Appl (Unlicensed))

  • Identify metadata needed for demo (demo location, product and antigen order map) (@Craig Appl (Unlicensed))

  • Develop a metadata map between OpenLMIS demo location ID and OpenSRP server demo location ID

  • Develop the Order template text file to store in Nifi

  • Create and test the flows

• EPIC: Develop a flow to query OpenLMIS for a shipment and convert it to the OpenSRP data model(@Antonate Maritim (Unlicensed) or Kelvin)
  Dependency: This task is dependent on defining the OpenSRP API endpoint

  • Get a sample representation of the OpenLMIS shipment for the demo (@Craig Appl (Unlicensed))

  • Identify metadata needed for demo (demo location, product and antigen shipment map) (@Craig Appl (Unlicensed))

  • Develop the Shipment template text file to store in Nifi that matches the shipment to the antigen type

  • Develop the flow to push the shipment to the OpenSRP API

  • Create a flow to query OpenLMIS shipment API

  • Create a flow to post the shipment to OpenSRP server's API

OpenSRP Server

• EPIC: Develop a data model and API to store and get order requests (Ephraim K and Vinny)

  • Define the API endpoint and structure (include: @Craig Appl (Unlicensed) and @Peter Lubell-Doughtie (Unlicensed))

  • Define the data model

  • Define a standardized API (May require a new API pattern specifically for Orders) 

  • Develop the data model and services

  • Develop the API

• EPIC: Develop a data model and API to store shipments (Ephraim K and Vinny)

  • Define the API endpoint and structure (include: @Craig Appl (Unlicensed) and @Peter Lubell-Doughtie (Unlicensed))

  • Define the data model

  • Define a standardized API (May require a new API pattern specifically for Orders)

  • Develop the data model and services

  • Develop the API

Android Client

• EPIC: Work on Android Client design for both create order and receive shipment (@Craig Appl (Unlicensed)

  • Define mock-ups of UI (@Craig Appl (Unlicensed) & Roger Wong)

  • Solidify end user workflows (@Craig Appl (Unlicensed))

• EPIC: Develop the ability to request stock from the Android Client (Ephraim K and Vinny)

  • Begin scoping the Android client syncing strategy

  • Scope the Android client data model