| Table of Contents |
|---|
| Page Properties | ||
|---|---|---|
| ||
Introduction
This article helps troubleshoot issues with involving the generation of LQA reports.
Before |
|---|
reading the article below |
|---|
, |
|---|
make sure you |
|---|
have a good understanding of the mechanism and the prerequisites for generating the Linguist (evaluative) LQA report, which are |
|---|
described in detail in |
|---|
this dedicated article: Two types of LQA report - description and use case! |
|---|
...
Issue description & Solution
Sometimes the LQA score in the UI and the score in the generated report
...
differ by 0.01%
Solution: This is a well-known behavior phenomenon but there is no plan to address it soon.
The LQA report does not generate at all
Solution: Such a situation may happen in might occur for a couple of casesreasons:
Please, make sure Ensure that the following LQA option Yes, save results in user record LQA option is enabled in the Workflow editor, for the step where in which LQA evaluation is to be performed.
...
Ensure that the LQA-preceding step is fully performed by the assigned linguist (LQA-related segments
...
must be manually confirmed
...
so that they have green status in XTM Workbench).
...
...
Ensure that the very LQA step is fully performed by the assigned linguist (LQA-related segments
...
must be manually confirmed
...
so that they have green status in XTM Workbench).
...
Ensure that both linguists (Translator and LQA reviewer) stay assigned to the
...
relevant steps after finishing the LQA step.
...
If either of them
...
are missing at that time, the LQA report will not
...
be generated.
...
| Note |
|---|
IMPORTANT! If all the cases described above |
...
have been verified, |
...
but the issue still occurs, |
...
create a |
...
support ticket |
...
for the XTM International Support team and provide all the details needed for investigation. |
The LQA report is generated, but contains no errors
...
, and its score is 100%, despite
...
LQA errors having been added in the LQA step and
...
the segments having been confirmed
Solution: Such a situation may happen in can occur for a couple of casesreasons:
Please, make sure Ensure that the LQA reviewer imposes errors on the segments that were modified by the linguist in the step before LQA-preceding step. If LQA errors are added to the segments that were not touched affected in the previous step, they will not be displayed in the report since they are out of the evaluation scope.
Please, make sure that it was Ensure that the actual linguist assigned to the task who has entered XTM Workbench and modified the segments. It might be the case that
...
, although the LQA report that was generated
...
had the first linguist's name assigned to it (the
...
linguist to whom the task was assigned), the LQA errors
...
created in the LQA step were allocated with the statistics that were saved for the second linguist,
...
so they were not included in the LQA report
...
that evaluated the first linguist.
...
In other words, the fact that another linguist was also working on this project caused issues with statistics
...
. As a result, LQA errors were calculated incorrectly.
...
For LQA report and errors to be generated correctly, XTM Workbench has to must be opened by the proper correct linguist that is assigned , to whom the step has been assigned. If there are any mix-ups, errors then LQA will not be calculated correctly - , as shown in the case above.
LQA reports are downloaded with an error from a file, by a particular user, in the XTM Cloud UI
Sometimes you might encounter an issue that users download LQA reports with an error from a particular file, in the XTM Cloud UI.
...
The zipped package only contains a TEXT file with the following error message:
YYYY-MM-DD HH:MM:SS – An error occurred while downloading the file |
Solution: The problem most likely has been caused by insufficient rights to access LQA reports at the time of the report creation, in Users → User list → (select a user) → Access rights → LQA.
...
Even though the user’s settings might now allow accessing all LQA reports, it does not affect some past files, including the ones reported by you.
Solution: To troubleshoot a persisting case for the past files, you first of all need to enable the relevant user’s LQA access rights (if you have not done this yet). However, if this action does not avert the problem, do not hesitate to contact the XTM Support team, as proper changes on the database site might be needed. Once this is finished, you should seamlessly access the affected LQA reports.
...
If all the cases described above cases have been verified, yet but the issue still occurs, please, raise create a formal support ticket to for the XTM International Support team and provide all the details needed for investigation.