- 1 Group members
- 2 Assignment
- 3 Requirements
- 4 Architecture
- 5 Licensing
- 6 Timeline
- 7 Division of labour
- 8 Repository
- 9 Working App
- 10 References
Carl Petter Boehlke
The application shall have two modes:
- Estimates, showing estimated months left of a selected stock, for chosen organization units.
- Time trend, showing time trend of stock for a single organization unit.
The user can choose between the two modes described above.
- Default min/max boundaries can be set by an administrator (administrator view in mockup).
- The user can specify their own desired min/max boundaries as well (user view in mockups).
- If the administrator has not set a default min/max boundary, there is no default min/max boundary in the plot.
- The user can specify one stock type, and multiple organization units.
- Show current estimates as columns in a column diagram.
- Columns outside the specified min/max boundaries will be highlighted.
- Estimates are calculated based on average consumption over the last 3 months, and current stock levels ((current stock) / (average consumption) = estimated months left).
- Default min/max boundaries are shared by all organization units.
For "Time trend":
- The user can select an organization unit, and a stock type.
- Show time trend(months) of available stock as a graph.
- The min/max boundaries are shown as lines in the graph.
- The user can choose the time period they wish to see the time trend for (by default the last 6 months).
- Default min/max boundaries are associated with a specific organization unit and stock type.
Changes from the initial requirements:
- Administrator has two min/max inputs, one for each mode.
- The administrator can create and save queries.
- The user can pick queries created by an administrator to generate plots quickly.
- The query options used by the administrator is also accessible to the user, but hidden behind a "Show advanced options" button.
- "Stock usage" and "Stock availability" are selected separately through separate dropdown menus. "Stock usage" is not used for the "timetrend"-mode.
- The administrator can delete old query presets.
- The administrator can see a preview of the results of their query before saving it.
- The "estimates"-mode has a "from"-date. The average use is calculated based on the period from the chosen date up to the current date.
- Show a tutorial for how to use the app when it is started.
We have chosen React JS, because of the view focused framework. We also feel that the group as a whole has more experience with React.
We used Create-React-App to set up the initial app and build our project.
We have used basic CSS functionality, but have not used any extra front end frameworks as we felt it would unnecessarily complicate the code.
Highcharts is a dynamic plotting tool. We used it to create the plots for our project since we found it easy to use and it quickly gave nice looking plots.
We used React-Select because we needed a dropdown-menu with search function, and the ability to select multiple items.
We used Semantic UI for improving the user interface.
The license for this Project is:
Attribution-NonCommercial 3.0 Unported (CC BY-NC 3.0)
complete license info: https://creativecommons.org/licenses/by-nc/3.0/legalcode
We originally used MIT licensing, that the components React-Select, Semantic-UI and React JS had.
Sadly, late in the project we discovered that Highcharts is not compatible with any open source licenses , therefore we need to use CC(creative commons) Attribution-NonCommercial 3.0 Unported (CC BY-NC 3.0). This means our app cannot be used for commercial purposes.
The full license information can be found here: https://github.uio.no/TeamHope/project/edit/uitest/dhisapp/LICENSE.MD
|1||Wiki page ready||November 1st||October 27th||Will be improved more as the project evolves|
|2||Start of coding||October 31st||October 27th|
|3||Prototype ready||November 7th||November 3rd|
|4||App ready for use||November 20th||November 20th||Still missing Dashboard App|
|5||End of coding||December 5th||December 4th||Dashboard app implemented and UI improved|
Division of labour
We divided in some specific tasks, although overall we all worked with React JS, and also with the API to connect with DHIS2. Since this was important for everyone.
- Mode selector component
- Input min/max (user&admin) component
- UserInput component
- Availability/Used selector
- Validate user input in MenuContainer.
- Implement method getProperties in MenuContainer.
- Create "try it out" button for admin.
- Calculations and data manipulation prior to plotting
- API calls related to datastores and user authority
- Admin panel logic (Displaying nothing if user has insufficient authority)
- Dashboard App (Peer programmed with Mikkel)
- Building and uploading to Dhis (fixing manifiests, icons, etc.)
- Organization selector component
- Stock selector (and fetch from database)
- API-calls to analytics
- getPredifined method from namespace, Initial business logic for data for plotting
- Semantic UI Implementation. Design
- Architecture document
- Period selector
- Delete preset component in admin panel
- Frontend layout
- Gather adminpanel input
- Validate input in admin panel
- Dashboard App (Peer programmed with Kristian)
See our Github page for more information about each task.
- Nordli, Lars Henrik and Orlova, Ekaterina. 2017, Introduction to front-end development, lecture notes, INF5750: Open Source Development, UiO.