Page Comparison

...

Objective

1. The aim is that objects of type questionSet be used as target objects for sourcing projects without having to create them elsewhere.

2. Objects of type question be contributed and reviewed individually to such sourcing projects.

Background

1. Product requirements document. (Confluence Document)

...

2. Product mockups. (Google Slides)

Proposed Implementation

1. Sourcing

...

1. We will add an enableQuestionCreation attribute to the editor configuration

2. We will implement changes to be able to emit question set metadata on exiting the question set creation page

3. We will use a target_type of questionSets to show/hide the changed UI for creating a program with a target questionSet.

2. Contribution

- Question Creation

...

We will create a new add-from-library Angular library to add questions from library to question sets.
Scope:

- In release-4.4.0
1. We will add one new attribute to the collection and questionSet KP schemas: reusedContributions, which will contain the list of identifiers added to the collection via library

3. We will use this list of identifiers to detect whether a question has been added from library or not

- In release-4.3.0

1. We will invoke this library from the portal for an existing question set.

2. The question set and unit identifiers will be passed to the library, which will use the existing library and player components

3. On returning/saving, the library will emit the question identifiers that have been added

4. The portal will then make an update hierarchy call for the given section

5. Caveat: We will only add questions to the section that was passed to the library to begin with.

6. We will use the following components of the existing collection editor:

   • Library: We will need to enable the existing library components for objects of type Question

   • Quml Player: We will need to support previewing QuML questions in the library component etc.

...

1. We will have to modify this logic to be able to publish question sets only with "Approved" questions, and not re-create questions when the question set is re-published.

2. We will add acceptedContributions and rejectedContributions attributes in creation-portal question-set schema.

3. If sourcing reviewer approves the question, we will add its identifier to acceptedContributions array and if question is rejected it will be added to rejectedContributions array.

4. We are using autoCreatorV2 flink job to copy contents from sourcing to consumption. Here we will add a check condition to validate if acceptedContributions attribute exists or not in question-set metadata.
   - If attribute exist, we follow the new flow, in which we will remove the rejected questions from
   question-set hierarchy and save only with approved questions to consumption.
   - If attribute does not exist, we will use the existing flow and save all questions in question-set to
   consumption irrespective of questions approval and rejection.
   

DB Changes: ProgramTable

DB Changes: Configuration Table

...