@DoniaEsawi and @Mehul-Kumar-27 – This is where all of your communications this summer will reside.
Congratulations from all of us here at LibreHealth!
You may use the Jitsi room below for video chat. I count the fact that it’s linked as it being public.
I have added a Jitsi room link – you may use that and only that if you need video conferencing.
Hello @DoniaEsawi and @Mehul-Kumar-27. @sunbiz, myself, and the other mentors on this project are excited to be working with you on GSoC 2023! We would like to set up regular meetings, and are looking at the possibility of Wednesdays at 10 am EST. Can you kindly check your calendar and revert if this day/time would work in your location? Best, Dr. Bucher
Hello @shbucher and @sunbiz, thank you for reaching out. I am equally thrilled to have the opportunity to contribute to LibreHealth during the GSoC 2023. Wednesdays at 10:00 am EST work perfectly for me.
Great, @Mehul-Kumar-27 ! We will start next week. In the meantime, @sunbiz and I are meeting today to finalize Summer planning. More information will be posted on the forum later today, EST. Thanks!
Hello Dr. @shbucher ,
Thank you for reaching out and for your warm welcome! I am excited to work with you and the rest of the mentors on this project for GSoC 2023.
Wednesdays at 10 am EST works for me and I am available for regular meetings at that time. I will mark my calendar accordingly.
Thank you for your time and I look forward to our future discussions.
Do we need to join the Jitsi room for the meet ?
Hello @sunbiz and Dr. @shbucher,
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?