Versions Compared

Key

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

...

Slide 2-6 attached for wireframes of the solution

Technical solution:

...

  • We’ll use SB-Forms to create quality-check form.

  • The config will be stored in the category definition. 

  • If quality check form exist in category definition then we’ll open the pop-up

  • The value of quality-check form will be stored in question object.

Category Definition:

We’ll add new form in category definition named reviewerQualityCheck.

Code Block
languagejs
{
  "objectCategoryDefinition": {
     ...
     "forms": {
       "create": {},
       "delete": {},
       "publish": {},
       "review": {},
       "search": {},
       "reviewerQualityCheck": {
          "templateName": "",
          "required": [],
          "properties": [
            ...
          ]
       }
     }
  }
}

Question Schema:

We’ll add a new key meta of object type reviewerQualityChecks which will store all the quality-check form information.

Code Block
languagejson
{
   “identifier”"identifier": “do"do_id”id",
    ...
    “meta”"reviewerQualityChecks": {
       “comprehensibility”"comprehensibility"“2”"2",
       ...
    }
}

Reason for storing reviewerQualityChecks in question schema:

  • Leveraging existing API

  • Avoiding multiple API calls