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


Introduction

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

JTBD

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

Requirement Specifications

Reusing NCERT Textbooks 

For other states, we need to facilitate the reutilization of NCERT textbook as it is. State should be able to reuse the textbook 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, rather it is essentially the source book with same do_id. It is just an extension for the consumption of the actual NCERT TB to state audience.

There are three areas to look for reusing textbook:

1. Textbook Creation

Textbook Creation Process (From Backend)

  • Once NCERT is onboarded, framework assigned, content/textbooks & QR codes are imported, linked and published, its textbooks can be reused by other state.
  • In current scheme of things NCERT textbooks shall be reused for a state from backend only. (However in JFM user driven process on Diksha shall be enabled)
  • State required to specify which NCERT textbooks it wants to reuse (TB details can be provided as - TB name, do_id, Medium, grade, subject) along with state textbook creators credentials.  
  • Backend team should be able to reuse NCERT text book in requesting state's tenant however this TB would have the same do id as of NCERT. To reiterate, reused TB is not a new instance of NCERT textbook, rather it is essentially the source book with same do_id. It is just an extension for the consumption of the actual NCERT TB to state audience.

2. Textbook Consumption

Once NCERT TBs are reused by a tenant, there are following ways to consume the content:

  • Scan QR code from NCERT textbook (from Diksha App), need to display linked content
  • Display linked content if user enter NCERT QR code on Diksha portal 
  • User reaches out to NCERT Diksha page and explore content (Diksha.gov.in/ncert/explore). User should view NCERT textbooks and content first before viewing other content
  • Searching content without a board should show up content from all the boards and NCERT. Down the line , we also need to enable the search based on "Publisher".
  • No user should see NCERT textbook in library page in mobile app by default unless that state has imported the NCERT textbooks and have been readied for consumption. 
  • In mobile, when a user selects the board (which has imported NCERT TBs) and goes to the library page, it should display the imported NCERT textbooks there.
  • In portal, when a user opens explore page from the state’s DIKSHA page, the imported NCERT textbooks are shown first (sort order).

3. 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 tenant means there is no reuse of such TBs. In this case any activity (for scan, play or download) will increase numbers for NCERT tenant 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


<User Story> <To be taken up in JFM>

Textbook Creation Process (On Diksha) < IN JFM>

  • 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 tenant 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 tenant
  • In case there are many textbooks falling under search criteria, appropriate pagination should be enabled
  • Once NCERT textbooks are reused by a tenant, they are tagged to that tenant’s board and searching textbooks using the tenant board should show up the reused textbooks. When NCERT textbooks are deleted, the tagging should be removed.

Viewing Imported Textbooks <In JFM>

  • 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 tenant 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 tenant.
  • In case number of textbooks rendered are too many, Appropriate pagination should be enabled


<Main Scenario>

Srl. No.User ActionExpected Result






<Alternate Scenario 1>

Srl. No.User ActionExpected Result






Exception Scenarios

Srl. No.Error / ExceptionExpected Handling






Wireframes

For Future Release

JIRA Ticket ID

<Use Case 1 - User Story 2> Overview

Localization Requirements

UI ElementDescriptionLanguage(s)/ Locales Required



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