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:

1. Upload existing content (pdfs, videos or html)
2. Reuse existing DIKSHA content
3. 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:

1. Content contributors  do not have the right context when they create or upload content, resulting in content that may not be very relevant.
2. 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.
3. 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:

1. A state sets up an ETB program and defines the scope from back-end (same as existing functionality for CBSE).
2. The state configures textbook creators, textbook reviewers, content contributors and content reviewers for the program through back-end.
3. 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 will be done form back-end.

Contribution can be done either by contributing content to respective node of the textbook 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. A new role "Bulk content publisher" will be created in the system and a user with that role can only do Bulk upload and publishing of content. Textbook for which the bulk upload is being done must be in draft state. Multiple bulk upload can be done for a textbook, but not at the same time. Upon successful upload, content would be created, published and linked to relevant section of the textbook as mentioned in bulk upload file.

Overall Process Workflow

User Story: A new role "Bulk Content Publisher" is enabled in the system and a set of users are configured with this role for ETB Program

System will enable a new role called "Bulk Content Publisher". A user with this role can perform the following actions:

1. Bulk upload content - This will create all content that is bulk uploaded and as well as publish it
2. Link content to a given Textbook - Link bulk uploaded content to Textbook sections

User Story: User accesses DIKSHA & selects required textbook under program for which bulk upload has to be done

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

Exception Scenarios

User Story: User selects bulk upload option

Main Scenario: User selects bulk upload option for the first time for the textbook

Alternate Scenario: User selects bulk upload option, after completing a previous bulk upload

Alternate Scenario: User selects bulk upload option, after completing a previous bulk upload

Alternate Scenario: User selects bulk upload option, while a bulk upload process is in progress

Exception Scenarios

Alternate Scenario: User selects bulk upload option, while a bulk upload process is in progress

Main Scenario: User uploads Bulk Upload CSV and starts upload process

Srl. No.

User Action

Expected Result

User populates the bulk upload file in the required format in her local system

User selects ""Upload File"

Dialogue box opens with an option to select and upload csv

User selects bulk upload file from local system and clicks on "Start Upload"

Upload is started and user is taken back to Bulk Upload dialog

Alternate Scenario: Change Bulk Uploaded File

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

User Story 3: Populate Bulk Upload csv file and start upload 

Main Scenario: User uploads Bulk Upload CSV and upload process starts successfully

Alternate Scenario

Srl. No.

User Action

Expected Result

User clicks on "Last Upload Status"

This should display the upload status of the last upload.

1. Start Time

2. End Time

3. Total number of content

4. Content published and linked

5. Content failed

6. Content to be processed

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

In case file contains validation errors

Bulk Upload dialogue shows the list of validation errors (Refer validation error section in the last of this PRD for detail).

User Story 4: Rectification of validation errors and upload again

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

Alternate Scenario: User selects "Download Sample File" option

Exception Scenarios

User Story 4: User views "Last Upload Status" section

Main Scenario: User views "Last Upload Status" section of an ongoing bulk upload process

Alternative Scenario: User views "Last Upload Status" section of a completed bulk upload process

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

Wire frames

Wire frame link: https://projects.invisionapp.com/share/7QST139948N#/screens/374220905 

Localization Requirements

NA

Telemetry Requirements

Alternative Scenario: User downloads Bulk Upload Status Report

Exception Scenarios: Bulk upload Process is "Aborted"

Wire frames

Wire frame link: https://projects.invisionapp.com/share/7QST139948N#/screens/374220905 

Localization Requirements

There are no localization requirements for UI. UI is only in English.

However, the Bulk Upload CSV should support values in Indian languages for fields like - Content Name, Description, Textbook Level names, Topics, Keywords etc - where the fields can be in Indian languages. The values are expected to be in Unicode.

Telemetry Requirements

Non-Functional Requirements

Impact on other Products/Solutions

Impact on Existing Users/Data 

Key Metrics

Number of content successfully uploaded on following parameters:

