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)

...

Selection of Multiple Sub roles

In the education system, many times, multiple system roles are assigned to a single person. For eg, a teacher can also be a CRP. A HT can also be a teacher. In UP,  teachers can be ARP or Shikshak Sankuls.  In Punjab, a teacher can be a Block Mentor. Thus, currently on the Diksha app, for the discovery of preferred resources the user has to keep changing their role/sub role in the profile. Thus it is important that users have a choice to select multiple sub-roles in their profile in order to ease the consumption of preferred resources.

In order to accommodate this request, User-org needs to make changes in APIs, DB and ES to accommodate this request.

  • Change the request and response format of user APIs to support the user subtype as an array. 

  • Data migration has to be done for existing data in cassandra 

  • User reindexing and data sync in ES