Instructions to use this template:

Use this template to write the Product Requirements Document (PRD) for a single User JTBD or Initiative.
Each workflow within the PRD will correspond to an Epic in JIRA. Each User Story will correspond to a Story in JIRA that will be part of the Epic.
Each section in the template has instructions, with examples explaining the type of content to be written in that section.
You may start typing into the section by eliminating the instructional text, or delete the instructional text after you have entered all content for the section.
Repeat from section <Use Case 1> Overview for every use case in the User JTBD or Initiative

Table of Contents

outline	true

Introduction

Content Sourcing of ETB is the step of ETB process where states pool existing content from various sources or create new content relevant to the textbooks that are part of their ETB program scope.

Following are the different ways content is sourced for ETB:

Upload existing content (pdfs, videos or html)
Reuse existing DIKSHA content
Create new content

However this content sourcing process is not textbook driven. The content is uploaded/created, reviewed and published outside the scope of ETB. Once published, they are linked to the relevant textbooks. This results in multiple issues:

Content contributors do not have the right context when they create or upload content, resulting in content that may not be very relevant.
Content contributors have to explicitly tag the content with relevant board, medium, class, subjects and topics based on the textbook for which the content is created.
ETB program administrators cannot track the progress of ETB - number of contents that are getting created, reviewed for each textbook.

To solve the above problems, the solution is to enable content contributors to contribute content (upload existing or create new) based on Textbooks under program scope. This process has been enabled as an experiment for CBSE. The same has to be enabled for all the states.

JTBD

Jobs To Be Done:
1. As a content contributor I want to contribute relevant content for the textbooks under program scope.
2. As a content reviewer I want to review the content contributed for textbook under program scope.
3. As a program admin I want to see the over all content dashboard for monitoring.
User Personas: This story is relevant for Content contributor, content reviewer, program admin.

Requirement Specifications

Pre-requisites:

A state sets up an ETB program and defines the scope from back-end (same as existing functionality for CBSE).
The state configures textbook creators, textbook reviewers, content contributors and content reviewers for the program through back-end.
Textbook creators create or add ETBs to the program scope (as defined in the story:
Jira Legacy
server System JIRA
serverId 2207a759-5bc8-39c5-9cd2-aa9ccc1f65dd
key SB-16761
). As long as mentioned story is not implemented, it can also be done form back-end.

Contribution can be done either by contributing individual content or through bulk upload.

<Use Case 1> Content contribution for a textbook through bulk upload.

Bulk upload option shall be available for a textbook under program. Bulk upload will be done only for a textbook at a time. Bulk upload can be done only by a user who has both content contributor and review roles in the program. Textbook for which the bulk upload is being done must be in draft state. Upon successful upload content would be created, published and linked to relevant section of the textbook as mentioned in input file. A textbook must not be published unless it has any of the linked content in draft state. It should through an error mentioning "Kindly publish all the linked content".

<Use Case 1 Overall Process Workflow>

Image Added

<Use Case 1 - User Story 1> User access Diksha platform

<Main Scenario> Authorized user having valid content creator and reviewer rights for a program under state tenant access Diksha.

Srl. No.	User Action	Expected Result
	User enters Diksha URL	Diksha page opens with sign in option.
	User enters valid credentials	User sign in and land on tenant home page

<Use Case 1 - User Story 2> User selects required textbook under program for which bulk upload has to be done

<Main Scenario> Valid user having content creator and reviewer rights for a program access relevant textbook under program for which bulk upload has to be done.

Srl. No.	User Action	Expected Result
	User clicks on "Contribute"	Program list page opens which has all the programs created for the state.
	User selects required program	User lands on the textbook page. Page has all the books displayed under program scope.
	User selects the required textbook	Textbook structure (TOC) page opens which has contribution options both either to contribute at each node one by one or to bulk upload.

Exception Scenarios

