Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

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

  • If score based, we propose to allow the creator to set a % (e.g. 75%) or average score (e.g. 3 out of 5)>

  1. Courses in Programs for Admins

Currently, all the other asset types like observation, survey, and projects can be wrapped in a program for admin persona except courses. Courses are important in the improvement and learning journey of HT and other officials' personas. Thus, it is important for a program designer to be able to map courses in a program to ensure the continuity of their learning.

This feature will allow the following:

  1. Program designers will be able to map relevant courses in a program targeted for a particular sub role and location.

  2. Program designers will be given creator’s rights that will allow them to open batches for their courses

  3. Once the course is mapped and the program is published, users will be able to take up courses in the program context.

2. Observation creation portal

Currently, the creation of observation is not self-serviceable and resource creators have to create the entire observation form via excel sheet templates which is a hectic and tiresome process. Further, the implementation/support team has to rework this and upload it at the backend after checking. This creates a lot of friction in the creation of the form. Thus having a self-serviceable observation creation portal was the need of the hour.

The observation creation portal will allow resource creators to easily create their observations and publish them on the platform. This will give the creator an idea of the look and feel of the questions and question sets on the app while creating the form. Having the self-service portal will reduce the backend and support related work too. The process of publishing observations will become smoother and quicker.

The capability will allow the following to resource creators:

  1. create questions and group them at the same time using the question set editor.

  2. create the observation form with ease in self-service mode.

  3. the review process for all the created forms will be enabled on the portal.

  4. dependencies for creating observation forms will be reduced

  5. creation of all the different resource types will be at a single place.

  • No labels