Introduction

As part of e-creds experiment in 2.5.0, we've enabled issue of creds to non-registered platform entities like School and Student. But this eventually will need to be extended to any entity in the education system like District, Cluster, Block etc., Each entity/cred type could have a template of its own with a set of information (static + dynamic) to be displayed in the certificate. The input CSV file currently takes only one dynamic field, which is the recipient name. This needs to be enhanced to take multiple fields depending on the cred type and these fields need to be shown on the certificate.

 JTBD

Use Case - Overview

Enabling states to recognize best Student/Teacher/Cluster/Block/Teacher etc. by awarding them digital credentials. The scope of current and future use cases built on DIKSHA generic credentialing service will be limited for usage in education domain. 

https://project-sunbird.atlassian.net/browse/SB-15451

User Story 1 - Issue Certificate for non registered users based on the cred type

As a State admin, I would want to be able to issue certificate to non registered users based on the cred type, So that they are motivated and perform better

Pre-conditions: 

1. User is logged into the Program portal

2. Cred type is identified and defined/set

3. Contents of the CSV file are identified and defined/set

Business Workflow: 

1. Program/Product team identifies the cred type to be issued in discussion with the State

2. Based on the cred type, Program/Product team identifies the Certificate template (static and dynamic contents) in discussion with the State 

3. Implementation team to set up the cred type on the Program portal. Below two things are executed as part of this activity

   1. Certificate template is created (static content with hard coded text + dynamic contents/fields)

   2. The identified dynamic fields are made available in the CSV file 

4. Issuer logs in to the program portal and issues the certificate

5. Issuer downloads the certificates, prints and distributes to the recipients

Acceptance criteria:

Verify that:

Main work flow

1. The existing certs workflow remains unaltered with the below exceptions

   1. The newly set cred type should be available in the "select cred type" drop down

   2. Preview of the corresponding certificate template is displayed on selecting the cred type

   3. While uploading, the CSV file should contain the identified dynamic fields in the same format (this should support more than one dynamic field) 

2. The above workflow for a State is explained with an example for reference

   1. State decides to recognize "Best district" in various disciplines for the year 2018-2019 and issue digital certificates.

   2. A new cred type called "Best District" is identified by the program team after discussing with the State

   3. State identifies the static and dynamic contents to be part of the template, in discussion with the program/product team

   4. Based on the agreed certificate template, Implementation team creates the new cred type called "Best District" and creates the CSV file format (District Name, recognition, purpose, Timeline). All the identified fields in the CSV are mandatory 

   5. Issuer logs in to the Program portal

   6. Issues selects the newly added cred type "Best District" from the "select cred type" drop down

   7. Issuer previews the new certificate template for "Best District" cred type (as attached below)

   8. Issuer generates the digital certificate by uploading the CSV file in the defined format for the "Best District" cred type

   9. The rest of the workflow remains the same

Open

Open

Alternate work flow

None

Exceptional Workflow

1. When uploading the CSV file, if one or more records fail to get uploaded, the entire file should not get uploaded. Display error message as "The CSV file was not uploaded due to issues with one or more records in the file"

JIRA Ticket ID

https://project-sunbird.atlassian.net/browse/SB-15380

User Story 2 - Certificate template to support multiple languages

As a State Admin, I would want to have the Certificate be available in a language that is local to my state, So that it is easy for the recipients to understand

Pre-conditions:

1. Implementation team has set the language based on the state's request as part of cred type creation

2. User is logged into the programs portal

3. User selects the cred type

Acceptance criteria:

Verify that:

Main work flow

1. The certificate template is displayed in the set language in preview mode. Both the static and dynamic contents are displayed in the set language (This means that the user should be able to enter in the set language in the CSV file as well)

2. The certificate issued to the user is displayed in the set language

3. On scanning the QR code, the first screen where the user enters the certificate code/QR code is retained in English. The second screen where the certificate details are displayed needs to be in the set language 

4. Steps 1 to 3 work for all the languages that are currently supported 

Alternate Workflow

None

Exceptional Workflow

None

UI design

None

JIRA Ticket ID

https://project-sunbird.atlassian.net/browse/SB-15445

Localization Requirements

Telemetry Requirements

Non-Functional Requirements

Impact on other Products/Solutions

Impact on Existing Users/Data 

Key Metrics