Task and Task Sequences (Models and API Endpoints)

[mlent]

Write the task models and sequences.

Tasks should include:

• endpoint - The endpoint to which the morphological query is applied. This tells us whether we are testing at the word-level, or the sentence level.
• aspect - Vocabulary, Morphology, or Syntax. This helps us fill in the user's knowledge map about these words.
• name - Serves as the unique identifier for this task.*
• success_msg - Message user sees on success.**
• hint_msg - Message user sees on first incorrect attempt.**

Grammar should include:

• TaskSequence: m2m relationship to tasks, with the following data in the joining table (TaskContext):
  • target_accuracy: when a user reaches this level of accuracy, they should move to the next task.
  • max_attempts: the maximum number of times the user should be presented with this task, regardless of accuracy, before moving on to the next task.

*Their unique identifiers should always correspond to the views and templates in these directories: https://github.com/OpenPhilology/phaidra/tree/master/static/js/views/lessons/tasks https://github.com/OpenPhilology/phaidra/tree/master/static/templates/js/lessons/tasks

**May be written as an underscore template string with access to the word's variables.

[mlent]

@ThomasK81 Here is where I can use some input. The TaskContext section should describe parameters use that must be met for a user to proceed to the next task. Can you provide ideas for considerations we should take into account?