Content Visibility on Consumption and Souricing

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

1. Questions created for the SAT project - Draft, Submitted, Approved, Change Requested or Rejected

2. Question paper - All the approved questions by sourcing reviewer

After exam -

1. 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)

2. Only the questions approved by the sourcing reviewer to be part of the question paper are visible to the student

Overall Flow

For the first use case implementation the question paper will be created using the,

1. Editor version - 0.5 Editor

2. Target Collection - Question paper collection

3. 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

1. Admin will create the question paper collection on Consumption portal - One for each question paper

2. Admin will create a project to source the questions for the collections.

   1. In one single project multiple collections can be created

   2. At the time of project creation the admin gets the option to edit the visibility of each of the question paper collection

   3. Default value for the question paper collection is Picked from the Question paper collection’s property

   4. The value set for the question paper collection is applicable to collection as well as target content (questions) created for the question paper.

3. 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:

1. Getting list of all the relevant question papers

   1. Search for All the question papers created and published by a the State (Haryana can search for resources created by Haryana)

   2. Search based on Board, medium, Grade, Subject

   3. Visibility status - Only search for questions papers that are published and have visibility of Private

   4. 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)

2. Identifying the question paper - After previous step the list of all the question papers are shared to the external app, then either

   1. Show all the question papers from the previous step to the user to choose, or

   2. Do some filtering at their end and show selected question papers to the users from the list

3. Getting the complete content of the question paper

   1. An API call is made to fetch the complete details of the questions in the question paper

      1. Question - Text, images (along with size), special symbols, etc. (along with question editor state)

      2. Answer key

      3. 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:

1. Admin requests the sourcing reviewer to edit the visibility property of one or more collections in the project

2. 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.

3. If made public - the question paper can now be visible on consumption directly

   1. 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.

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)