Introduction

Many of the states working on ETB program have a lot of exiting content in the form of videos or pdfs. They prefer to reuse it for linking to the QR codes in their textbooks. This greatly reduces effort and time required in finding content for ETB. It also enables reuse of existing curated and quality content for ETB. This story details enabling of bulk upload of existing content by states through online portal.

JTBD

• Jobs To Be Done: Uploading existing content one by one manually is an intensive effort and time taking. Hence they prefer bulk uploading of the content on to the system. Currently this is being supported by implementation team. However with 28 states on-boarding, and the bulk upload process happening in multiple iterations, it becomes a significant effort for implementation team to handle this. Hence there is a high value in enabling this process through online portal so that each state can do this through their resources. There is no requirement of a detailed review process for this content as it would have already happened. Hence review of this on system before publishing is only a formal verification.
• User Personas: State resources who own the process of content pooling for ETBs are the primary users of this system. These are typically an identified set of teachers who collate existing content and map them to the state textbooks. 
• System or Environment: Desktops with Chrome browser and possibly MS office for working with excel. Network connectivity can be assumed but with lower bandwidth (1 mbps)

Requirement Specifications

Bulk Upload of Content - Overview

In order to ensure effective scale rollout of ETB and associated programs across states, it is critical to make states self-reliant to execute most of the ETB activities themselves. One of the major activity for which state is dependent on Diksha implementation team is bulk content upload. In this PRD we are going explain process, workflow and upload format for bulk data upload on Diksha by states.

Actor: Only Content Reviewer can execute this use case flow

Bulk Upload of Content - Overall Process Workflow

Bulk Upload of Content  - User Story

Main Scenario: Upload and Publish Content and Link it to Textbook

This scenario is uploading content, publishing it as well as linking the content to relevant textbook sections based on the QR code. The pre-requisite for this:

1. The textbook to which content is linked should be in draft state and QR codes are mapped to relevant textbook sections
2. The Bulk Upload CSV has mapping of QR code and Textbook id for each content

Actions:

1. Content reviewer access Diksha link
2. Reach out to Workspace. There should be a new option called: "Bulk Content Upload". Under this, there will be two options:
1. Upload csv file: To start bulk upload.
2. Last upload file: This should display the upload status of the last upload. For the first time it would not be there since there is no previous bulk upload.
3. Download the sample upload file from the link below the upload option (refer screen). Format of the bulk upload sheet is as follows: https://docs.google.com/spreadsheets/d/1zo_KVAU3y_RR3p4Gpgud-geROZYXv9Efpgwdflszemc/edit#gid=0
4. User should be able to access user guide from the link below the upload option (Refer screens).
5. User populates the bulk upload sheet in the required format.
6. Select "Upload csv file".
7. By default, "Publish & Link to Textbook" radio button would be selected as upload type. Upload options are:
1. Publish : Content created and published.
2. Publish & Link to Textbook: Content created, published and linked to the respective textbooks as provided in bulk upload sheet. By default, this radio button is selected.
8. Browse the populated bulk upload file. Click on "Start Upload".
9. In case file contains validation errors, error dialogue should appear with listed validation errors (Refer wire frames). User should rectify and upload again.
10. In case there is no validation error, upload should start and user should be redirected to Work space screen.
11. While upload is in progress, "Upload csv file" should be disabled for next upload.
12. At the same time, clicking on "View Report", should take user to bulk upload status dialogue box, where user should see following fields:
1. Start Time
2. End Time
3. Total number of content
4. Content successfully processed
5. Content failed
6. Link to download status report "Download Report"
13. Status report would have following additional fields (apart from input bulk sheet fields) for each row (representing each content)
1. Upload Status: Success, Fail
2. Content Do_Id: If success, than do id of the created content
3. Reason of Failure:  If fail, than reason of failure. In case there are multiple reasons for failure, display each of them by numbering them in the same cell for each row.
14. Once upload is complete,  "Upload csv file" button will be enabled. Now user can start a new upload.
15. There will be two complete status, would be rendered depending upon contents upload status:

    1. Completed : When there is no content failure in status report 

    2. Completed with errors : When there are content which got failed because of some error. In this case user to check the details and download status report.

16. Till the new upload is started, "Last upload file" will show the status of previous upload.
17. User would be required to rectify the reason of failure and upload the failed content again.

Alternate Scenario 1: Publish Content (no linking to textbook)

This scenario is uploading content and publishing it only.

Actions:

In this scenario all the actions are similar as for the main scenario, just a difference that in step 7, while uploading bulk upload input sheet, user select bulk upload type as "Publish" from the radio button. In this case, content is created and published on Diksha.

Exception Scenarios

Prerequisite:

1. Before any validation/processing, space trimming should be done for preceding and trailing value of each cell.
2. Validation must be done before the content creation for each row. For example system should read the entire row, in case any mandatory cell value is missing, fail the content creation for that row and display with error message in status report.  

Wireframes

https://docs.google.com/presentation/d/1Qd-2AruRDSPS6pjdSTuUt-oZt6w0bBfnE_ZpYW3gWdQ/edit#slide=id.g5bde35cc17_0_0 

Invision Link: https://projects.invisionapp.com/share/7QST139948N#/screens/374220905 

For Future Release

NA

JIRA Ticket ID

SB-12164 - Getting issue details... STATUS

Localization Requirements

NA

Telemetry Requirements

Non-Functional Requirements

Impact on other Products/Solutions

NA

Impact on Existing Users/Data 

NA

Key Metrics