Use case - Question paper
A state wants to source question paper for conducting SAT in the state. For the creation fo SAT question paper, the questions are sourced by teachers/ resource groups. Once the questions are added and a first level review happens. The reviewed and accepted questions are shared further with the State SCERT Assessment wing. The assessment wing, selects and curates a paper from the pool of reviewed questions. Once the question paper is curated:
Offline mode - The question paper’s Word/pdf doc is generated and distributed either via courier or email to districts to further print and conduct the examination in pen and paper format. However given the pandemic situation, the State has moved to Online mode.
Online mode - The question paper is shared to the state APP via Authorized and authenticated API call. The state app after receiving the question paper, serves it to students for consumption and stores relevant data points of student performance.
Key requirement: Before the exam - The questions / question paper must have limited visibility and be only accessible to authenticated and authorized users.
This applies to all the
Questions created for the SAT project - Draft, Submitted, Approved, Change Requested or Rejected
Question paper - All the approved questions by sourcing reviewer
After exam -
The state can choose to make the question paper visible to the students for practice - This will be available on the consumption portal (Dikhsa, or even external apps via API)
Only the questions approved by the sourcing reviewer to be part of the question paper are visible to the student
...
For the first use case implementation the question paper will be created using the,
Editor version - 0.5 Editor
Target Collection - Question paper collection
Target Content - Exam Question.
User roles:
Admin - SCERT assessment wing admin who will create collections for all the question papers, create projects, and manage roles.
Question Contributor - Subject teachers or Resource person who will contribute a question
Question Reviewer - (Contribution reviewer) Subject matter expert who will review all the questions that are contributed and can accept or request for change
Question paper creator - (Sourcing reviewer) They select or reject the question that are submitted by question reviewer. All the selected questions are treated to be part of the question paper.
Question paper sourcing
Admin will create the question paper collection on Consumption portal - One for each question paper
Admin will create a project to source the questions for the collections.
In one single project multiple collections can be created
At the time of project creation the admin gets the option to edit the visibility of each of the question paper collection
Default value for the question paper collection is Picked from the Question paper collection’s property
The value set for the question paper collection is applicable to collection as well as target content (questions) created for the question paper.
Question paper is created on Diksha on a state channel, and only users mapped to that particular state (e.g. Haryana) are able to contribute to that question paper on Sourcing
Question paper creation flow
Contribution - Questions are added by Question contributors in the relevant question papers and projects.
Question reviewer - Question reviewer, reviews the questions for quality, correctness and tagging, if required requests for changes from the contributor or approve the question
Question paper creator - They get all the questions approved as part of the list, which they can further reject or accept form the list to curate the question paper.
- Once the question paper is created they set the question paper start and end date. This value is also passed on to question paper when it is published on consumption.
- The start and end date for a question paper can be updated/ modified. On modifying the date and saving on the sourcing portal, will also update the dates for the question paper published on the consumption
Admin - Admin will go to consumption (Dikhsa) and Submit the question paper collection for review. Once it is approved for publishing the question paper will be published on consumption. The visibility will remain as the same as was defined at the time of project creation.
Question paper consumption
In Online mode - The External registered application, will make an authorized and authenticated API call to Consumption to get the published ‘Question paper’ resource.
There are 3 steps to identifying a question paper:
Getting list of all the relevant question papers
Search for All the question papers created and published by a the State (Haryana can search for resources created by Haryana)
Search based on Board, medium, Grade, Subject
Visibility status - Only search for questions papers that are published and have visibility of Private
Question paper start and end date - All the question papers for which the current date/ date of request lies between the start and end date set for the question paper (by the question paper creator)
Identifying the question paper - After previous step the list of all the question papers are shared to the external app, then either
Show all the question papers from the previous step to the user to choose, or
Do some filtering at their end and show selected question papers to the users from the list
Getting the complete content of the question paper
An API call is made to fetch the complete details of the questions in the question paper
Question - Text, images (along with size), special symbols, etc. (along with question editor state)
Answer key
Tags and other properties - attached to the each question
After Exam
After the examination, the admin can choose to make the question paper public, so that students can access the past year question papers for practice.
Steps:
Admin requests the sourcing reviewer to edit the visibility property of one or more collections in the project
Sourcing reviewer modifies the visibility property of one or more question paper collection and saves. On save, the visibility property for the published question paper resource and questions inside it are also updated.
If made public - the question paper can now be visible on consumption directly
Under a section called Past question papers
Visibility of different objects
For the sake of this document, I am not using the term Public, protected, Private or parent. They have a specific meaning attached to them in the context of sunbird which may be different from the literal meaning of the word. I am going to use the terms
V1 - Publicly available/visible on consumption
V2 - Limited visibility based on Role and permission.
...
Object State
...
Resource
...
Visibility
...
Consumption
...
Sourcing
...
Draft
...
QP Collection
...
-
...
Visible only to creator Admin
...
NA
...
Draft
...
Project -
(Each collection in a project)
...
V2
...
Visible only to creator Admin
...
Visible to contributors, and reviewers
...
Draft
...
QP Collection
...
V2
...
Visible only to creator Admin
...
Visible to contributors, and reviewers
...
Draft
...
Questions
...
V2
...
Visible only to creator Admin
...
Visible to contributors, and reviewers
...
Published (Before Exam)
...
QP Collection
...
V2
...
Limited Visibility
...
Visible to contributors, and reviewers
...
Published (Before exam)
...
Questions
...
V2
...
Limited Visibility
...
Visible to contributors, and reviewers
...
Published (After exam)
...
QP Collection
...
V1
...
Public Visibility
...
Visible to contributors, and reviewers
...
Published (After exam)
...
Questions
...
V1
...
Public Visibility
...
Visible to contributors, and reviewers
Proposed Screens for Setting and editing visibility: (For the initial discussion)
Defining Visibility during project creation
...
Editing visibility at a later time.
...
Future scope:
This needs to be built in a way that it is not limited to Target collection as Question paper collection and Target content as Exam question. Soon (by July end) it will be implemented after the upgrade of Prashanvali to new QuML editor 1.0. Where the target object will be question set and target content will be questions.
Additionally the same logic can be applied to any content on Diksha which the state wants to create any explanation video or any other material and wants to keep it private for a bit (No direct use case for this is known right now, but from the product lens, it will be good to have this functionality for any object/category or content) State SCERT will source the question papers for conducting SAT, Regular interval (Fortnightly, Monthly, etc) Quiz and tests on Diksha. To create the question paper, the state will use Vidyadaan (Prashnavali) to create the question paper (with 2 level review).
Offline usage of question paper - Print a PDF and share with District Officers who further share with the Schools to conduct the exam. [This is not possible due to the physical schools being shut due to pandemic]
Online usage of question paper - Due to the 2nd wave of the pandemic, the opening of schools is for a physical test is not foreseeable. The states are looking to conduct teaching and learning activities online. And also conduct tests online.
There are State Education Applications - which will
Get the Question paper from Diksha
Show it to students
Generate and maintain the student’s performance report
Share usage telemetry back to the student
State SCERT Administrators who will have access to view and modify the question paper or its properties on Diksha
Update/Edit any question in the question paper
Update different property/metadata of the question paper
Key requirements:
Questions paper can not be publicly available - They need to be shared only with the users who have the authentication and authorization to view the question paper.
Question paper needs to be sequenced. Have a Go-live/ Start date and a Live-Until/ End date. These are required to ensure that the Question paper can be prepared and published beforehand and will only be shown to students only after the start date and until the end date.
If a question paper or any of its metadata is updated. It should immediately be reflected for the students who refresh/request the question paper after the update is made.
User Journey:
Rohan a student of 5th Grade in Haryana opens the State education app (Avsar).
He sees a section to take the test. In this section, he views all the tests that are to be taken by all the 5th-grade students today.
He clicks on Take Test, to begin his test. He completes the test on the state app digitally.
Once the test is completed, his performance report is generated and stored in his student profile, This student profile is visible to Rohan and his teachers.
What will it take to achieve it:
Approach 1:
Create a question paper on Sourcing(Vidyadaan) and Published on consumption (Diksha) - With private visibility - meaning that only authorized users can view it on consumption.
Authorized Applications make and authenticated API calls get the Content from Diksha that is Private(not visible/ available publicly)
If the Applications have permission to view the question paper and the date on which the request is made lies between the start/end date of the question paper. They get the question paper details.
...
Journey of a question paper after the exam is done.
The state can choose to make the question paper visible to the students as part of an additional resource for practice.
A student can go to Diksha and view past question papers
A student can go to state application and view past question papers (State application will make an API call to get this data from Diksha)
There can also be cases when a Public question paper is required to be made private or be unpublished
If the content is made private - it will stop being publicly available; be visible to authorized users only
If the content is unpublished - it will be made visible only to the Sourcing admin and no one else
...
Scope:
Immediate: In the first version we are looking to use:
Target Object: Question paper collection; Target content: Exam Question
Near Future: After migration of Prashanvali to QuML 1.0 from 0.5
Target Object: Question Set; Target content: Questions
The behavior of the question paper will remain the same as above.
Future: The same logic of private can be applied to any type of content that is created on Diksha
...
– An initial draft; (open to suggestion for modifications)
Proposed Screens for Setting and editing visibility: (For the initial discussion)
Defining Visibility during project creation
Design Flow: https://docs.google.com/presentation/d/12JW58Iokn-3IdwifUeWab8F8vPC8HFHqZjkbERtwsLc/edit?usp=sharing
Tech Implementation
Approach 1:
Publish Project
In a published project, the status of QuestionSets remains draft.
In the QuestionSet, questions will be:
Added and submitted by Contributors(status: Draft, but Review Pending ),
Reviewed by ContributorOrg reviewer(status: Live but Approval pending) and then
Approved and published by SourcingOrg reviewer(status: Live but Approved).
For QuestionSets having all approved questions, we’ll publish the QuestionSet on click of button(Publish Question Set) which will be enabled on the basis of config we’ll pass to category definition API.
An existing key
publishQuestionsetwill be used in category definition which will have boolean values.API: category/definition/v1/read
On click of button(Publish Question Set), we’ll hit publish API so the status of QuestionSets will become live.
API : questionset/v1/publish/do_id
It’s an Async API.
Adding Import Button on TOC
After having the status of QuestionSet as live, will show a button “Import QuestionSet” to import it on Ed Portal.
This will be enabled on the basis of the category definition config we used for the button(Publish Question Set) in 1(D).
On click of the button(Import QuestionSet) we’ll hit the import API.
API: questionset/v1/import
Pros: Use of existing API
Cons: Existing API only allows the QuestionSet having all approved questions
Open questions:
As the publish QuestionSet API is Async, how will we show the Import QuestionSet button.
If the publish QuestionSet API fails, what shall we show there or how should we handle this?
Approach 2:
...
Importing QuestionSet on Ed Portal
At the time of publishing a project by SourcingOrg Admin, a copy of the QuestionSets will be created at Ed portal as well using import QuestionSet API(New).
Import QuestionSet API will make a copy of QuestionSet having a common key “originalPath” to define relation/reference between both the QuestionSets i.e; original and cloned.
Questions will be added by contributor, reviewed by ContributorOrg reviewer and then SourcingOrg reviewer i.e; complete question journey upto approval pending will be on Vdn portal only.
Importing Questions on Ed
At the time of approval from SourcingOrg Admin/reviewer the question will get directly published at Vdn portal and imported at Ed Portal using import Question API(New).
Import question API will make a copy of approved questions from Vdn portal and import them on Ed portal.
originalPath key will be helpful in adding the approved questions in the correct QuestionSet.
Requirements: 2 New API
To import QuestionSets of a project from the Vidyadan portal to the Ed portal while publishing it.
To import all the approved questions to the imported project on Ed Portal.
...
*This document has been updated on 16th June, the comments might be outdated for an earlier version of this document.