Srl. No.	Error / Exception	Expected Handling
	In case user does not has contributor right for any of the program	User will not see "Contribute" option on Diksha tenant home page on top
	In case user clicks on any of the other program for which he does not has access	Error message should be displayed "Unauthorized Access"

<Use Case 1 - User Story 3> User selects bulk upload option

<Main Scenario> Valid user having content creator and reviewer rights for a program selects bulk upload option on textbook level.

Srl. No.

User Action

Expected Result

On Textbook level user clicks on "Upload CSV for Bulk Upload"

Dialogue box opens with option to upload file

User clicks on "Sample File" option in dialogue box

Sample file gets downloaded

Link to sample file: https://docs.google.com/spreadsheets/d/1zo_KVAU3y_RR3p4Gpgud-geROZYXv9Efpgwdflszemc/edit#gid=0

<Alternate Scenario 1>

Srl. No.

User Action

Expected Result

User clicks on "Last Uploaded File"

This should display the upload status of the last upload.

Start Time
End Time
Total number of content
Content successfully processed
Content failed
Link to download status report "Download Report"

For the first time it would not be there since there is no previous bulk upload.

Exception Scenarios

Srl. No.	Error / Exception	Expected Handling
	If user does not has reviewer rights for the program.	Bulk upload option shall not be available for such users on textbook level. They can only contribute content one by one for respective node.

<Use Case 1 - User Story

1> Overview<Main Scenario>

4> Populate sample file and upload

<Main Scenario> Valid user having content creator and reviewer rights for a program populate the sample file and upload

Srl. No.	User Action	Expected Result
	User populates the bulk upload sheet in the required format.	File should not have any validation errors.
	User selects ""Upload CSV for Bulk Upload"	Dialogue box opens with an option to select and upload csv
	User click on "upload"	User prompted to select the bulk upload file from local device.
	Click on "Start Upload"	Upload should start

<Alternate Scenario 1>

Srl. No.	User Action	Expected Result
	In dialogue box, After selecting the file from local device, an option should display "Change File".	Upon clicking on it, user should be prompted to again pick up file from local machine.

Exception Scenarios

Srl. No.	Error / Exception	Expected Handling
	In case file contains validation errors	Error dialogue box should appear with listed validation errors (Refer validation error section in the last of this PRD for detail).

<Use Case 1 - User Story 5> Rectification of validation errors and upload again

<Main Scenario> User will rectify validation errors identified and upload again.

Srl. No.	User Action	Expected Result
	User rectify the errors identified.	File should not have any validation errors.
	User upload rectified file.	Successful upload starts and user should be redirected to textbook level page.
	While upload is in progress and user clicking on "View Report	User should be redirected to bulk upload status dialogue box, where user should see the following fields: Start Time End Time - Currently there wont be end time since upload still in progress Total number of content Content successfully processed Content failed Link to download status report "Download Report" Status report would have the following additional fields (apart from input bulk sheet fields) for each row (representing each content) Upload Status: Success, Fail Content Do_Id: If success, than do id of the created content Reason of Failure: If fail, than reason of failure. In case there are multiple reasons for failure, display each of them by numbering them in the same cell for each row.
	Once upload is complete	1. Once upload is complete, "Upload csv file" button will be enabled. Now user can start a new upload. 2.There will be two type of complete status - would be displayed depending upon contents upload status: Completed : When there is no content failure in status report Completed with errors : When there are content which got failed because of some error. In this case user to check the details and download status report. 3.Till the new upload is started, "Last uploaded file" will show the status of previous upload. 4. User would be required to rectify the reason of failure and upload the failed content again 5. Once Bulk Upload is completed successfully, all the contents are published and linked to the textbook for the respective sections as given in the upload csv file.

Exception Scenarios

Srl. No.	Error / Exception	Expected Handling
	While upload is in progress, user tries to click on "Upload CSV"	Button should be disabled for next upload while upload is in progress

<Use Case 1 - User Story 6>

<Main Scenario> Valid user having content creator and reviewer rights for a program access Diksha.

