As the coding period has started, I have begun working on the authentication section to get started. In my proposal, I mentioned a problem that currently exists in the application. The issue revolves around the hardcoded uids of the tracked attributes and tracked entities of the NeoRoo program present at the DHIS2 server. This could pose a major problem in large-scale deployments since not all hospitals would have the same DHIS2 server and uids would be different for them, thereby restricting their access to the NeoRoo program.
To address this problem, I have proposed creating an API layer. This layer would fetch the uids of the attributes and the entity of the NeoRoo program after successful authentication from the DHIS2 server, which the user enters on the login page. If the attributes are present, this API section would store them in the application. However, if they are not present, it would proceed to create them.
Would you like me to work on this until we meet on Wednesday?
You cannot claim you did not know. Missing one will not hurt you – miss more and it will. Please complete the weekly reports ASAP that was due on Friday.
Jiatsu link last week didn’t work, so the teams were unable to meet. @sunbiz and I will now utilize public zoom links. I am currently in DC on NIH business. @sunbiz will meet with the teams this week.
Yes, but it didn’t work. I hurriedly tried to generate a Zoom link, but that didn’t work either. I hope this week will go more smoothly, with @sunbiz… Wednesday 10 am, EST.
Please come prepared with an extension of the proposal’s timeline as a PPT, a list of issues, and their description that you will work on over the summer. So, an issue should be the most basic unit of work and there can be 3-4 issues that you can work on to implement a feature. We will discuss your suggested issue list and prioritize the order in which you should start working on them.
@sunbiz , Dr @shbucher , I have opened a new issue, and the here is the pull request for the same.
Please review it, and suggest the enhancements that could be made.
@sunbiz, as you suggested, I tried creating a data element group. However, when attempting to assign data elements to it, I encountered an issue. Instead of getting the tracked entity attributes, only the data elements were available for selection. It seems that we can only assign data elements to a data element group. Is there a way to include tracked entity attributes in the assignment process as well?
Also I have updated the Merge Request, please review it for further improvements.
@sunbiz I have made another commit on the same merge request of the changes you suggested, I’m so sorry for being late on fixing it, I just had a problem with my email and didn’t get the notification but this won’t happen again
Hello @Mehul-Kumar-27@DoniaEsawi@akashsri3! Myself and @sunbiz look forward to our weekly meeting today, 10 am EST. Please use the public Zoom like provided by Professor Purkayastha last week. We look forward to updates on your projects. I am available to answer questions regarding the proposed clinical and implementation context for ECEB and NeoRoo. Thanks!
Strong work, Mehul. Also to @akashsri3 and @DoniaEsawi: One of the most innovative aspects of the open-source apps that @sunbiz and I + the teams are developing is the seamless integration of our suite of newborn care apps with DHIS2. Your work on the NeoRoo and ECEB apps is critical, in this regard. Be sure to follow the advice relayed by @sunbiz in our weekly scrum meetings, as he is one of the world’s leading experts regarding development within DHIS2 Android! This includes both his advice in regards to best practices for open-source code development and documentation, as well as specific advice to overcome technical blockers (at the level of actually writing and deploying successful code). Best, Dr. Sherri
