...
Task List
| Task | Component | Details | Status as of Oct 2017 |
|---|---|---|---|
| Minimum Integration | |||
| ODK Endpoint working in OpenLMIS | ODK | (requires OpenLMIS team help to understand RAML, etc)
| ODK team spun up ODK endpoint in Docker, Li Lin shared code and documentation |
| RBAC Magic Stringifier | OpenLMIS | converts 'dimensions' of facility/program/period in OpenLMIS into a string to use an a group/role name in ODK | OpenLMIS team released permission string feature in OpenLMIS 3.2.0 |
| Create ODK2 templates | both | with dimensions/reference data | |
| OAuth2 integration | ODK | ||
| OpenLMIS ODK program data connector service | OpenLMIS |
| |
| What this achieves: Can submit data from Android device, can see in OpenLMIS whether it is submitted. But we have solved the hard parts—auth, reference data lists, deployment. | |||
| Future Version | |||
| UI for web client data entry | OpenLMIS | without this, Android is required for ODK program data entry | |
| UI for data viewing/reporting | OpenLMIS | to view the program data that was submitted in the OpenLMIS web UI | |
| UI for ODK2 administration | OpenLMIS | without this, technical skills are required for an implementor to set up the ODK-OpenLMIS integration | |
| Support multiple program data forms per program | OpenLMIS | without this, there is at most 1 program data form per program | |
| Performance/Scaling for the endpoint and connector service | both | ||
| Long-term storage | OpenLMIS | store submissions inside OpenLMIS in long-term archive (because the storage inside the ODKv2 ecosystem is transient) | |
| Apply ODK beyond program data | OpenLMIS | other parts of OpenLMIS (apply this integration to other domains such as re-supply, stock management, etc) | |
| Push notification from endpoint via webhook | both | when new ODK data is available/synced | |
What this achieves:
| |||
User Story
| Gliffy | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...