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

Instructions to use this template:

  1. Use this template to write the Product Requirements Document (PRD) for a single User JTBD or Initiative. 
  2. Each workflow within the PRD will correspond to an Epic in JIRA. Each User Story will correspond to a Story in JIRA that will be part of the Epic.
  3. Each section in the template has instructions, with examples explaining the type of content to be written in that section. 
  4. You may start typing into the section by eliminating the instructional text, or delete the instructional text after you have entered all content for the section.
  5. Repeat from section <Use Case 1> Overview for every use case in the User JTBD or Initiative

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

Context:

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

Detailed Process Flow:

  • Content reviewer access Diksha link
  • Reach out to Workspace. There should be a new option called: "Bulk Resource Upload". Under this, there will be two options:
    • Start Bulk Upload: To start bulk upload.
    • Bulk Upload Status: This should display the upload status of the last upload. For the first time when there is no previous bulk upload, this button would remain disabled or upon click should display a message "There is no previous bulk upload".
  • For new bulk upload, user should click on "Start Bulk Upload"
  • Download the sample upload file from the dialogue box appeared. Format of the bulk upload sheet is as follows: https://docs.google.com/spreadsheets/d/1zo_KVAU3y_RR3p4Gpgud-geROZYXv9Efpgwdflszemc/edit#gid=0
  • User should be able to access user guide form the dialogue box appeared (Refer wireframes).
  • User populates the bulk upload sheet in the required format.
  • Again select "Start Bulk Upload".
  • Select bulk upload type from the drop down. Permissible values are:
    • Create:  Content created and sit in draft stage.
    • Create & Publish : Content created and published.
    • Create, Publish & Link to Textbook: Content created, published and linked to the respective textbooks as provided in bulk upload sheet.
  • Browse the populated bulk upload file. Click on "Upload".
  • In case file contains validation errors, error dialogue should appear with listed validation errors (Refer wireframes). User should rectify and upload again.
  • In case there is no validation error, upload should start and user should be redirected to Workspace screen.
  • While upload is in progress, "Start Bulk Upload" should be renamed to "Bulk Upload in Progress" and it should be disabled for next upload.
  • At the same time, clicking on "Bulk Upload Status", should take user to bulk upload status dialogue box, where user should see following fields:
    • Start Time
    • End Time
    • Total number of content
    • Content successfully processed
    • Content failed
    • Link to download status report "Download Status Report"
  • Status report would have following additional fields (apart from input bulk sheet fields) for each row (representing each content)
    • Upload Status: Success, Fail
    • Content Do_Id: If success, than do id of the created content
    • Reason of Failure:  If fail, than reason of failure
  • Once upload is complete,  "Bulk Upload in Progress" would again change to "Start Bulk Upload". Now user can start a new upload.
  • Till the new upload is started, "Bulk Upload Status" will show the status of previous upload.
  • User would be required to rectify the reason of failure and upload the failed content again.


Validations at the time of bulk sheet upload (Results in Validation Errors):

  • In case any mandatory column is missing, validation error should be thrown
  • Although "QR code" & "Textbook id" fields are not mandatory but in case user selects upload type as "Create, Publish & Link to Textbook", than these fields becomes mandatory and validation error should be thrown in case these columns are missing


Validations while processing each row for creating each content (Results in Content Failure):

  • Validation regarding mandatory fields should be checked while processing each row, in case cell value is missing fail that content
  • Validation regarding size and permissible data format should be checked for each field of each row, if not complied, fail the content creation

<Use Case 1> Overview

<Use Case 1 Overall Process Workflow>



<Use Case 1 - User Story 1> Overview

<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