Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Specify multiple scenarios for the same task type #76

Open
mesztam opened this issue Jan 29, 2020 · 2 comments
Open

Specify multiple scenarios for the same task type #76

mesztam opened this issue Jan 29, 2020 · 2 comments

Comments

@mesztam
Copy link

mesztam commented Jan 29, 2020

Hi,
there is a "type" field on tasks to specify which workflow to use this task (~ translation, localization, proofreading etc). But is there a way to further specify how to execute this task? E.g. if the client asks for "translation", and the supplier supports multiple translation procedures, can the client select which one to apply? E.g. Machine Translation is allowed or not, or what qa they expect etc?

regards,
Tamas

@jcompton-moravia
Copy link

Hi Tamas,

Thanks for bringing up this question; I've posted your question on the GALA "Connect" channel for TAPICC WG1, who came-up with the Task Type paradigm. With regard to the "what QA they can expect" question, is the thinking here that there might be different "service levels" for the same overall task type? Like Translation with Edit, Translation with No Edit, etc. I believe I'm understanding correctly, but I want to confirm.

Thanks!
-Jim

@mesztam
Copy link
Author

mesztam commented Feb 5, 2020

Hi Jim,

By QA expectations, I mean if the client needs a quick&dirty translation, or translation&proofreading, or even a certificate that the translation matches the original one (for official texts like certificates or so). Right, maybe these can be modeled by standardized additional task types.

The other thing that is in my mind that the same customer may send you different kinds of texts (legal documents, user’s manual, resources from software, internal documents etc), and the task type is always “Translation”, but they probably all need different kinds of TMs/termbases (stored at the Vendor/LSP, so not file-based and attached to the TAPICC project), are probably sent to different vendors, have different pricing etc. And I don't see how this could be standardized. E.g. in COTI, there is an action to query the available "workflows" (supported by the TMS), and when creating the project, you can specify which workflow to use.

regards,
Tamas

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants