Date
Participants
Goals
Showcase the pipeline
Discuss next steps for pipeline
Discussion topics
Time | Item | Presenter | Notes |
|---|---|---|---|
Demo v2->v3 pipeline | |||
Discuss next steps |
Notes
Next:
launch the v3 reporting stack against current demo
we should see the same demo that has the couple Requisitions from v2->v3, this time with the standard v3 reports in the reporting stack
document any field that’s directly in Requisition transformation that doesn’t make it from v2->v3 (https://openlmis.atlassian.net/browse/OLMIS-6492)
Reach out to Elias and Hassan as we find things with questions (likely turn this into a wiki page)
Reflect on the permission scheme, and zones that that we load
For PoC we can document the first next step transformations that would need to be worked on.
Within PoC we can’t do this fully until we’re building the bigger migration that has access to a more complete data source (UAT/Training)
We’ll request access to launch against a testing uat or training instance
Alfred, to help with this?
We know that it’s currently moving from the cloud to in country.
Beyond the PoC:
Start pulling in / advocating for more resources
3-6 months for Ashraf, Elias, Hassan, Ian, etc
Work on getting access to NIDC (data center in TZ)
eLMIS moving there now
Investigate if we should procure a server/time there either for the pipeline and/or v3.
We can do this in stages depending on what’s easier and what’s more desired (e.g. we could leave most of the pipeline in the cloud and move v3 in, knowing the pipeline is more temporary).
Action items
- Alfred Mchau to work on Beyond PoC advocacy
- Alfred Mchau to advise and help with access to training / uat
- Chongsun Ahn (Unlicensed) to plan work for launching v3 reporting stack
- Chongsun Ahn (Unlicensed) to plan work for documenting fields that don’t make v2->v3 migration in Requisitions
- Chongsun Ahn (Unlicensed) to plan work on documenting “permission scheme and zones” migration that would happen post-PoC