IMPORTANT MESSAGE: For the time being you will not be able to download or upload apps through the RWS AppStore.
We apologise for the inconvenience and will update the community when the situation changes. For the time being please use the Private AppStore.

Recommended size for Projects created through the API

Hi,

When developing an integration with SDL Managed Translation, what are SDL's recommendations regarding Project size and batching? How many files per project? What recommended word volume per project?

Thanks

Fred

Parents
  • Hi Fred

    There are no best practices with batch sizes, as it will vary by customer depending on their service level agreements with the translation vendor. For example, if the SLA is 24 hours, then the integration will need to provide many projects, each with a few files, so that those projects can be shared out across multiple translators. If the SLA is 5 days, then a single project with many files will be sufficient to send to one translator. Industy standards say 1500-2000 words translation per translator per day (depending on content type), so you would map that back to what the content is, in what format, and how that could be seperated.

    My advice would be to include a batch mechanism in the integration configuration page, allowing customers to make their own choice depending on the use-case and SLA. How this functions will also depend on the source content system and how it manages content files. For example, a PIM system may give you the ability to set batching based on number of products - thus a user sending 25 products with a batch set to 10, would create 3 files for translation (2 files with 10 products, 1 with 5 products). This scenario also suggests all 3 files go into one project, so again you might want to think about multiple batching mechanisms - one for file content, one for files in a project.
    A document repository would be less flexible, as its unlikely you would want to split word documents up through an integration, more likely build functionality into the UI to allow users to choose 1 or many files at project creation.

    Nigel
Reply
  • Hi Fred

    There are no best practices with batch sizes, as it will vary by customer depending on their service level agreements with the translation vendor. For example, if the SLA is 24 hours, then the integration will need to provide many projects, each with a few files, so that those projects can be shared out across multiple translators. If the SLA is 5 days, then a single project with many files will be sufficient to send to one translator. Industy standards say 1500-2000 words translation per translator per day (depending on content type), so you would map that back to what the content is, in what format, and how that could be seperated.

    My advice would be to include a batch mechanism in the integration configuration page, allowing customers to make their own choice depending on the use-case and SLA. How this functions will also depend on the source content system and how it manages content files. For example, a PIM system may give you the ability to set batching based on number of products - thus a user sending 25 products with a batch set to 10, would create 3 files for translation (2 files with 10 products, 1 with 5 products). This scenario also suggests all 3 files go into one project, so again you might want to think about multiple batching mechanisms - one for file content, one for files in a project.
    A document repository would be less flexible, as its unlikely you would want to split word documents up through an integration, more likely build functionality into the UI to allow users to choose 1 or many files at project creation.

    Nigel
Children
No Data