Content Comparison

Overview:

...

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

Points for Discussion in Implementation of Refactor Flow -

1. Reject Question API: We will add rejectedContributionComments key of an object type to store questions rejection comments in the question-set schema.

2. Sending a question back for corrections (From Sourcing reviewer to Contributor): Getting error while using /v1/update/do_id API to update status.

3. Adding marks as an attribute for questions: Add marks key in question schema.

4. Opening up of previously created UI when user clicks on Upload Content and selects Subjective Questions.