Review workflow¶

*(to be revised)...

The workflow when submitting a new Questionnaire or editing an existing one is as follows:

• A logged in User A can create a new Questionnaire or start editing an existing one.
  • When he does [save] his changes, it creates a new version (with the existing code if available) with status draft.
  • The user can add other users (editors) which can make edits to the draft. While a user is working on the draft, the version is locked for other editors to prevent conflicting edits.

• The original user (User A) can [submit] the version which receives status pending.
  • No more edits can be made to the version.
  • The moderators are notified that there is a new pending version.
  • A moderator reviews the version and decides what to do next:
  • Review decision [publish]: The changes are ok, the version receives status approved.
    • The approved version is inserted in Elasticsearch (replacing older ones).
    • Any old version receives status inactive.
    • All editors are notified.
  • Review decision [reject]: The changes are very wrong, the version receives status rejected.
    • All editors are notified.
  • Review decision [revise]: Corrections need to be made, the status of the version is set back to draft.
    • All editors are notified.
    • The users can make changes to the questionnaire again (review procedure starts again)

Missing: "revise" decisions need to be logged somehow. It should be possible to pass messages from user to user (eg. users submitting comment for the reviewer or reviewer submitting comment for the editors when "revise").