Details
-
Bug
-
Resolution: Unresolved
-
None
-
None
-
High
-
Empty show more show less
Description
problem
If there is currently an error in pretranslation/matchanalysis (problem with language resource or similar) then the pretranslation stops and the whole task is set to error.
This is not perfect but ok for running a pre-translation on import. For starting a pre-translation / analysis after import, this is wrong since it locks the task.
solution
reason
The reason is that the Match Analysis Worker and the BatchWorker extends the Import_Worker instead just the ZfExtended_Worker_Abstract.
Basically the task is not set to status error if there is a problem while pre-translation / analysis.
Therefore the user needs now feedback about that in a different way
- Status in the analysis - Implemented with this issue
- TRANSLATE-1994 - feedback in the task overview
- Linking of language resources errors also to the task, not only to the language resource - already done
Status in the analysis
Idea: add a status field to LEK_match_analysis_taskassoc, the status is then shown in the match analysis result panel too. Status may be: done, running, error
done: all done and analysis is ok
running: analysis is running, language resource window should then be locked of that task?
error: there was an error when using the analysis, must be set from the MatchAnalysis Worker. The frontend should point the user to look into the task / language resource log for details.
Attachments
Issue Links
- relates to
-
- Selected for dev
-
TRANSLATE-4078 Show error and warning icon in new column in tasks and projects
- Done
Activity
| Link |
New:
This issue relates to |
| Workflow | Original: MittagQI Workflow [ 30612 ] | New: MittagQI Workflow with Peer [ 37039 ] |
| Rank | New: Ranked lower |
| Description |
Original:
h1.problem If there is currently an error in pretranslation/matchanalysis (problem with language resource or similar) then the pretranslation stops and the whole task is set to error. This is not perfect but ok for running a pre-translation on import. For starting a pre-translation / analysis after import, this is wrong since it locks the task. h1.solution h2.reason The reason is that the Match Analysis Worker extends the Import_Worker instead just the ZfExtended_Worker_Abstract. If changing this, the following Code must be added to the MatchAnalysis Worker, and it will work again: {code:java} /** * @var editor_Models_Task */ protected $task; public function init($taskGuid = NULL, $parameters = array()) { $this->task = ZfExtended_Factory::get('editor_Models_Task'); /* @var $ class */ $this->task->loadByTaskGuid($taskGuid); if($this->task->isErroneous()) { return false; } return parent::init($taskGuid, $parameters); } {code} Now the task is not set to status error if there is a problem while pre-translation / analysis. Therefore the user needs now feedback about that in a different way # Status in the analysis - Implemented with this issue # TRANSLATE-1994 - feedback in the task overview # Linking of language resources errors also to the task, not only to the language resource - already done h1. Status in the analysis Idea: add a status field to LEK_match_analysis_taskassoc, the status is then shown in the match analysis result panel too. Status may be: done, running, error done: all done and analysis is ok running: analysis is running, language resource window should then be locked of that task? error: there was an error when using the analysis, must be set from the MatchAnalysis Worker. The frontend should point the user to look into the task / language resource log for details. |
New:
h1. problem If there is currently an error in pretranslation/matchanalysis (problem with language resource or similar) then the pretranslation stops and the whole task is set to error. This is not perfect but ok for running a pre-translation on import. For starting a pre-translation / analysis after import, this is wrong since it locks the task. h1. solution h2. reason The reason is that the Match Analysis Worker and the BatchWorker extends the Import_Worker instead just the ZfExtended_Worker_Abstract. Basically the task is not set to status error if there is a problem while pre-translation / analysis. Therefore the user needs now feedback about that in a different way # Status in the analysis - Implemented with this issue # TRANSLATE-1994 - feedback in the task overview # Linking of language resources errors also to the task, not only to the language resource - already done h1. Status in the analysis Idea: add a status field to LEK_match_analysis_taskassoc, the status is then shown in the match analysis result panel too. Status may be: done, running, error done: all done and analysis is ok running: analysis is running, language resource window should then be locked of that task? error: there was an error when using the analysis, must be set from the MatchAnalysis Worker. The frontend should point the user to look into the task / language resource log for details. |
| Status | Original: Open [ 10002 ] | New: Selected for Development [ 10100 ] |
| Link | New: This issue causes TS-821 [ TS-821 ] |
| Link | New: This issue relates to TRANSLATE-1994 [ TRANSLATE-1994 ] |