Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 30 Next »


Introduction

One of the themes of ETB is enabling multiple states and boards across the system to adopt and reuse ETBs published by a publisher.

NCERT is publishes books. They also have QR codes printed and digital content linked to it. NCERT is creating corresponding ETBs on DIKSHA. Many states use the NCERT books as is in their curriculum. All those states can potentially reuse the same ETBs. This document details various use cases of states adopting and reusing NCERT ETBs.. 

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

Adopt NCERT Textbooks by a State "as is"

This use case details the requirements of states being able to adopt Live NCERT ETBs, "as is" without any modifications to its metadata, ToC, QR codes and linked content.

States are not allowed to make any changes. Same instance of ETB is used by the states and hence any changes to the NCERT ETB should automatically get reflected to all the states adopting it.

Creation (non self-service)

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

SB-15417 - Getting issue details... STATUS

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

SB-15418 - Getting issue details... STATUS


Adopt NCERT Textbooks by a State "as is" for more than one medium

The first use case, Adopt NCERT Textbooks by a State "as is" - details requirements of states adopting the NCERT ETBs as it is without any changes.

However there is a use case where NCERT ETB would be used by teachers and students of a different medium of a state. For example an ETB of Class 7, English Subject in English Medium of NCERT could be used as English Subject ETB in both English Medium and Gujarati Medium Class 7 in Gujarat. In this case, when a teacher or student from Gujarat Board, Class 7, Gujarati Medium (with these values set in their her) access Library page in Mobile App, she should see the adopted NCERT ETB under English Subject. The same should work when someone searchers and filters ETBs by Gujarat Board, Class 7, Gujarati Medium.

User Story 1: State to identify NCERT Textbooks to be adopted & to provide required details to implementation team

Main Scenario: State to identify and provide NCERT textbooks details like TB do ids (which are to be adopted), state board name, mediums, Grades & subjects to which these TBs to be tagged. 

Srl. No.
User Action
Expected Result

State user identifies NCERT textbooks to be adoptedState user to provide do ids of such textbooks

State user provides board name, medium, grade and subject details to which these textbooks are to be tagged. Medium, grade and subject values can be more than one. 

Textbook do ids, state board, mediums, grades and subjects details to be sent to implementation team in following format.

https://docs.google.com/spreadsheets/d/1n_R--ub7GYSqvTicfnfgB5rCILm1pgsNfPH2x7Qd_kU/edit#gid=0

User Story 2: Implementation team to tag the NCERT textbooks to the required B, M,G, S as per details provided by state.

Main Scenario: On the basis of input provided by the state, Implementation team will tag such textbooks to state B,M,G,S.

Srl. No.
User Action
Expected Result

Implementation team will tag NCERT textbooks to state B,M,G,S (M,G,S can be more than one) from back end as per input provided Such tagged NCERT textbooks should be visible for all consumption scenarios for state.



Exception Scenarios

Srl. No.
Error / Exception
Expected Handling

In case state provides wrong/invalid NCERT textbook do idsImplementation team should identify and communicate this to state

In case state provides wrong/invalid board detailsImplementation team should identify and communicate this to state

In case state provides wrong/invalid medium detailsImplementation team should identify and communicate this to state

In case state provides wrong/invalid grade detailsImplementation team should identify and communicate this to state

In case state provides wrong/invalid subject detailsImplementation team should identify and communicate this to state

Consumption

User Story 1: Adopted NCERT textbook consumption for states for more than one medium, grade and subjects

Main Scenario: When a state adopts NCERT textbooks by for more than one mediums , grades and subjects the adopted textbooks should be available for state uses for all these values.

Srl. No.
User Action
Expected Result

DIKSHA App library page: When user selects the state board, medium, grade , subjectThe 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 , subjectThe 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 portalThe 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 "as is" with different meta values for the same TB instance.

NCERT as a tenant has been onboarded on Diksha. There is a requirement to allow states to use NCERT textbooks to be consumed (as it is) under state tenants. To facilitate that, a backend mechanism has been enabled 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 the same do_id.

Once an NCERT textbook is tagged to the state board, it can be searched and consumed under state tenant. User would see TB name, icon and other meta values as per NCERT since it is the same instance. In the physical world, there is a scenario where a state reprints NCERT textbooks by changing the textbook name and cover (icon) that are specific to the state. But in the system, since the textbook will continue to show name and icon of the NCERT textbook, it will confuse end users. 

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.

Creation

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 1: 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 user identifies NCERT textbooks to be adoptedState user to provide do ids of such textbooks

State user identifies different set of meta values for which these textbooks are to be adopted. 

State provides following details to implementation team for each textbook:

  1. State board
  2. Mediums (Can be more than one)
  3. Grade (Can be more than one)
  4. Subject (Can be more than one)
  5. Textbook name
  6. Textbook description
  7. Textbook Icon

in following format: https://docs.google.com/spreadsheets/d/1n_R--ub7GYSqvTicfnfgB5rCILm1pgsNfPH2x7Qd_kU/edit#gid=0

Alternate Scenario:

Srl. No.
User Action
Expected Result

In case state does not provide meta values. 

Default NCERT textbook meta values shall be adopted.




User Story 2: Implementation team to tag the NCERT textbooks to the state board with different set of meta values as provided by the state

Main Scenario: On the basis of  meta values provided by the state, Implementation team will tag such textbooks to state board. 

Srl. No.
User Action
Expected Result

Implementation team will tag NCERT textbooks to state board with different set of meta values as provided by the state.Such tagged NCERT textbooks should be visible for all consumption scenarios for state.



Consumption

User Story 1: Adopted NCERT textbook consumption for states 

Main Scenario: When a state adopts NCERT textbooks by changing the metadata, the adopted textbooks should be available for state uses.

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 boardThe 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 portalThe adopted textbooks should be shown.

DIKSHA Portal Search and Filter - When a user searches for textbooks and filters on state boardThe 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.

Validations

.
Error / Exception
Expected Handling

While adopting NCERT textbook for different set of meta values, the main body body of the textbook (TOC, Linked Contents, Linked QR codes) gets changed.

The main body of the textbook (TOC, Linked Contents, Linked QR codes)  should not be changed.


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




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 NameDescriptionPurpose

Non-Functional Requirements

Performance / Responsiveness RequirementsLoad/Volume RequirementsSecurity / Privacy Requirements



Impact on other Products/Solutions

Product/Solution ImpactedImpact Description


Impact on Existing Users/Data 

User/Data ImpactedImpact Description


Key Metrics

Srl. No.MetricPurpose of Metric




  • No labels