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

Use case - Question paper

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:

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

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

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

  1. Rohan a student of 5th Grade in Haryana opens the State education app (Avsar).

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

  3. He clicks on Take Test, to begin his test. He completes the test on the state app digitally.

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

  1. Create a question paper on Sourcing(Vidyadaan) and Publish it on consumption (Diksha). With private visibility (meaning only authorized users can view it.)

  2. Authorized Applications make and authenticated API calls get the Content from Diksha that is Private(not visible/ available publicly)

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

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

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

Defining visibility at the time of project setup

Editing visibility at a later time.

Editing visibility at a later time

*This document has been updated on 16th June, the comments might be outdated for an earlier version of this document.

  • No labels