<Proposed capability name. Should describe the capability in max 4 words. e.g. Creating Merit Certificates>
<Summarize the capability by answering the questions ‘Why are you developing the said capability?’ i.e. what problem is the capability trying to resolve, and ‘What is your proposed solution?’>
<Sample text:
States and organizations feel the need to motivate and recognize deserving learners.
To address this need, States/organizations can issue Merit certificates from DIKSHA. However, since the criteria for merit cannot be standard, we propose to make the merit criteria (rules) configurable. The parameters that States/organizations can set are:
...
who will get the certificate (all users or select few),
...
when (on completion of assessment or based on a score, or both)
...
Support for multiple Consent Statuses
Till date, the system supported only one type of consent - the user was considered to have given consent, or not. We’re now seeing a need for different types of consent. A user may choose to first give consent, and then remove it. Also, the consent may be removed by the system for various reasons.
Hence, the construct of ‘Consent’ will be expanded to include 3 types of consent : Active, Deleted, Revoked.
Reporting jobs will be updated accordingly to include only ‘active’ consents for reporting.
Additional user meta-data to be displayed on QR scan from Certificate
Validation of a certificate (via a QR code scan) may require additional parameters (as compared to what is already available on the certificate) to be displayed. The list of meta-data included in the certificate is to be enhanced to make available a super-set of user meta-data fields
Viewer Service Implementation
The current APIs for progress and score computation are being rewritten to be made further granular and better support scale and stability requirements. The current APIs will be replaced with four APIs - Start, Update, End, Read (and also Summary)
The implementation of these APIs, related Flink job changes, deployment scripts, test cases and load testing will be taken up as part of Release 4.4
Assessments Archival
Archival of assessments data for better management of accumulating data - Implementation, test cases, load testing, Flink job changes, refactoring of activity aggregator and enrolment reconciliation jobs.
Ability for a user to select multiple sub-roles
There are use cases for a user of type Head Teacher/ official to be able to select multiple sub-roles, as such users may be handling more than one sub role - this is necessary to ensure they are able to discover content/ programs targeted to them. This change will permit for users of type HT/ officials to be able to select more than one sub-role
User Consent related changes
Proper updation of Consent and Declaration tables on user migration from Custodian to State tenant
Data migration required as part of a fix for existing users
Tech Items
Load testing of User Read API to increase TPS
SMS Provider changes
Merge Verify OTP with V1 User Sign Up