Introduction

Diksha is engaging with NCERT, as result a business requirement has evolved to on board NCERT as tenant on DIKSHA and subsequently other states can reuse the published NCERT textbooks. 

System should support reuse of NCERT textbook as it is by other boards (State Boards or CBSE). They can reuse textbooks as is, along with TOC, QR codes & contents linked to it. However, they should not be allowed to make any changes to the book as reused TB is not a new instance of NCERT textbook. 

In this document, where ever it is mentioned as a "State", it includes any other board like CBSE as well.

JTBD

• Jobs To Be Done 1: As a textbook creator of a state, I want to reuse one or more NCERT textbooks as is in my state and want it to open for state user consumption.
• Jobs to be Done 2 - As a user of a state, I want to consume NCERT textbooks content reused in my state

Requirement Specifications

Tag Textbooks for Reuse by a State

This flow describes how a state can specify the list of textbooks that they would like to reuse as it is. Currently this can happen only through a back end script/

• Once NCERT is onboarded, framework assigned, content/textbooks & QR codes are imported, linked and published, its textbooks can be reused by other state.
• State specifies list of NCERT textbooks it wants to reuse in a csv (with columns: Medium, Grade, Subject, TB Name, do_id) along with details of state and textbook creator's credentials.
• Back-end team will upload the information and the textbooks will be tagged as reused by the state with state's board tagged to it. To reiterate, reused TB is not a new instance of NCERT textbook, rather it is essentially the source book with same do_id.

Consumption

Once one or more NCERT textbooks are tagged for reuse by a state, there are following ways to consume the content:

Scan QR code from NCERT textbook (from DIKSHA App)

Display linked content to the QR code. Once user plays the content and comes back to Library page, in case Board is not set, display a popup that asks user to select the Board.

User selects the states's board and goes to library page (from DIKSHA App)

Display the NCERT textbooks reused by the state along with any other textbooks created by the state.

Enter NCERT QR code on DIKSHA portal 

Display linked content to the QR code.

Access NCERT DIKSHA page and explore content (diksha.gov.in/ncert/explore).

View NCERT textbooks and content first before viewing other content

Search textbooks and filter by the state's Board

Show up NCERT textbooks reused by the state.

User opens explore page from the state's DIKSHA page on portal

The imported NCERT textbooks are shown along with any other textbooks created by the state first (sort order).

Exception Scenarios

Wireframes

N/A. There are no UI changes.

For Future Release

Tag Textbooks for Reuse through Portal  <To be taken up in JFM>

Tag Textbooks for Reuse 

• States are to be facilitated for reusing the entire NCERT textbook as it is.
• An option can be provided under workspace for the same called "Reuse Textbook". Upon clicking on it, user should be redirected to a page to search the textbooks to be reused.
• TB creator should be able to search the textbooks tagged for "Medium", "Grade", "Subject" and "Published By" (published by field which has the state name).
• The list of values to be shown in “Published By” can be configured at DIKSHA level. To start with, only NCERT to be configured.
• Upon providing the search parameters and clicking on "Search", a list of textbooks should render with following fields - Textbook Name, Medium, Grade, Subject, Published By
• There should be a check box for each textbook row, also there should be an "Reuse" button
• User should be able select single or multiple check boxes (for textbooks) and upon clicking on "Reuse", all such selected textbooks should be reused in state.
• In case there are many textbooks falling under search criteria, appropriate pagination should be enabled
• Once NCERT textbooks are reused by a state, they are tagged to that state's board and searching textbooks using the state board should show up the reused textbooks. When NCERT textbooks are deleted, the tagging should be removed.

Viewing Reused Textbooks

• There should be an option , "Delete Textbooks" for the TB creator to view the previously reused textbooks. This option can be provided on the same landing page which is rendered when user clicks on "Reuse Textbook" from work pace
• User should be able to filter reused textbooks on the basis of -  "Medium", "Grade", "Subject" and "Published By" (published by field which has the state name).
• Textbook list should appear with following fields - Textbook Name, Medium, Grade, Subject, Published By
• User can just view these TBs but cannot make any changes at all.
• However TB creator should be provided an option to delete such TBs at any point of time as required.
• Again the list should appear with checkbox for each textbook row.
• There should be a button called "Delete"
• User should be able to select textbooks from checkbox and if clicks on "Delete", all such textbooks should be deleted from state.
• In case number of textbooks rendered are too many, Appropriate pagination should be enabled

Reports (<in JFM'20>)

Reports can be populated across following parameters:

• Scans
• Plays
• Downloads

Above parameters will be counted on the basis of Geographical location (or user profile details) of the users/device. 

Following reports shall be populated:

• Daily Usage Metrics
• QR code status
• ETB creation status

Parameters for above reports will remain same as per current reports. There will be no district level reporting.

For counting the report numbers following points should be considered:

• When NCERT textbook is only used in NCERT means there is no reuse of such TBs. In this case any activity (for scan, play or download) will increase numbers for NCERT only.
• When NCERT textbook is reused by another state and the consumption (scan, play, download) is done by that state user only. The consumption is attributed to a state when the device location is from the state

JIRA Ticket ID

Localization Requirements

N/A

Telemetry Requirements

Non-Functional Requirements

Impact on other Products/Solutions

Impact on Existing Users/Data 

Key Metrics