Versions Compared

Version Old Version 14 New Version 15
Changes made by

Saket Sinha

Saket Sinha

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview:

...

Index

Open Questions

Appraoch 1

Slide 1- 12 - Project Creation

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

  2. Slide 2 -

    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

  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 - does this work?

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

Slide 13- 16 - User Role management - Sourcing

<Same as existing flow, no change>

Slide 17- 20 - User Role management - contribution

<Same as existing flow, no change>

Slide 21- 26 - Question contribution

  1. Slide 22 - 24 No change

  2. Slide 25 - List of question types to be shown as defined in the project set.

  3. Slide 26 - Now opens up the question details page and not the earlier flow of question set.

Contribution reviewer flow

<To be updated>

Souricing reviewer flow

<To be updated>

Approach 2

(This is alternate approach only for project creation flow, rest all remains the same as previous Mockup slides)

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>

Detailed PRD

  1. Project Creation

  2. Contribution Flow

  3. Review flow

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.

...

Status
titleOld Comments
Status
titleonly 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