Content Sourcing of ETB is the step of ETB process where states pool existing content from various sources or create new content relevant to the textbooks that are part of their ETB program scope.
Following are the different ways content is sourced for ETB:
However this content sourcing process is not textbook driven. The content is uploaded/created, reviewed and published outside the scope of ETB. Once published, they are linked to the relevant textbooks. This results in multiple issues:
To solve the above problems, the solution is to enable content contributors to contribute content (upload existing or create new) based on Textbooks under program scope. This process has been enabled as an experiment for CBSE. The same has to be enabled for all the states.
Use this section to elaborate on:
Pre-requisites:
Contribution can be done either by contributing content to respective node of the textbook or through bulk upload.
Bulk upload option shall be available for a textbook under program. Bulk upload will be done only for a textbook at a time. A new role "Bulk content publisher" will be created in the system and a user with that role can only do Bulk upload and publishing of content. Textbook for which the bulk upload is being done must be in draft state. Multiple bulk upload can be done for a textbook, but not at the same time. Upon successful upload, content would be created, published and linked to relevant section of the textbook as mentioned in bulk upload file.
System will enable a new role called "Bulk Content Publisher". A user with this role can perform the following actions:
Srl. No. | User Action | Expected Result |
---|---|---|
1 | User enters Diksha URL | Diksha page opens with sign in option. |
2 | User enters valid credentials | User sign in and land on tenant home page |
3 | User clicks on "Contribute" | Program list page opens which has all the programs created for the state. |
4 | User selects required program | User lands on the textbook page. Page has all the books displayed under program scope. |
5 | User selects the required textbook | Textbook TOC page opens which has contribution options both either to contribute at each node. There is also "Bulk Upload Content" option. |
Srl. No. | Error / Exception | Expected Handling |
---|---|---|
1 | User does not have any role assigned in the program | The program is not displayed in the list of Programs in the Program list page |
Srl. No. | User Action | Expected Result |
---|---|---|
1 | In Textbook detail page, user clicks on "Bulk Upload Content" | Dialog box opens with following options "Upload File" - The option is enabled for user to upload file "Download Sample File" - The option is enabled for user to download sample file "Start Bulk Upload" - This option will be disabled by default. It will be enabled only once a bulk csv file is uploaded. "Close" - The option is enabled for user close the bulk upload dialog |
Srl. No. | User Action | Expected Result |
---|---|---|
1 | In Textbook detail page, user clicks on "Bulk Upload Content" | Dialog box opens with following options "Upload File" - The option is enabled for user to upload bulk csv file "Download Sample File" - The option is enabled for user to download sample file "Last Upload Status" - Shows status of previous bulk upload process with following fields:
"Start Bulk Upload" - This option will be disabled by default. It will be enabled only once a bulk csv file is uploaded. "Close" - The option is enabled for user close the bulk upload dialog |
Srl. No. | User Action | Expected Result |
---|---|---|
1 | In Textbook detail page, user clicks on "Bulk Upload Content" | Dialog box opens with following options "Upload File" - The option is disabled, and user cannot upload file "Download Sample File" - The option is enabled for user to download sample file "Last Upload Status" - Shows status of previous bulk upload process with following fields:
"Start Bulk Upload" - This option will be disabled by default. It will be enabled only once a bulk csv file is uploaded. "Close" - The option is enabled for user close the bulk upload dialog |
Srl. No. | Error / Exception | Expected Handling |
---|---|---|
1 | If user has only contribution rights but does not have "Bulk Content Publisher" role in the program. | Bulk upload option shall not be available for such users on textbook level. They can only contribute content one by one for respective node. |
Srl. No. | User Action | Expected Result |
---|---|---|
1 | User selects "Upload File" option | File browser dialog opens for user to browse and select and bulk csv from her local system |
2 | User browses selects bulk upload file from local system | ."Start Bulk Upload" button is enabled |
3 | User clicks on "Start Bulk Upload" | System validates the bulk csv is required format and upload process is started Last Upload Status will show the status as In Progress and other fields are updated. Once Bulk Upload is completed successfully, all the contents are published and linked to the textbook for the respective sections as given in the bulk csv file. |
Srl. No. | User Action | Expected Result |
---|---|---|
1 | In Textbook detail page, user clicks on "Bulk Upload Content" | Dialogue box opens with option "Download Sample File" |
2 | User clicks on "Download Sample File" option in dialogue box | Sample file gets downloaded Link to sample file: https://docs.google.com/spreadsheets/d/1zo_KVAU3y_RR3p4Gpgud-geROZYXv9Efpgwdflszemc/edit#gid=0 |
Srl. No. | Error / Exception | Expected Handling |
---|---|---|
1 | In case file format contains errors that are detected before starting of upload process | Bulk Upload dialogue shows the list of validation errors (Refer validation error section in the last of this PRD for detail). The process is not started. User corrects the errors in the bulk csv file and click on the "Upload File" option again. User browses and selects the correct bulk csv. The main flow of this story executes. |
Srl. No. | User Action | Expected Result |
---|---|---|
1 | User upload correct bulk upload csv and starts Bulk Upload process. | Bulk upload process starts |
2 | While upload is in progress user views the details in "Last Upload Status" section. |
The above status has to be refreshed every 60 secs. |
Srl. No. | User Action | Expected Result |
---|---|---|
1 | User clicks on "Download Report" option in Last Upload Status section of Bulk Upload Dialog | 1. Once upload is complete, "Upload csv file" button will be enabled. Now user can start a new upload. 2.Status: There will be two types of complete status
3.Till the new upload is started, "Last Upload Status" will show the status of previous upload. Note: If the bulk csv contains a content that was already created previously, it will be considered as an error with reason as "Duplicate Content". Hence in such scenario, the status will show "Completed with errors". |
Srl. No. | User Action | Expected Result |
---|---|---|
1 | User opens Bulk Upload Dialog where the last bulk upload process is complete |
|
Srl. No. | Error / Exception | Expected Handling |
---|---|---|
1 | Bulk Upload process takes more than 24 hours to complete | The upload process is aborted. Last Upload Status section will have following values
|
Wire frame link: https://projects.invisionapp.com/share/7QST139948N#/screens/374220905
There are no localization requirements for UI. UI is only in English.
However, the Bulk Upload CSV should support values in Indian languages for fields like - Content Name, Description, Textbook Level names, Topics, Keywords etc - where the fields can be in Indian languages. The values are expected to be in Unicode.
Event Name | Description |
---|---|
Click on button "Bulk Upload" option in Textbook ToC page | Parameters to be captured for this events are: Time stamp, user id, tenant id, textbook id, program id |
Click on "Start Upload" option in Bulk Upload dialog | Parameters to be captured for this events are: Time stamp, user id, tenant id, textbook id, program id |
Download of sample template file option in Bulk Upload dialog | Parameters to be captured for this events are: Time stamp, user id, tenant id, textbook id, program id |
Click on "Close" button in Bulk Upload dialog | Parameters to be captured for this events are: Time stamp, user id, tenant id, textbook id, program id |
Download of "Status Report" button in Bulk Upload dialog | Parameters to be captured for this events are: Time stamp, user id, tenant id, textbook id, program id |
Click on "Last Uploaded File" | Parameters to be captured for this events are: Time stamp, user id, tenant id, textbook id, program id |
Start of Bulk Upload Process in the back-end | Parameters to be captured for this events are: Time stamp, user id, tenant id, textbook id, program id, number of contents, unique process id |
End of Bulk Upload Process in the back-end | Parameters to be captured for this events are: Time stamp, user id, tenant id, textbook id, program id, number of contents, unique process id, status (completed successfully, completed with errors, aborted) |
Performance / Responsiveness Requirements | Load/Volume Requirements | Security / Privacy Requirements |
---|---|---|
Maximum expected time for bulk upload process to complete - 8 hours. 9.6 seconds per content. | A bulk csv file can have maximum 1000 contents | N/A |
Time to complete creation, publish and linking one content: Average 13 secs Maximum: 30 secs | Concurrency: System should support up to 100 concurrent bulk uploads. Beyond that, it should be scalable by scaling infra |
N/A
Product/Solution Impacted | Impact Description |
---|---|
N/A
User/Data Impacted | Impact Description |
---|---|
Srl. No. | Metric | Purpose of Metric |
---|---|---|
| To have clear view and understanding about the content being uploaded for a textbook and subsequently for a program. It would help to achieve target driven contribution objectives. |
General Rules:
Error / Exception | Expected Handling |
---|---|
Validations at the time of bulk sheet upload (Results in Validation Errors) | |
In case any mandatory column is missing, validation error should be thrown. Mandatory columns: Name of the content, Audience, Author, Copyright, Icon, File Format, File path, content type, Level 1 Textbook Unit | Error Message to Display: "Following mandatory columns are missing in input sheet: XXX, YYY, ZZZ." |
Number of content in input sheet should not be more than 1000. | Error Message to Display: Input sheet should not have more than 1000 content. |
Validations while processing each row for creating each content (Results in Content Creation Failure) | |
In case already successfully uploaded content is being uploaded again. Duplication of content shall be checked on the basis of following parameters: Combination of Channel, Board, Medium, Grade, Subject Content Name should be unique. (Note: Channel, Board, Medium, Grade, Subject values are adopted from the values of Textbook) | System should fail the upload of such content with following error message: "Duplicate Content" |
Validation regarding mandatory fields should be checked while processing each row, in case cell value is missing fail that creation of that content | Error message should be displayed in cell of the column "Reason For Failure" as: "Following mandatory fields are missing: XXX, YYY." |
File format: Validate the given file is in one of the supported formats by the system (all formats supported through "Upload Content" option of individual content) | Error message should be displayed in cell of the column "Reason For Failure" as: "Invalid file format" |
Validate given file format matches with format specified in File Format field. If it doesn't match give error | Error message should be displayed in cell of the column "Reason For Failure" as: "File doesn't match with the mentioned format" |
File Size: Each content should not be more than 50 MB. | Error message should be displayed in cell of the column "Reason For Failure" as: "File size is more than 50 MB" |
Icons and files to be put in google drive and to share google drive links in the respective field. Please ensure Google Drive links are correct and having view access to all permissions. Else give error | Error message should be displayed in cell of the column "Reason For Failure" as: "Unable to access file at google link" OR "Unable to access file at google link" |
Bulk csv sheet should not have two contents with same following values: Content Name | In case already created content is found again in further rows of the same input sheet, treat it as duplicate and display following error as reason for failure: "Duplicate Content" |
Multiple contents in one single row is strictly not allowed. Only one content must be shared in one row. | Error message should be displayed in cell of the column "Reason For Failure" as: "Multiple content values in a single row" |
Topic field values should follow the framework/taxonomy of the tenant. | Error message should be displayed in cell of the column "Reason For Failure" as: "Invalid Topic" |
Image icon should not be more than 1 MB and must be in png, jpg/jpeg format | Error message should be displayed in cell of the column "Reason For Failure" as: for icon image size: "Image icon size is more than 1 MB" for icon image format: "Icon image is not of png, jpg or jpeg format" |
Check Textbook hierarchy as given in "Level" columns exist in the given textbook. If not, give error | Error message should be displayed in cell of the column "Reason For Failure" as: "Incorrect values in Textbook Levels" |
Content Type: Value in Content type field should be one of the values configured in the current program. If not, give error | Error message should be displayed in cell of the column "Reason For Failure" as: "Incorrect Content Type" |
System Error | This is not a validation error. But, if any system error occurs while processing the content, error message should be displayed in cell of the column "Reason For Failure" as: "System error: <<the error message thrown by the system>>" |
Topics and Keywords - More than one topics or keywords are separated by commas. They do not contain commas within them
Currently interactive practice questions (MCQs, FTB etc) can be created and published by content editor through work space. We are heading towards program driven content contribution approach where we look forward to create such interactive content under program scope. This use case defines creation, review and linking of interactive contents to textbook under program. User having contribution role for a program can create such content. User having review role for a program can review such content. Upon successful review and acceptance, content shall be published and linked to respective section of textbook.
Prerequisites:
The over all workflow process could be broadly viewed in two parts 'contribution' and 'review'.
Srl. No. | User Action | Expected Result |
---|---|---|
Authorized user access Diksha portal | Diksha portal opens | |
User enters valid credentials | sign in to Diksha portal state tenant page | |
User clicks on "Contribute" | Program list page opens which has all the programs created for the state. | |
User selects required program | User lands on the textbook page. Page has all the books displayed under program scope. | |
User selects the required textbook | Textbook structure (TOC) page opens which has contribution (Add/contribute) option for each node |
Srl. No. | Error / Exception | Expected Handling |
---|---|---|
In case user does not has contributor right for any of the program | User will not see "Contribute" option on Diksha tenant home page on top | |
In case user does not has access to other programs | Do not display those program at all. |
Srl. No. | User Action | Expected Result |
---|---|---|
Upon reaching on textbook level. Option available for each node to "Contribute". User clicks on it. | A dialogue box opens to select which type of content user willing to contribute. This platter has only those type of content types which are defined for this program scope. The content types are:
| |
User selects "Interactive Practice Content" | Editor opens to allow user to create content. This is mapped to ECML mime type. |
Srl. No. | User Action | Expected Result |
---|---|---|
When user clicks on "Interactive Practice set" | Content Editor is opened. User can create an ECML content through content editor (all functionality as supported by current content editor). | |
User clicks on 'save' | Content is saved with the corresponding content type and linked to corresponding textbook section. | |
User clicks on "Send for review" | Saved content is sent for review | |
User closes the content editor | User returns to the contribution page of the program. |
Srl. No. | User Action | Expected Result |
---|---|---|
Validated user with reviewer rights access Diksha portal | Diksha portal opens | |
User enters valid credentials | sign in to Diksha portal state tenant page | |
User selects required program | User lands on the textbook page. Page has all the books displayed under program scope. | |
User selects the required textbook | Textbook structure (TOC) page opens which has all the contents contributed for each node |
Srl. No. | Error / Exception | Expected Handling |
---|---|---|
In case user does not has reviewer right for any of the program | User will not see "Contribute" option on Diksha tenant home page on top. Although name suggest as contribute but it is also same option for reviewer to reach out to designated textbook to review its content. | |
In case user does not has access to other programs | Do not display those program at all. |
Srl. No. | User Action | Expected Result |
---|---|---|
On textbook level, reviewer can filter the contents to be reviewed by selecting chapter from drop down. | Upon selecting the chapter in drop down, only those contents should be displayed which are contributed to that chapter. | |
Reviewer selects content to be reviewed | Content detail page opens | |
Reviewer clicks on preview | Content preview opens | |
Reviewer accepts the content | Content accepted, published and linked to textbook node |
Srl. No. | User Action | Expected Result |
---|---|---|
Reviewer rejects the content | Dialogue box opens to capture the reviewer's remark | |
Reviewer enters the remarks and submit | Content rejected and remark sent to contributor. |
Srl. No. | Error / Exception | Expected Handling |
---|---|---|
Reviewer rejects the content without remarks | Error message displayed that providing remark for rejecting the content is mandatory. |
NA
Use this section to provide requirements of the events for which telemetry should be captured. To add or remove rows in the table, use the table functionality from the toolbar.
Event Name | Description | Purpose |
---|---|---|
User log in to Diksha | Parameters to be captured for this events are: Time stamp, user details, event status (fail/success), Reason for failure if any | |
User click on "Contribute" | Parameters to be captured for this events are: Time stamp, user details, event status (fail/success), Reason for failure if any | |
User click on any of the program | Parameters to be captured for this events are: Time stamp, user details, event status (fail/success), Reason for failure if any | |
User click on any of the textbook under program | Parameters to be captured for this events are: Time stamp, user details, event status (fail/success), Reason for failure if any | |
User click on "Contribute" button on textbook level | Parameters to be captured for this events are: Time stamp, user details, event status (fail/success), Reason for failure if any | |
Content type selection from content platter | Parameters to be captured for this events are: Time stamp, user details, event status (fail/success), Reason for failure if any | |
User click on 'save', 'send for review' button in editor | Parameters to be captured for this events are: Time stamp, user details, event status (fail/success), Reason for failure if any | |
Reviewer click on content to review it | Parameters to be captured for this events are: Time stamp, user details, event status (fail/success), Reason for failure if any | |
Reviewer click on 'preview' button | Parameters to be captured for this events are: Time stamp, user details, event status (fail/success), Reason for failure if any | |
Reviewer click on Accept/Publish button | Parameters to be captured for this events are: Time stamp, user details, event status (fail/success), Reason for failure if any | |
Reviewer click on Reject/Request Change button | Parameters to be captured for this events are: Time stamp, user details, event status (fail/success), Reason for failure if any |
Use this section to capture non-functional requirements in the following table. To add or remove rows in the table, use the table functionality from the toolbar.
Performance / Responsiveness Requirements | Load/Volume Requirements | Security / Privacy Requirements |
---|---|---|
Follow the Diksha standards for performance and responsiveness in terms of event response and page load. | As mentioned in exceptional scenarios for user stories to allow authorized and valid user to access the system. | |
Product/Solution Impacted | Impact Description |
---|---|
View of a textbook under work space which is open for contribution in a program | Only textbook owner/creator can view the textbook under work space. Textbook should display all the contents which have been contributed, reviewed & published and linked to textbook node. Textbook should not display any content which although has been contributed for the textbook in any of the program but still pending for review. |
Srl. No. | Metric | Purpose of Metric |
---|---|---|
Number of content contributed, accepted, rejected on following parameters:
| To have clear view and understanding about the content being uploaded for a textbook and subsequently for a program. It would help to achieve target driven contribution objectives. | |
. | Error / Exception | Expected Handling |
---|---|---|
User does not has content contributor rights | "Contribute" option will not be displayed on state home page after Diksha log in | |
User does not has program access as a contributor or reviewer | Program will not be displayed at all | |
In case textbook has linked content in draft state and user try to publish the textbook | Error message should be displayed that "Unpublished contents are linked to textbook". | |
In case textbook is in publish state and is in scope for state program. | Textbook instance shall not be available under program for contribution. | |
Content sent for review, user wants to make changes in it. | Content which are in draft state, can only be edited. Once sent for review or published can not be edited. | |