Srl. No.	User Action	Expected Result
	User enters Diksha URL	Diksha
	User enters valid credentials

<Alternate Scenario 1>

Srl. No.	User Action	Expected Result

Exception Scenarios

Srl. No.	Error / Exception	Expected Handling

Wireframes

For Future Release

JIRA Ticket ID

<Use Case 1 - User Story 6> User access Diksha platform

<Main Scenario> Valid user having content creator and reviewer rights for a program access Diksha.

Srl. No.	User Action	Expected Result
	User enters Diksha URL	Diksha
	User enters valid credentials

<Alternate Scenario 1>

Srl. No.	User Action	Expected Result

Exception Scenarios

Srl. No.	Error / Exception	Expected Handling

Wireframes

For Future Release

JIRA Ticket ID

<Use Case 1 - User Story

2> Overview

6> User access Diksha platform

<Main Scenario> Valid user having content creator and reviewer rights for a program access Diksha.

Srl. No.	User Action	Expected Result
	User enters Diksha URL	Diksha
	User enters valid credentials

<Alternate Scenario 1>

Srl. No.	User Action	Expected Result

Exception Scenarios

Srl. No.	Error / Exception	Expected Handling

Wireframes

For Future Release

JIRA Ticket ID

Localization Requirements

UI Element	Description	Language(s)/ Locales Required

Telemetry Requirements

Event Name	Description	Purpose

Non-Functional Requirements

Performance / Responsiveness Requirements	Load/Volume Requirements	Security / Privacy Requirements

Impact on other Products/Solutions

Product/Solution Impacted	Impact Description

Impact on Existing Users/Data

User/Data Impacted	Impact Description

Key Metrics

Srl. No.	Metric	Purpose of Metric

Version	Old Version 1	New Version 2
Changes made by	Snehil Verma	Snehil Verma
Saved on	Feb 02, 2020	Feb 02, 2020

Content Comparison

Versions Compared

Key

Introduction

JTBD

Requirement Specifications

<Use Case 1> Content contribution for a textbook through bulk upload.

<Use Case 1 Overall Process Workflow>

<Use Case 1 - User Story 1> User access Diksha platform

<Main Scenario> Authorized user having valid content creator and reviewer rights for a program under state tenant access Diksha.

<Use Case 1 - User Story 2> User selects required textbook under program for which bulk upload has to be done

<Main Scenario> Valid user having content creator and reviewer rights for a program access relevant textbook under program for which bulk upload has to be done.

Exception Scenarios

<Use Case 1 - User Story 3> User selects bulk upload option

<Main Scenario> Valid user having content creator and reviewer rights for a program selects bulk upload option on textbook level.

<Alternate Scenario 1>

Exception Scenarios

<Use Case 1 - User Story

4> Populate sample file and upload

<Main Scenario> Valid user having content creator and reviewer rights for a program populate the sample file and upload

<Alternate Scenario 1>

Exception Scenarios

<Use Case 1 - User Story 5> Rectification of validation errors and upload again

<Main Scenario> User will rectify validation errors identified and upload again.

Exception Scenarios

<Use Case 1 - User Story 6>

<Main Scenario> Valid user having content creator and reviewer rights for a program access Diksha.

<Alternate Scenario 1>

Exception Scenarios

Wireframes

For Future Release

JIRA Ticket ID

<Use Case 1 - User Story 6> User access Diksha platform

<Main Scenario> Valid user having content creator and reviewer rights for a program access Diksha.

<Alternate Scenario 1>

Exception Scenarios

Wireframes

For Future Release

JIRA Ticket ID

<Use Case 1 - User Story

6> User access Diksha platform

<Main Scenario> Valid user having content creator and reviewer rights for a program access Diksha.

<Alternate Scenario 1>

Exception Scenarios

Wireframes

For Future Release

JIRA Ticket ID

Localization Requirements

Telemetry Requirements

Non-Functional Requirements

Impact on other Products/Solutions

Impact on Existing Users/Data

Key Metrics