Content Comparison

Sl

User story

Present user interaction

Proposed user interaction

Open Items/ Decisions

1

Admin can create a Project for sourcing question papers.

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 setAdmin will go to sorucing (vdn sourcing) and create project along with the question set defining the scope.

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

2. Name the project, allow or not allow nominations

3. Define relevant dates

4. Create/ select target question set(s)

   1. Define metadata for question set [Grade, Subject, medium, etc]

   2. Define sections for the question set

   3. Define Instructions for the question set (description)

   4. Admin can also search for past question sets, using filters for grade, subject, medium.

   5. Admin can select one or more existing question sets

5. User can select Type of questions (this instead of content types) allowed in the question set

6. Define blueprint for each of the question set(s)

7. Assign Object (collection) creator role

8. Pubish project

Closed:

1. Question set on the dev portal now, does not allow to add sections. Is that a limitation?
   Creation of sections can be managed through configuration, we need to specify/limit levels at which sections can be created.

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. Question sets, can only be created/selected through this flow. There is no separate screen/ touchpoint where user can view/create question sets.

2. Blueprint definition will happen as per the current flow.

Open:

1. Since we are already defining the question set definition what is the use of collection creator role?

Open Tasks:

1. Final inputs on the UI Mockup

2. Use case grooming session with Kartheek

3. Enginnering implementation design to be shared by Bharat

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

Closed:

1. There will not have any ripple effects here?be any change in this flow due to the change in project creation flow.

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

Closed:

1. There will not be any change in this flow due to the change in project creation flow.

2. It is not possible to allow for contribution roles from the sourcing portal?
   (Opinion - All the role management should be unified at a single place, sorucing portal should be used as unified manager).

Open:

1. Design flow for taking user to the contribution role assignment page from souricng project.

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 Create 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 create 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 reviewInputs on design flow awaitied

Open:

1. Closing on UI Mockups

2. There is no change in user interaction flow

3. There is change in the type of content being opened, when a contribution reviewer or sourcing reviewer opens a question for review

4. Bharat needs to share engineering design implementation approach.

Closed:

1. Is there any change in the question 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

No Change

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

Closed: (Approach)

1. Frontend to remain the same as the current view

2. APIs exist for displaying question object (as opposed to questioning set object)

3. Wiring has to be done for the question object

   1. Open question editor

   2. Enter question and answer

   3. Add tags

   4. submit for review

Open:

1. Implementaion approach to be shared and closed

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 ?

Change

1. Go to contribution portal

2. View all the project, open a project

3. View all the added questions

Closed: (Approach)

1. Frontend to remain the same as the current view

2. APIs exist for displaying question object (as opposed to questioning set object)

3. Wiring has to be done for the question object

   1. Open question editor

   2. Enter question and answer

   3. Add tags

   4. submit for review

Open:

1. Implementaion approach to be shared and closed

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 ?

Change

1. View all the added questions

2. Open a question and take action

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

Closed: (Approach)

1. Frontend to remain the same as the current view

2. APIs exist for displaying question object (as opposed to questioning set object)

3. Wiring has to be done for the question object

   1. Open question editor

   2. Enter question and answer

   3. Add tags

   4. submit for review

Open:

1. Implementaion approach to be shared and closed

Appraoch 1

Slide 1- 12 - Project Creation

1. In the heading Create/select collection is changed to create/select Objects

2. Slide 2 - <Tag Kamesh>

   1. There is a change in order of selecting allowed for nomination and nomination date selector.

   2. Search for content type is removed

3. Select content is renamed as select assets <Tag Kamesh>

4. Slide 6 - Previous question sets are shown for selection, searching - This was kept to keep the consistency in user interaction and design, should this be removed? If yes how will the user interaction look like for this

5. Slide 7 - Should there be a Select All? for the type of questions?

6. Slide 8 - Save as draft button is renamed as Save - <tag suren,kamesh> does this work?

7. Slide 12 - In this context how will this role be used? If not being used, can we remove it?

User Role management - Sourcing

<To be updated>

User Role management - contribution

<To be updated>

Question contribution

<To be updated>

Contribution reviewer flow

<To be updated>

Souricing reviewer flow

<To be updated>

Approach 2

Slide 1- 11 - Project Creation

1. In the heading Create/select collection is changed to create/select Objects

2. Slide 2 - <Tag Kamesh>

   1. There is a change in order of selecting allowed for nomination and nomination date selector.

   2. Search for content type is replaced with target object, was this intentioned in your design as well?

3. Slide 5 - Since Content type drowdown is not at the same level as other three search dropdowns, why are the kept together in a sequence? <Copied for Kamesh’s design here>

User Role management - Sourcing

<To be updated>

User Role management - contribution

<To be updated>

Question contribution

<To be updated>

Contribution reviewer flow

<To be updated>

Souricing reviewer flow

<To be updated>