Versions Compared

Old Version 4

changes.mady.by.user Chongsun Ahn (Unlicensed)

Saved on

compared with

New Version 5

changes.mady.by.user Josh Zamor

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

TimeItemWhoNotes
5mAgenda and action item reviewJosh Zamor
20mDe-centralized lot managementSebastian Brudziński
  • Angola implementation cannot rely on centralized lot management and needs storeroom managers to be able to add lots in some way
  • Any plans, designs or ideas for anything similar ever existed in core?
  • MVP that would be accepted in core? It would be worth to design something that could be incorporated in core
15mPerformance testsSebastian Brudziński
  • More and more are failing
  • We cannot rely on results too much - /wiki/spaces/OP/pages/558825646
  • Do we have resources to continue fixing and taking care of them?
20mLook at streaming from CasperChongsun Ahn (Unlicensed)
  • Brief intro of goals of project:
    • proof of concept to show a gradual v2→v3 migration
    • focus on streaming data
  • What we've learned about:
    • considerations in building for streaming as opposed to batch
    • lessons from technology involved
  • what should OpenLMIS understand from this?
3mUI caching design - call for reviewsSebastian Brudziński

Notes


Decentralized Lot Management


  • Current implementation is to manage items and lots centrally, there's one admin right for both of these.
    • data quality was the big reason to choose this
  • Angola needs: 
    • not centralized
    • each user managing stock at the facility could manage lots as they go
      • through the physical inventory and receive processes
      • search first, then add lot as they go if it doesn't exist
    • Need something before next core release
  • What's the minimum working version that'd be accepted in core
    • configuration option to select either centralized or not-centralized
    • keep the boundaries between ref data and stock mgmt correct
      • in Angola it'd be a UI and right change (split), in core we'd likely want this to be more comprehensive
      • seems like lots would need to be created before a stock event could be fully processed, as a lot id is part of the stock event data
    • strategy for de-duplication:
      • report for mgmt to find dupes
      • stock events and stock line items are written in stone - they can't change.  We should keep this in mind that UPDATE on certain tables are not allowed.

...