Problem

Exports utilizing several chained workers cannot be stuffed into a single request. There is an solution with a "Popup in Progress" that is quite ugly with bad usability

Solution

Introduction of a "Basket" with the generated exports that can be downloaded. This "basket" is located in 2 places:

In the Project Grid: In the task-properties tabs, as a new first tab "Available Exports" in the "Manage Files" tab

In the Tasks Grid: as a seperate menu-Item "Available Exports" that is below the "Export" Item. This is neccessary, because there are users who canot see the project Grid

The Basket/Grid will show an Export as soon as it is exported via the task-menu. The tab in the project grid's properties tab is automatically opened when something is exported.

• An item in the grid has 4 props: Type, filename, state, date of creation (as menu-item this is shortened to Type/state/date)
• Initially, filename & date are not filled
• The state of an export can be "in progress", "available" "failed". Failed will have a tooltip to look in the events for details
• When the export is available (or failed), the entry will by highlighted (css effect) and updated. This is initiated via messagebus (and therefore can be triggered by workers). Also there will be a toast "Export type XYZ for task XYZ is available"
• In the Tasks-grid, the "Available exports" menu will be populated automatically when opened and no trigger via messagebus is neccessary. The toast is sufficient here
• The items will have view-rights that are the same obviously needed to initiate the export of the given type
• There shoud be prequesites to add a proper progress-calculation later on
• The datamodel should respect that we may have a versioning later on
• Initial implementation: an initiated export will replace an existing export after successful generation. If the generation fails, a preceeding export is still available
• In the initial implementation, all endponts in the task-export menu shall add their files into the basket also but work the way they are (no toast)
• When an export was initiated via the export-menu and it is available, it should be downloaded in the background by the browser (can be achived via window.location = downloadURI IF the "Content-Disposition: attachment"-header is set)

Instant Translate

The current implementation of the Instant-translate "file-list" shall be replaced being an alternative view of the export-basket

Data model/storage

• The Exports are stored in a new table LEK_task_export, fields are obvious
• The files are stored in the subdir /export of the task's data-dir