Under Community Review

Integrated with WorldServer, highly recommended to enable users to assign Translator and Reviewer from within CMS (KC/Tridion)

Hi Team,

At VMware R&D, SDL WorldServer and KC are integrated so that our localization team pushes the translation job from CMS to WorldServer, which saves efforts to export and import.

However, we have a pain point that we have been hoping to get supported for long where our project managers have to login WS again to assign translator and reviewer after the project is created from CMS. To make it simple, do you think it is possible to add two options as on below mock-up so that we can directly select Translator and Reviewer team when we create the project?

Screenshot of Translation Job Properties in Mozilla Firefox showing fields for Name, Job Scope, Description, Required date, Source language, Translation template, and a dropdown for Translators with 'WELOCALIZE' selected.

Just like those Project Types pulled from WorldServer, that drop-down options are two customized Project Attributes in WorldServer. I ever talked over this with Chip last year and he is fully confident that this can be easily implemented.

Thank you for support and I really expect we have that flexibility to streamline process,

 

Cheers,

Anson

Anson Zhang
Parents

  • Hi  Chip,

    Great to see your updates.

    For companies who are using single vendor to translate everything, it is not a problem and absolutely fine as is. If they are using multiple vendors which is true in most of cases, to them, then, what makes more sense is to assign vendors at creating the project. Else done manually or automatically in any post process after the project gets created is a unnecessary pain point.

    So this has to be done within CMS since users are creating a job within CMS. I know this may or may not be considered in the end and also difficult to tell when, but I do hope to get this resolved - to do or not to do, so that I know what to do else.

    Looking forward,

    Anson

Comment

  • Hi  Chip,

    Great to see your updates.

    For companies who are using single vendor to translate everything, it is not a problem and absolutely fine as is. If they are using multiple vendors which is true in most of cases, to them, then, what makes more sense is to assign vendors at creating the project. Else done manually or automatically in any post process after the project gets created is a unnecessary pain point.

    So this has to be done within CMS since users are creating a job within CMS. I know this may or may not be considered in the end and also difficult to tell when, but I do hope to get this resolved - to do or not to do, so that I know what to do else.

    Looking forward,

    Anson

Children
No Data