Under Community Review

Integrate a query sheet as part of each project

Hi team,

it would be great to have a query sheet that all translators could share within each project. It could be a separate tab for example.

That way, if a translator has a query, everyone else will also see it and there will be no duplicates. It would also ensure that all languages receive the query replies, not only the translator who asked the query.

Vera Malysheva
Parents

  • Thanks, Vera, for raising the idea. Could you elaborate what a query sheet is specifically in your case? You mean like an Excel?

    Just a note, that we have plans on our roadmap to build out native query management functionality.

  • in reply to Luis Lopes

    That's great news! Right now we use an Excel sheet, but I don't think that the optimal way to manage queries. My idea would be to add a tab to the Project view like so: 

    Screenshot of Trados Enterprise Project view with a new 'Queries' tab added in red handwriting next to existing tabs like Dashboard, Stages, Workflow, Reports, Costs, Files, Task History, Settings, and Notes.

    And it would list all the queries the translators have posted. It would pull the data from the online editor, so you would be able to see what segment, what file and what context the query was posted in.

    For the translator view, perhaps they could post their queries from within the Online Editor in a separate tab, same as a segment-specific comment. And then when the replies come in, they'd be able to see that in the Query tab as well, as well as filter for segments with queries.

    Close-up view of Trados Enterprise Online Editor toolbar with a new icon circled in red, indicating the addition of a 'Queries' feature.

    Other nice to haves would be:

    • Make it part of the QA check - if a query is still open, files can't be delivered. The translator has to tick a box next to the query that says "Query reply implemented" to confirm they've seen the reply and implemented it.
    • Add an option to mark a query as language-specific OR applicable to all languages. So that the PM can decide, is this something that all languages need to look at and implement (example: source errors), or is it just for the language that asked the query
    • Add this as a datapoint to the Report functionality - so that we can see how many queries get asked for what types of projects, and how long it takes to get replies.
    • Give the PM the option to assign queries to be answered by other users, such as software developers for software L10n
  • in reply to Vera Malysheva

    Thanks, Vera. You should become a Product Manager ;), because it goes along the exact lines we are thinking of.

    I can't give any timelines right now, and certainly not in 2023, but it's something we are looking at Slight smile

  • in reply to Luis Lopes

    Thank you! I enjoy this kind of topics so I'm happy to give feedback :)

  • in reply to Luis Lopes

    Hi Luis,

    Any updates on when something like this may be added? This would be super helpful for our linguists.

    Thanks,

    Russell

Comment Children
No Data