Page Comparison

Updates

• Average Consumptions Extention point
  • Requirements and use case isn't completley understood yet
  • Will come back after immediate deadlines are met
  • This will be an extention point, or use another method to calculate
  • Confluence page will be updated, when we return to this issue

Aggregate Requisitions

• RAML model has been delivered and approved by technical committee
• Main reason is to have a performant API in high-latency settings
• Point of contention is if the endpoint returns 400 or 200 when there is one requisition that errors
• Need to add contract tests for these endpoints
• Outcome: Discussion going to dev-forum, any changes
• UI changes are large, unsure if we want to merge into OpenLMIS-Requisition-UI
  • See MW-84 for proposed UI changes

• Goal: Need to be comfortable with proposed process AND have it publicly documented
• Focusing on extension points, which hopefully will extend to extra data process later
• See process details below
• Presumptions:
  • There are active maintainers to manage PRs
• Next Steps: Josh Zamor will formalize this write up and share in next tech committee meeting

• Question: In reference data, how do we want to handle adding pagination and extra data to resources in semantic versioning
• Answer: One big fat release
• Next Step: Josh Zamor will write a "stub" JIRA ticket