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: SB-16761 - Getting issue details... STATUS ). As long as mentioned story is not implemented, it can also 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. 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".

Overall Process Workflow

User Story 1: User access 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 2: User selects bulk upload option

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

Alternate Scenario:

Exception Scenarios

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

Main Scenario: Valid user having content contributor and reviewer rights for a program populate the sample file and upload 

Alternate Scenario:

Exception Scenarios

User Story 4: Rectification of validation errors and upload again

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

Exception Scenarios

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

Localization Requirements

NA

Telemetry Requirements

Non-Functional Requirements

Impact on other Products/Solutions

Impact on Existing Users/Data 

Key Metrics

Overall Exception Scenarios

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.  

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 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 2: Overall Process Workflow

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

Use Case 2 - 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

Use Case 2 - 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. 

Use Case 2 - User Story 3: Content creation and send for review

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

Use Case 2 - 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

Use Case 2 - User Story 5: 

Main Scenario: 

Alternate Scenario:

Exception Scenarios

Localization Requirements

NA

Telemetry Requirements

Non-Functional Requirements

Impact on other Products/Solutions

Key Metrics

Validations