Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

<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)

...

To ensure Groups feature is accessible compliant on portal

Every potential user including people with disabilities should have a decent user experience and be able to easily access Groups on the portal. The accessibility feature aims at ensuring the following:

  1. Compliance to https://www.w3.org/WAI/standards-guidelines/ and GIGW guidelines from an accessibility point of view.

  2. Ensuring the apps allow navigation using assisted devices

  3. Ensuring content can be played using assisted devices & tools

To notify users on important Groups actions

Users should be notified on important group actions so that they can be on top of it and also manage it effectively (through in-app notification). These notifications will be triggered by certain contextual triggers - for eg. when a user has been added to a group or when an activity is assigned to the group. This will use the new notification service that is built in a generalized manner that can be integrated in any context (Groups, DF, events etc.,). This will also replace the existing notification service that is used for certificate (while ensuring the workflows are retained as it is)

DF - Load testing (DB change & testing)

Based on the load testing results, it was concluded that the database needed to be changed from Mongo to Redis. With the database change, thorough testing was done to ensure none of the workflows break in any scenario.