You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
UCI is created with a vision to make the conversation flow creation configurable to a level, that it can be done by program owners, without the intervention of any engineers at all. At the same time, it also envisions reducing the redundant coding required for enabling the same business logic for different channels.
UCI aims to democratize the use of different communication channels such as WhatsApp, Telegram, SMS, email and more across all governance use cases.
UCI is being used to create 2 ways communication channels via chatbots between lakhs of teachers in Uttar Pradesh & the state. These chatbots are configured from an admin panel and trigger notifications to the teachers. Teachers then click on the notifications on their Android phones and talk to the chatbot. This is making day to day communication realtime & very effective between teachers and the state.
Features to be implemented
Once a notification is received, frontend clients can send back telemetry / analytics to the UCI acknowledging delivery and read receipts of the notifications. Currently this telemetry is not visualised.
We need to plan and implement a dashboard which will visualise the data to the users.
This could be integrated in the UCI - Admin repo itself.
What exists
firebase/web API already exists in inbound. Declared here. The data is being inserted into a database as well.
The number of sections and items within each section can change. This needs to be visualized on the dashboard where each section should have its own graph illustrating its own items data.
All the services also generate log files which should be viewable from the dashboard itself. The log files may contains several GBs of data hence it is crucial to handle the pooling of data from the frontend and limit the amount of data being downloaded or else, it may be detrimental to the system. The functionality should consist of the following:
Pooling log data from the server.
Filtering logs based on a search string.
What needs to be built
Reading data from the database
Adding visualization to uci - admin
Reading data from 1 and showing in 2
Learning Path
Complexity
Medium
Skills Required
Java to understand BE systems, React to design and develop the dashboard.
This issue is nominated for Code for GovTech (C4GT) 2023 edition.
C4GT is India's first annual coding program to create a community that can build and contribute to global Digital Public Goods. If you want to use Open Source GovTech to create impact, then this is the opportunity for you! More about C4GT here: https://codeforgovtech.in/
Project Details
UCI is created with a vision to make the conversation flow creation configurable to a level, that it can be done by program owners, without the intervention of any engineers at all. At the same time, it also envisions reducing the redundant coding required for enabling the same business logic for different channels.
UCI aims to democratize the use of different communication channels such as WhatsApp, Telegram, SMS, email and more across all governance use cases.
UCI is being used to create 2 ways communication channels via chatbots between lakhs of teachers in Uttar Pradesh & the state. These chatbots are configured from an admin panel and trigger notifications to the teachers. Teachers then click on the notifications on their Android phones and talk to the chatbot. This is making day to day communication realtime & very effective between teachers and the state.
Features to be implemented
Once a notification is received, frontend clients can send back telemetry / analytics to the UCI acknowledging delivery and read receipts of the notifications. Currently this telemetry is not visualised.
We need to plan and implement a dashboard which will visualise the data to the users.
This could be integrated in the UCI - Admin repo itself.
What exists
firebase/webAPI already exists in inbound. Declared here. The data is being inserted into a database as well.Payload for API:
{ "text": "", "from": "", "messageId": "", "eventType": "DELIVERED/READ", "report": { "externalId": "", "destAdd": "", "fcmDestAdd": "" } }Apart from this, the notification monitoring script outputs log data and Kafka data in a JSON format given below:
The number of sections and items within each section can change. This needs to be visualized on the dashboard where each section should have its own graph illustrating its own items data.
All the services also generate log files which should be viewable from the dashboard itself. The log files may contains several GBs of data hence it is crucial to handle the pooling of data from the frontend and limit the amount of data being downloaded or else, it may be detrimental to the system. The functionality should consist of the following:
What needs to be built
Learning Path
Complexity
Medium
Skills Required
Java to understand BE systems, React to design and develop the dashboard.
Name of Mentors:
@chinmoy12c
Project size
8 Weeks
Product Set Up
https://github.com/samagra-comms/docker-deploy#manual-setup---one-click-deployment-is-wip
Acceptance Criteria
Out of Scope
Milestones
Designs
We shall refer to open source posthog visualizations.
C4GT
This issue is nominated for Code for GovTech (C4GT) 2023 edition.
C4GT is India's first annual coding program to create a community that can build and contribute to global Digital Public Goods. If you want to use Open Source GovTech to create impact, then this is the opportunity for you! More about C4GT here: https://codeforgovtech.in/