• one project can contain an arbitrary number of tasks, but only one task per language combination
• the source language of all tasks of one project is always the same
• Projects are simply bundles of tasks, where on task creation all task values are the same except the target language
• In the task properties the editable task properties can manually be changed, so that afterwards they differ between tasks of the same project. When the overwriting of the system config via task template is implemented, this will also be true for everything you can define via task template
• in the DB add a column “project name” and a column “project id” to the task table

Consequences for the import:

• If more than 1 target language is selected in the task wizard, for each target language a task with the settings from the import wizard is created
• All values of these tasks are identical except the target language
• also all automatic mechanisms in the follow up of the task creation work as usual (like termTagging, language resource association, analysis, user association)

Implementation in the GUI:

• The TaskOverview grid stays as it is, projects are not shown (already filtered out on the load from the server)
• Add another grid (similar to TaskOverview) which shows only projects and tasks without a project (possibly introduce another task type)
  • The grid gets a rowWidget feature to show a separate small grid with the tasks (completly separate store and load)
  • The columns that are shown by default in the separate small grid are the same as in the task grid. If in a later stage the user will be able to set his own default of which columns in which order are shown, the small grid here behaves independently from the task grid.
  • All action icons available in the task grid are also available in this small grid
  • Action icons
    • In the first step there will be only one action icon on the project level: "Delete". Pressing this button, the project and all its tasks will be deleted
    • In the future we will implement a fly-out menu with more actions, that will be analogous (where it makes sense) to the existing action icons on task level

• in the “Add task” wizard:
  • Rename the field “task name” to “project name”. During import set the task name of all tasks to "rfc5646 -> rfc5646 / project name", so for example "de-DE -> enUS / Dies ist ein Testtask"
  • change the target language field to a “tag field” to allow selection of multiple target languages (same form field type as the “client” field in the “add language resources” dialogue)
  • All possible language combinations are shown with a doubled grouping feature (language pairs first) in one Association Grid. Expand / collapse all buttons should be provided.
    • PROBLEM: Multiple Grouping Feature must be purchased: https://www.extjs.com/blog/introducing-gridplugins-learn-new-ways-to-improve-the-ext-js-grid
    • Alternative: TreeGrid here? First Level Target Language, second Level Service Type, Third Level the checkboxes as currently used.
    • Solution: In the first implementation phase we will provide the possibility to group on target language AND on language resource type. Grouping by target language will be active by default
  • The following settings are used for each task:
    • count internal fuzzy
    • pre-translation
    • pre-translation match-rate
    • pre-translate (MT)
    • Check and mark terminology
• The projects overview should be accessible from the task overview (use routing!)
  • Meaning: in the task grid there is an action icon "jump to project". Clicking this will jump to the project grid, scroll to the project and expand it so that all tasks of this project are shown