Idea Delivered Partially

User report generation

A section or feature that allows us to generate data of each translator/ post-editor working on TMS.

Purpose:

1. To generate monthly report of translator’s/post-editor’s and assess their productivity vs content they translate/post-edit.
2. To get a quick overview of their work status and assigned task.

Sneha Bhave
Parents

  • Hi All,

    There are a couple of datasets available via Custom Reporting that provides some of the metrics requested in the idea description. I've moved the status to "Idea Delivered Partially" until we have clarified if any further data points are required beyond what is currently available.

    The Task Status dataset provides task level metrics, including word count, actual duration (the difference between the task creation and completion dates), and assignees. This allows you to measure the work performed by a linguist - the pivot table, below, is intended to give an example of what can be achieved. Here, I am showing the total words and total actual duration for each user (taking the hashed email address) by task type and target language. Filtering can be used to specify a date range, if you are only interested in seeing tasks completed within a given time period, for example.

    You could create a similar visual to show work currently assigned to a linguist by filtering on entries with a task status of "In progress" and "Pending".

    Note: we don't currently hold assignment data for tasks that haven't yet been created. It isn't therefore possible to report on work that may be assigned to a linguist in the future.

    Pivot table showing task word count and actual duration in hours by user email hashed, task workflow name, and target language code. Columns for Editing and Translation in languages zh-CN, sv-SE, pl-PL, and ko-KF.  

    The Translation Productivity Assessment dataset provides metrics specifically for linguistic tasks performed in Trados, including the number of segments and edit distance. In the example chart below, I am reporting on the number of segments handled by each linguist for translation tasks (using the hashed email address) and comparing this with the average edit distance for those segments, represented by the line series. 

    Bar and line chart displaying the sum of segments and average edit distance by translator user email hashed. Bars represent segment count and the line shows edit distance for each user.

    More details for these datasets are available in the online documentation here.

    Cheers,

    Ian

  • in reply to Ian Parnell

    Hi Ian,

    Is actual duration looking at the date the linguist actually started the work or the just the creation of the task/assigned date?

    Thanks,

    Russell

  • in reply to Russell Banton

    Hi Russell,

    the actual duration compares the task creation date and completion date and calculates the difference (in minutes) between those two values.   

Comment Children
  • in reply to Ian Parnell

    Hi Ian,

    Is there a way to get the duration that someone works on a task? Actual duration is not a helpful metric, especially if a project is created on a Friday, but not picked up until Monday. We are trying to see linguistic throughput and with the "actual duration" we are having linguists who average less than 10 words per hour when trying to find words per hour.