--
You received this message because you are subscribed to the Google Groups "OpenLMIS Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openlmis-dev+unsubscribe@googlegroups.com.
To post to this group, send email to openlm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/f220702e-b63d-4f87-b7f2-ea45b21632ed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi Craig,I reviewed endpoints with red notes and proposed some actions in the https://openlmis.atlassian.net/wiki/spaces/OP/pages/380305418/APIs+Tech+Debt+review I hope we can discuss this on the next tech committee meeting.Regards,Lukasz
On Wed, May 9, 2018 at 2:50 PM, Craig Appl <ca...@ona.io> wrote:
Hi Everyone,I just finished a research spike for OLMIS-4651 that includes an analysis of all service API endpoints identifying how frequently the information changes and recommending whether we should consider ingesting it in the reporting stack. This is our first step in understanding what information should be stored in the reporting platform and assessing appropriate data models.This assessment also includes notes. Please review the notes in red for issues that may require development to improve the API. https://openlmis.atlassian.net/wiki/spaces/OP/pages/374636847/Microservice+API+Analysis+for+ReportingSincerely,Craig
--
You received this message because you are subscribed to the Google Groups "OpenLMIS Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openlmis-dev...@googlegroups.com.
To post to this group, send email to openlm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/f220702e-b63d-4f87-b7f2-ea45b21632ed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.