• Total number of bulk upload contents for a Textbook
• Total number bulk upload contents for a subject under program scope (can have more than one textbook)
• Total number bulk upload contents for a Grade (can have multiple subject and multiple textbook)
• Total number bulk upload contents for a program

Validations

Prerequisite for bulk upload:

1. Textbook for which the bulk upload is being done must be in draft state.
2. 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".
3. Before any validation/processing, space trimming should be done for preceding and trailing value of each cell.
4. Validation must be done before the content creation for each row. For example system should read the entire row, in case any mandatory cell value is missing, fail the content creation for that row and display with error message in status report.  

Non-Functional Requirements

Impact on other Products/Solutions

N/A

Impact on Existing Users/Data 

N/A

Key Metrics

Validations

General Rules:

1. Textbook for which the bulk upload is being done must be in draft state.
2. Before any validation/processing, space trimming should be done for preceding and trailing value of each cell.
3. Validation must be done before the content creation for each row. For example system should read the entire row, in case any mandatory cell value is missing, fail the content creation for that row and display with error message in status report.  

Assumptions

1. :Level columns in bulk csv file contain textbook unit names.
2. Textbook unit names - There are NO two textbook units with same name and with same hierarchy (levels). In case they are present, system takes the first one to link

3. Topics and Keywords - More than one topics or keywords are separated by commas. They do not contain commas within them

4. Through bulk upload process, the content is always linked to the given textbook. NO content is removed from textbook through this process
5. It is assumed that the textbook for which bulk upload happens is not simultaneously edited using textbook editor during the process. Parallel editing of textbook might delete the linked content through bulk upload
6. In case a row in bulk csv has more than one validation errors, only the first error detected will be given in the error message field
7. Bulk upload process does NOT stop if an error occurs in validation of a specific row or during processing of a specific row. It proceeds with other rows.
8. Board, Medium, Grade, Subject values are taken from corresponding values of Textbook and populated in all the uploaded content.

Use Case 2: Creation of interactive practice questions and linking to ETBs under program scope

Currently interactive practice questions (MCQs, FTB etc) can be created and published by content editor through work space. We are heading towards program driven content contribution approach where we look forward to create such interactive content under program scope. This use case defines creation, review and linking of interactive contents to textbook under program. User having contribution role for a program can create such content. User having review role for a program can review such content. Upon successful review and acceptance, content shall be published and linked to respective section of textbook. 

Prerequisites:

1. User with contributor rights can contribute to program. She must be given contributor rights explicitly.
2. User with reviewer rights can review the content for a program.
3. Program, scope of the program, Textbooks set up for contribution & valid user creation for contribution and review should have done prior to contribution.
4. Textbook for which contribution is happening , must be in draft state. 
5. A textbook must not be published if it has any of the linked content in draft state. It should through an error mentioning "Kindly publish all the linked content".
6. Once contribution editor is opened under a program, it should only display program scope values for medium, grade and subject.

Overall Process Workflow

The over all workflow process could be broadly viewed in two parts 'contribution' and 'review'. 

User Story 1: Contributor logs in to Diksha & select the textbook for contribution

Main Scenario: User to select the designated textbook for which the contribution has to be made

Exception Scenarios

User Story 2: Select interactive content type from content platter to contribute

Main Scenario: User to select which type of content she wants to contribute. In this case it is interactive content. 

User Story 3: Content creation and send for review

Main Scenario: Contributor creates content in editor, saves it and sends for review

User Story 4: Reviewer logs in to Diksha & select the textbook for review.

Main Scenario: User to select the designated textbook for which the review has to be done.

Exception Scenarios

User Story 5: Review of contributed content

Main Scenario: Reviewer accepts/rejects the content and provide remarks for rejection only.

Alternate Scenario

Exception Scenarios

Localization Requirements

NA

Telemetry Requirements

Non-Functional Requirements

Impact on other Products/Solutions

Key Metrics

Validations