Introduction

This report will provide you the total list of Live contents created or uploaded in that state with the consumption matrixes for those content.   

JTBD

• Jobs To Be Done: As a state admin, I want to have a look at various aspects of the content such as creation 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 content consumption report generates in 3 types, For all these reports the data fields will be the same as bellow.

1. Content Consumption Aggregated metrics till date
2. Content Consumption Metrics for the last 6 weeks
3. Content Consumption Metrics for the last weeks

Key points:

1. Display records for all published content
2. The report will have one record for each content which is in "LIVE" status
3. Explanation of specific fields in the report:
1. [Creation Date]: The date when the content was created first time irrespective of the number of publishing cycles it might have gone
2. [Creator (User Name)]: The user who created or uploaded the content on Diksha
3. [Last Publish Date]: Date of publishing of current Live version
4. [Linked Textbook Id]: Textbook id in which that content is linked. 
5. [Linked Textbook Name]: Name of the textbook for which the content is linked. 
6. [Total Content Downloads]: Number of times the content was downloaded on App.
7. [No. Of Plays (On App and Portal)]: No. of Plays on App + No of Plays on Portal
8. [Content Plays on APP]: The number of times the content was played on App.
9. [Content Plays on Portal]: The number of times the content was played on the Portal.
10. [Average Play Time in mins (On App and Portal)]: Average Play Time in mins on App + Average Play Time in mins on Portal.
11. [Average Play Time in mins on App]: 
12. [Average Play Time in mins on Portal]:
13. [Total No of Ratings]: Number of users rated the content. 
14. [Average Rating (Out of 5)]: The overall average rating rated for that content by the users.    
15. [End Date of the Week]:  
4. This will have all the contents sorted by State, Board, Medium, Class, Subject.
5. This report is generated based on the state tenant.
6. This report should be updated on a weekly basis.
7. Last updated on Field should be shown on the top in the "content consumption metric for the last 6 weeks" report.
8. This report will have only 1 table, No graphs are shown.
9. In the table, the overall "Content Consumption Aggregated metrics till date" will be shown and there will be 3 download buttons on the top, One is for "content consumption Aggregated metrics till date" and followed by the other two reports.
10.  No table view for  "Content Consumption Metrics for the last 6 weeks" and "Content Consumption Metrics for the last weeks", Only Download CSV option.
11. Whenever the report is updated in portal the Last "updated on" field should show that date.
12. In the portal, This report should be shown below the "Daily Usage " Report.
13. When the report is downloaded the file name should be as follows 
    1. Content aggregated metrics:- content_aggregated
    2. Content Consumption Metrics for the last 6 weeks:- content_consumption
    3. Content Consumption Metrics for the last weeks:- content_consumption_lastweek

Sample Report

1. Content Consumption Aggregated metrics till date

https://docs.google.com/spreadsheets/d/1tMDUwDjwD-6x3U4Fmiu1CEQeBOIyL1em2R3lQIEOT8k/edit?usp=sharing

2. Content Consumption Metrics for the last 6 weeks

3. Content Consumption Metrics for the last weeks

https://docs.google.com/spreadsheets/d/1a_QlkFdBuGJYXkB0JjtljUs6I6GFmRyhPQFVEXKqWRs/edit#gid=1530612835

Wireframes

JIRA Ticket ID

SB-13557 - Getting issue details... STATUS SB-17458 - Getting issue details... STATUS SB-17609 - Getting issue details... STATUS

Title and the Description

Title: Content Consumption Report

Report Description: This report provides details about all content that are published and their consumption statistics. The details are specific to each state and is updated on a weekly basis.

Localization Requirements

N/A

Telemetry Requirements

Non-Functional Requirements

Impact on other Products/Solutions

N/A

Impact on Existing Users/Data 

N/A

Key Metrics