Compared to last sprint, my group and the other AMPATH groups have gotten a lot more done. At the beginning of the sprint we were fortunate to get some information and feedback from Gregory Schmidt. Greg created videos that pretty much described what he wants from this project. Link: https://www.youtube.com/playlist?list=PL7e8VJ_ZN6eo13AmOMnvXgUEZ38J9pygN) The first video is pretty much an overview of what the layout will be as a whole. Here he explains what he wants for the main components. This included a form page, a patient list, left navigation bar and multiple patient lists. From there he goes in depth on each of the components. The first component is the selection cards and tab rows. This video was especially helpful because Greg mentioned apps that include the tab piece. Along with the other parts, he used Google Mail a lot to reference which helps us have a visual idea of what he wants. The last two videos that were included in the playlist of videos included what he wanted for the navigation elements. After watching all of the videos and figuring out the main components needed for the project we split them up and each was assigned to a team.
The one my group and I decided on was the tab rows. We were thankfully given a link that goes through a demo for mobile angular app development by Kathleen Law. (Link: http://mobileangularui.com/demo/#/tabs) There were a number of different kinds of components and tools that that were listed. Kat also gave us the link to the documentation too. (Link: http://mobileangularui.com/docs/) Of these, a tab component was given, which helped us out greatly. Sam also found a link that pretty much gives us skeleton code for the tab component. (Link: https://material.angular.io/components/tabs/overview) All three of these links will help us out when it comes to actually writing the code.
The last thing that was done during the sprint was kind of a group effort between all of the teams. Professor Wurst created a repository for all of the teams. (Link: https://github.com/cs-worcester-cs-448-sp-2019/amrs-simple-app). In this repository there is the whole entire AMPATH project. Professor Wurst also created all of the teams that are contributing to this project. While getting everything set up we also figured out that we will need to find all of the services that will be needed for each part of the project and mock the services that will be needed for each component. Andrew Finneran created a group on Slack called ‘ampath-server’ and gave us an example which was in the ng2-ams file. In that file you find the src file and then go into it and then find the app file and go into that. From there you look for two kinds of folders, one names etl-api and the other was names openmrs-api. Both of these offer all kinds of services. When you clicked into a server that you needed you will see a bunch of code but specifically a url that goes to the server and then the functions of each of the codes call that url. This is helpful because we will need to in the future mock up these function to return values.
We as a class also decided to created a ampath-frontend slack group which consists of us talking about how we will start the project. We decided that we will push up a blank angular project in the github repository that i listed above. The master branch was set to protected so no one could push it directly and for each story that we work on within our groups we will make a separate branch to work on it.
