Introduction
This report provides details of Diksha usage in terms of QR code Scans, Content Downloads, and Content Play. All the graphs show the usage status per day. This report is updated every day. The particular state can view only their state report in Diksha.
JTBD
- Jobs To Be Done: As a state admin, I want to have a look at various aspects of ETB such as consumption failures, etc.
- User Personas: The logged in users who have State Admin role, report viewer role can access this report.
- System or Environment: works on for desktops with Chrome browser only.
Requirement Specifications
This report will have 2 fields i.e; graph and Table. Below are the details
- Graphs
- QR Code Scans per day: This graph shows total no of QR code scans, per day.
- % Failed QR code scans per day: This graph shows the percentage of faild QR code scans, per day.
- Content Download per day: This graph shows the total number of content downloaded (from app), per day.
- Content Plays (Portal and APP) per day: This graph shows the total no of times contents are played (on Portal and App), per day.
- Hours of content played per day: This graph shows the total number of hours for which content are played (on Portal and App), per day.
- Table
Date | Total QR Scans | Successful QR Scans | Failed Scans | Percentage (%) of Failed QR Scans | Total Content Downloads | Total Content Plays on App | Total Devices that played content on App | Content Play Time on App (in hours) | Total Content Plays on Portal | Content Play Time on Portal (in hours) | Total Content Plays | Total Content Play Time (in hours) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
Description: This report provides details of Diksha usage in terms of QR code Scans, Content Downloads, and Content Play, All the graphs show usage status per day. This report is updated every day.
Data Fields
Date: Date when data is captured.
Total QR Scans: Total number of scans for the particular day
Logic: Total no. of scans done on QR codes which are linked to that state-specific books
Successful QR Scans: Total number of scans which rendered content successfully upon scan
Logic: QR code is present in ETB and has content linked which is linked to that state-specific book.
Failed Scans: Total number of scans for which the user did not get any linked content
Logic: For state-specific book, if the QR Code is present in the ETB but no contents are linked. Those QR codes scans are considered as failed scans
Percentage (%) of Failed QR Scans: Percentage of failed scans
Logic: Failed / Total
Total Content Downloads: Total number of content downloaded on a specific day
Logic: This value should be calculated based on the content downloads of state-specific QR code scans or Directly from the state-specific ETB.
Total number of Content Plays on App: Total number of content played on the App which includes both online contents play and downloaded content plays.
Logic: Total no of content played either through QR code scans or Directly from the ETB in that state.
Total unique devices that played content on App: Overall in how many devices did the content has been played.
Logic: unique count of devices which played the content in that state on the app.
Total number of hours Content Play Time on App (in hours):
Logic: Total time spent on the content in that state either through QR code scans or directly from ETB
The total number of Contents Play on Portal: Total number of content played on the portal
Logic: Total number of content which is linked to the ETB or from the QR code played on that day from that state.
Total Unique devices that played content on Portal: Overall in how many devices did the content has been played.
Logic: unique count of devices which played the content in that state on the portal.
Total number of hours Content Play Time on Portal (in hours):
Logic: Total time spent on the content in that state which is linked to the ETB
Total number of Content Plays: Total no of content played both on App and the Portal
Logic: Total Content Plays on App + Total Content Plays on Portal.
Total number of hours of Content Play Time including both app and portal (in hours):
Logic: Content Play Time on App (in hours) + Content Play Time on Portal (in hours).
Note:
- The report should be generated on a daily basis with the previous day data.
- In this report, all the values should be generated based on QR code scans or ETB which are linked to that specific state.
JIRA Ticket ID
Localization Requirements
| UI Element | Description | Language(s)/ Locales Required |
|---|---|---|
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 |
|---|---|
0 Comments