Introduction
One of the important objectives of the system is reuse. Reuse of individual content pieces or collections, across different tenants is already enabled. Content created by any tenant can be accessed by other tenant and can be linked to their ETBs. Further, there can be book publishers who publish ETBs and they get used reused by different tenants. System has to support this to enable further reuse.
The first use case of this is reuse of ETBs published by NCERT by various states. Several states use NCERT textbooks in their curriculum. NCERT has published QR codes in their textbooks and linked digital content. NCERT is also creating and publishing corresponding ETBs on DIKSHA. States using NCERT books will adopt the NCERT ETBs as is.
System should support adoption of NCERT textbook as it is by other tenants (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, wherever it is mentioned as a "State", it includes any other board like CBSE as well.
JTBD
- Jobs To Be Done 1: As a ETB owner of a state, I need to specify one or more NCERT textbooks to be adopted 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 ETBs adopted by my state
Requirement Specifications Specifications
Adopt NCERT Textbooks by a State "as is"
Creation
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.
JIRA Ticket ID
Jira Legacy server System JIRA serverId 2207a759-5bc8-39c5-9cd2-aa9ccc1f65dd key SB-15417
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).
JIRA Ticket ID
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Adopt NCERT Textbooks by a State for more than one medium, grade & subject - Creation (supply side)
The first use case enables a back end mechanism to tag NCERT textbooks to state boards which would make such NCERT textbooks available under state tenant for consumption. To be noted that reused TB is not a new instance of NCERT textbook, rather it is essentially the source book with same do_id. When an NCERT textbook is tagged to state board, it can be searched under state tenant with same Medium, Grade & Subject values for which it has been tagged in NCERT tenant.
However there is a use case where NCERT textbook would be consumed in other mediums that are specific to state tenant. For example, an ETB of English Subject in English Medium under NCERT tenant could be used as English Subject under English Medium as well as Gujarati medium in Gujarat state. Since currently the tagged TB inherit the same MGS combination as of NCERT, it can not be searched and consumed in any other medium under state tenant.
Similar requirements persists for having textbooks to be tagged to more than one grade and subject. Hence we need to enable the tagging of NCERT textbook for more than one medium, grade and subject when a state adopts it.
Overall Workflow
User Story: State to identify NCERT Textbooks to be adopted & to provide required details to implementation team
Srl. No. | User Action | Expected Result |
|---|---|---|
State ETB owner identifies NCERT ETBs to be adopted State ETB owner provides board name, medium, grade and subject details to which these ETBs are to be tagged. Medium, grade and subject values can be more than one. The details are provided to implementation team as a file in following format. https://docs.google.com/spreadsheets/d/1n_R--ub7GYSqvTicfnfgB5rCILm1pgsNfPH2x7Qd_kU/edit#gid=0 | Implementation team runs script inputting the given file. The given list of ETBs will be tagged with the provided Medium, Grade, Subjects in the back end. |
Exception Scenario
Srl. No. | Error / Exception | Expected Handling |
|---|---|---|
Following are possible errors in the data shared by state: Incorrect Textbook Ids Incorrect Board, Medium, Grade, Subject details | Implementation team should will communicate back the errors the request initiator for correction. |
Adopted NCERT textbook consumption for states for more than one medium, grade and subjects - Consumption
Srl. No. | User Action | Expected Result |
|---|---|---|
| DIKSHA App library page: When user selects the state board, medium, grade , subject | The adopted books should be displayed under corresponding mediums, classes and subjects as tagged by adopted textbooks. | |
| DIKSHA App Search and Filter - When a user searches for textbooks and filters on state board, medium, grade , subject | The adopted books should be displayed under corresponding mediums, classes and subjects as tagged by adopted textbooks. | |
| DIKSHA Portal Library page of the State - When user (anonymous or signed in) goes to the library page of state on DIKSHA portal | The adopted textbooks should be shown. | |
| DIKSHA Portal Search and Filter - When a user searches for textbooks and filters on state board, medium, grade, subject. | The adopted books should be displayed under corresponding mediums, classes and subjects as tagged by adopted textbooks. | |
| Whenever a user accesses a state adopted textbook | Meta values should be shown as given by the state. |
Adopt NCERT Textbooks by a State with different name, description and icon for the same TB instance - Creation (supply side)
Certain states adopt NCERT textbooks but by reprinting them with just the change in the textbook name and cover page that are specific to the state. When these states adopt NCERT ETBs as is, the state users will see the NCERT textbook name and icon provided by NCERT. Since they are different from their textbooks, it might lead to confusion.
To avoid this, while adopting NCERT textbooks in system, state should be optionally allowed to provide a different set of metadata values - such as Name, Description, Icon as per the state tenant. However the main body of the textbook (TOC, Linked Contents, Linked QR codes) should not be changed. It should continue to point to the NCERT textbook. Any changes to the textbook body of NCERT textbook should automatically reflect in the state adopted textbook.
When a state adopts an NCERT textbook, the board will be changed to the state board. All other metadata will by default have values of NCERT textbook. Once a textbook is adopted by a state, any change to the metadata of the NCERT textbook will not reflect on the adopted textbook. It will only reflect to consumption experience of adopted textbook in state tenant.
The adoption of NCERT textbook by a state happens as a back end script run by implementation team (NOT Self-Service).
Overall Workflow
User Story: State to identify NCERT Textbooks to be adopted & to provide required details (textbook do ids and different set of meta values) to implementation team
Main Scenario: State to identify and provide NCERT textbooks details like TB do ids (which are to be adopted), state BMGS, Textbook name, Icon, & Description to which these TBs to be tagged.
Srl. No. | User Action | Expected Result |
|---|---|---|
State ETB owner identifies NCERT ETBs to be adopted State ETB owner provides board name, medium, grade and subject details to which these ETBs are to be tagged. Medium, grade and subject values can be more than one. State ETB owner also identifies set of textbooks requiring a different set of name, description, icon and provides state specific values for these textbooks. The data is shared with implementation team in the following file format: https://docs.google.com/spreadsheets/d/1n_R--ub7GYSqvTicfnfgB5rCILm1pgsNfPH2x7Qd_kU/edit#gid=0 | Implementation team runs script inputting the given file. The given list of ETBs will be tagged with the provided Medium, Grade, Subjects in the back end. |
Alternate Scenario:
Srl. No. | User Action | Expected Result |
|---|---|---|
| In case state does not provide meta values. | Default NCERT textbook meta values shall be adopted. | |
Adopt NCERT Textbooks by a State with different name, description and icon for the same TB instance - Creation (supply side)
Srl. No. | User Action | Expected Result |
|---|---|---|
| DIKSHA App library page: When user selects the state board, | The adopted books should be displayed under corresponding mediums, classes and subjects as tagged by adopted textbooks. | |
| DIKSHA App Search and Filter - When a user searches for textbooks and filters on state board | The adopted textbooks should be shown. | |
| DIKSHA Portal Library page of the State - When user (anonymous or signed in) goes to the library page of state on DIKSHA portal | The adopted textbooks should be shown. | |
| DIKSHA Portal Search and Filter - When a user searches for textbooks and filters on state board | The adopted textbooks should be shown. | |
| Whenever a user accesses a state adopted textbook | The name and other metadata should be the shown as given by the state. |
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
Localization Requirements
N/A
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 |
|---|---|---|