Skip to main content

XTM Cloud 13.4

Quality tab

The Linguistic Quality Assessment (LQA) results for a particular linguist are displayed in the Quality tab screen.

Note

XTM Cloud Administrator or Project Manager must first enable this option for the relevant user in User Editor > unlock-alt-solid.svglock-keyhole-solid.svg Access rights > LQA.

Results are collected from LQAs that are performed in the workflow step after the step to which the linguist was assigned. LQA results are stored for linguists only when the option Yes, save result in user record has been selected from the LQA dropdown list in the Edit Workflow window.

The evaluated and the LQA step need to be finished in XTM Workbench and all relevant segments must be set to Completed green-tick.svg for the report to be generated. Additionally, linguists must stay assigned to both steps even after the LQA step has been finished.

The Quality score at the top of the tab is the weighted arithmetic mean from all reports per language completed so far by the relevant linguist.

LQA results can be displayed:

  • Per file.

  • Per language.

LQA results are presented in a table containing the following information:

  • Project name.

  • Source language.

  • Target language.

  • Workflow step.

  • Filename – This information is displayed only in case of LQA reports per file. LQA reports per language aggregate data from all files in the relevant language combination.

  • Score.

  • Words.

  • Evaluator.

  • Test completed.

You can access the following options from the context menu icon bars-solid.png on the left-hand side of the relevant LQA result:

  • pen-to-square-solid.svg Open project editor – open the Project Editor popup on the Project Editor > General info tab.

  • download-solid.svg Download LQA report – download the linguist LQA report in Excel format. This report contains an evaluation of the work of a particular linguist. The calculations in this report type are based on a project's Statistics. This report only lists errors made by the relevant linguist in the segments they have changed manually.

    This report displays the following information for the relevant file (if you selected the Per file option) or for the relevant language combination (if you selected the Per language option):

    • Evaluee.

    • Evaluator.

    • Severity multipliers.

    • Word count.

    • Issue types.

    • Weight of the LQA errors.

    • Issue count.

    • Penalty.

    • Target subscore.

    • Total score.

    Note

    This report can be also downloaded using the REST API method. The Type parameter enables to specify, whether to get the report Per file or Per language. For details, see the REST API documentation: https://www.xtm-cloud.com/rest-api/#tag/Project-LQA/operation/downloadLqa.

  • download-solid.svg Download extended report – This menu option enables you to download the extended linguist LQA report in Excel format.

    In addition to information displayed in the standard LQA report, this report contains the Extended table tab with these column headers:

    • ID – Segment ID.

    • Source – Source text.

    • Target – The final version of the target text with information who completed it and when.

    • LQA errors – Type and severity of an error and the workflow stage at which it has been reported.

    • Comment.

    • Corrector changes – Changes made to the target segment by the user assigned to the next workflow step.

    • Last revision – Changes made to target segment after rollback to the translate workflow step.

  • trash-solid.svg Delete – remove an item from the list.

    Notice

    This option enables you only to delete the relevant report from the user interface. It will not cause the deletion of LQA errors listed in the report. These errors will still be stored on server and can be listed in another LQA report.

    To delete LQA errors from the server, in XTM Workbench, delete relevant LQA errors from the LQA docked panel. For details, see Deleting LQA errors in XTM Workbench.

    After the project revision, the Per language report will be overwritten with the new data. In case of the Per file report, a new report with changed data will be generated in addition to the previous one.