Date
...
- Nick Reid (Deactivated) Understand ODK App Designer output, and how it might work within OpenLMIS
- Josh Zamor to send documents about OpenLMIS RBAC to ODK team
ODK 2.0 Description and Changes
Original ODK Update is a huge clump of code, that is being refactored into a dockerized service that doesn't use big table, but uses a structured database (mysql/postgres). Changes are coming to the Agrogate service API as the current API doesn't match the underlying structure — but a majority of the API should stay the same , and is keep the existing unit tests to honor the service API contracts.
Docker containers are stripped down aggrogate (built on linux and windows images). Trying to do two paraell paths — windows cloud or linux cloud
...
Users and permissions (groups)
Azure cloud
MSQL has structures we don’t want to rebuild (supporting 3rd party logins)
Currently aggregate permissions work as they did
How ODK and OpenLMIS might be integrated
Requisitions has data that needs to be configured — it is a mix of complex and simple data — so of it is programatic that would change in many different ways
...