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

<Use Case 1 - User Story 1> Overview

<Main Scenario>

<Alternate Scenario 1>

Exception Scenarios

Wireframes

For Future Release

JIRA Ticket ID

<Use Case 1 - User Story 2> Overview

Localization Requirements

Telemetry Requirements

Non-Functional Requirements

Impact on other Products/Solutions

Impact on Existing Users/Data 

Key Metrics