Time | Item | Who | Notes |
---|---|---|---|
10 min |
Josh's thoughts and questions:
Decision: bring to PC. Get decisions on the above questions. Share with team and start designing. | ||
20 min |
|
Permission discussion
Read API will be done first. Questions: Should the write API support batch and individual sign in creation? Decision: Need further discussion on the configuration of Sources/Destinations. How does a facility know who their valid sources and destinations? We should review and look into supply lines within requisitions. We know the hierarchy will be different than requisitions. Approach: VR suggests creating the write API while doing the read API, however leave out the business logic and outline all the questions to be addressed for configuring the new facilities. | |
10 min |
| ||
20 min | Open questions |
| |
5 min | New QA onboard |
|
Shiyu Jin (Deactivated), where are we with permissions? I'm pasting in what Lakshmi put together.
In the end I'd like something similar to requisitions to be completed for Stock Management so people can clearly see what is being built https://openlmis.atlassian.net/wiki/display/OP/Requisition+Rights.
Create | Update | Submit | Delete | View | |
Stock management _ create | X | X | X | ||
Stock management _ delete | X | ||||
Stock management _ view | X |
A few points of discussion: