Versions Compared

Key

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

...

With this design and implementation, we are enabling most of the capabilities and behaviour to Question and QuestionSet object which are already exists for Content and Collection.

Below capabilities we will enable together (for all object by generalising) once we achieve this.

  • Visibility: Parent for Content and Question.

  • Collection and QuestionSet with Visibility: Parent as reusable objects in the platform.

  • QuestionSet - is always materialised. Dynamic QuestionSet capability is not enabled now.

API Spec:

<TODO>

Conclusion:

<TODO>

Questions:

  1. Separate Mime Type For QuestionSet?

    1. QuestionSet contains only Questions but, Collection contains Content and QuestionSet.

    2. Structure is same but, the publishing process require its own logic to handle.

    3. QuestionSet should generate printable version (PDF) based on configuration.

    4. Now we are handling only materialised QuestionSet. When we enable Dynamic QuestionSet (based on search query) it requires separate handling.