Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 5 Next »

Overview:

On Sunbird the core definition of the QuML editor is upgrading. This means the question set, object definition is being changed. Prashnavali essentially is about the question and question paper creation, which means that the core way of how questions are added and question paper is created, needs an upgrade.

However, the overall user stories for all the actors (Admin, Question contributor, Question Reviewer, Question paper creator) do not change drastically.

There are some user interaction design and some User interface changes that will be visible to the end-user, on the backend, there will be complete rewiring of the fundamental building blocks.

User story level mapping:

Sl

User story

Present user interaction

Proposed user interaction

Open Items

1

Admin can create a structure for a QP; definining its
- Metadata
- grade subject medium etc.
- Sections in the QP
- Instruction block

  1. Go to Diskha Portal, to create a new Question paper collection

  2. Define metadata for the question paper

  3. Define sections of the question paper

  4. Define instructions for the question paper

Instead of defining a question paper collection, admin can now define a question set.

  1. Go to souricng portal, Create new project -> create new question set

  2. Define metadata for question set

  3. Define sections for the question set

  4. Define Instructions for the question set (description)

  5. Define blueprint for the question set

  1. Question set on the dev portal now, does not allow to add sections. Is that a limitation?

  2. As per the design shared by Kamesh, the Question set can only be added from under create new project? What are the other starting touch points for admin to create a new question set?

  3. Blueprint defintion earlier used to happen at the time of project creation, now will this be done at the project set definition level? (Opinion - This should happen at this level itself, for the users to have continiuty of actions)

2

Admin can create a new project for sorucing questions for the question paper

  1. Go to Souricing Portal

  2. Click on create new project

  3. Select Content Type

  4. Select Target Collection

  5. Define blueprint values

  6. Publish Project

  1. Go to sourcing portal

  2. Create new project

  3. Select Target Question set (as opposed to target collection)

    1. Filter question sets based on Grade, medium, subject (same as current flow)

    2. Choose one or more question sets from the list of question sets

    3. If question set does not exist, click on create new question set

  4. Select Type of questions allowed for
    quesiton sets in this project

  5. Publish Project

  1. Finalizing the UI for the user flow

  2. Task break down and Planning?

  3. Frontend and backend both will be owned by Ekstep team?

  4. How can parallel development be intiated for Contribution and souricing?

3

Admin can assign users as Souricng reviewers (Question paper creator)

  1. Go to Souricng portal

  2. Select a published project

  3. Go to assign users tab (in project details page)

  4. Search for user and assign them the role of reviewer

No interaction Change

No UI Change

  1. Is it safe to assume that project target will not have any ripple effects here?

4

Admin can assign users as Question contributors and Question reviwers

  1. Go to Contribution portal

  2. Select a published project

  3. Go to assign users tab (in project details page)

  4. Search for user and assign them the role of reviewer

No interaction Change

No UI Change

  1. Is it possible to do user role management for the contribution portal from the sourcing portal?
    (Opinion - All the role management should be unified at a single place, sorucing portal should be used as unified manager)

5

Question contributor can view projects assigned to them

  1. Login on to contribution portal

  2. Click on my projects

No Change

6

Question contributor can upload a new question

  1. Login on to contribution portal

  2. Open the project

  3. View all the sections in the question paper

  4. Click on upload question on any one section

  5. Select the type of question that is to be uploaded

  6. Add the question and answer key

  7. Click on edit details

  8. Add tags to the question

  9. Submit the question

  1. Go to contribution portal

  2. Open the project

  3. See the sections in the question set

  4. Click on Add new

  5. Select the type of question

  6. Add the question, answer key, set the question tags here itself.

  7. Submit the question for review

  1. Inputs on design flow awaitied

  2. Is there any change in the question set defintion as well?

7

Question contributer can make edits in a question for which edits are requested and can re-submit the question

  1. Go to contribution portal

  2. View all the added questions and their status

  3. Open a question which is requested for change

  4. Make edits and resubmit

  1. Change in implementation approach

  1. What engineering changes are required for the making the content editable for the question? (The current flow is at the question set level)

8

Question reviewer can view all the uploaded questions

  1. Go to contribution portal

  2. View all the project, open a project

  3. View all the added questions

No change on user flow

  1. Change in implementation approach

  1. What engineering changes are required ?

9

Question reviewer can Accept a question or request for change

  1. View all the added questions

  2. Open a question and take action

  3. Accept the question or Request for change( with comments)

No change on user flow

  1. Change in implementation approach

  1. What engineering changes are required ?

UI mockup:

https://docs.google.com/presentation/d/19yWPgL4s8mbT--RB1unnpPFiGZR1alFZ-jaTCN9YD3A/edit?usp=sharing

Slide 2-9: Creating a new project and a new question set editor

Slide 11-13: User Role management - Sourcing

Slide 15-17: User Role management - contribution

Slide 19-25: Question contribution

Slide x-y: Question reviewer flow <to be added, based on comments for question contribution>

Slide x-y: Question paper creator flow <to be added, based on comments for question contribution>

Old Flow:

A question paper collection is created on the Consumption portal, followed by project creation on sourcing and contribution portals. The life cycle is shown below.

New Flow:

The question set is created on the sourcing portal. The new life cycle is shown below

OLD COMMENTS ONLY FOR REFERENCE

  1. Instead of question collection, create a question category

  2. Define sections (chapters) at question set level

  3. Define instructions at question set level (This will be used as instruction in the question paper)

  4. Define blueprint at the project level for a question set

  5. Contribute to a question set

    1. Instead of contributing a question set in the question paper collection, contribute a single question in the question set

    2. Instead of tags being defined at question set, define the tags at the question level

  6. Question review - Instead of question set review, now the review will happen at the question level

  7. Progress against blueprint - Show the progress against blueprint widget for the question set

  8. Print service - Instead of Question paper collection hierarchy, update the print service to work on new question set hierarchy.

Next steps:

  1. Define engineering step by step plan for migration

  2. Close discussions on the new changed frontend flow

  • No labels