memoQ is a powerful translation management system popular among a wide range of users, including enterprises, translation companies and freelancers. BeLazy supports connecting to memoQ servers and memoQ cloud instances through the web interface, memoQweb.

Use cases:

BeLazy supports integration with memoQ through a comprehensive connector that enables seamless translation project management. There are two main use cases where the memoQ integration comes in handy:

  • You have an instance of the memoQ server / memoQ cloud, where you create projects manually or automatically via content connectors or an API, or import packages, and would like these jobs to automatically appear in the business management system.
  • Your customer sends you jobs - packages or online jobs -, and you want to automatically pick them up in your business management system.

BeLazy connects memoQ with any business management system or tracker, and allows:

  • Project and job listing with all details, including analysis and workflow information,
  • Project creation in a business management system or tracker,
  • Linguist assignment monitoring in memoQ, and reassigning linguists in the business management system or tracker,
  • Linguist assignment monitoring in the business management system or tracker, and reassigning linguists in memoQ,
  • XLIFF download and upload (or memoQ package download and upload in the case of linguist accounts) for offline translation workflows,
  • Delivery monitoring and project completion tracking.

Integration type:

The memoQ integration impersonates users through the memoQweb interface using internal APIs. This implementation was chosen because memoQ's proprietary SOAP API only provides admin-level access to everything, and organizations may want to limit access to certain projects or resources. The integration supports both main user roles, i.e. project management and translator.

Requirements:

The memoQ server needs to have memoQweb installed. All memoQ cloud instances come with memoQweb. You need your memoQ username and password with appropriate permissions to access the projects and translation interface. There is no requirement for memoQ's own API.

Expected URL format:

The URL is the URL of memoQweb. In the case of cloud instances, it is https://xx.memoq.com/instance-name, where xx is the cloud server you're hosting and instance-name is the name of your (or your customer's) memoQ cloud instance.

memoQ-specific configuration:

Within memoQ projects or project templates:

Workflow definition: 

As memoQ does not define a workflow, and always allows flexible changes for Translation, Review1, Review2, you need to explicitly indicate in the memoQ project if you want BeLazy to create shorter workflows than three steps. In the first line of the memoQ project's Description field, you need to enter the workflow steps used: a combination of Translation, Review1, and Review2, with the steps separated by comma (e.g.: Translation, Review2 or T, R2). You can populate this information in memoQ project templates to always use the same workflow. If there is no workflow in the first line of the Description, BeLazy will consider this project to have the Translation, Review1, Review2 workflow. You can add other information in the lines below. In the business management system workflow you can have more than three steps, but memoQ only supports three.


Within BeLazy:

Project handling options:

  • Separate projects by languages: If your user has PM rights, by default each memoQ project represents a multilingual project in BeLazy. Enable this option to create separate projects for each target language of the memoQ projects (limited to users with PM rights).
  • Enable changing document status during delivery (recommended): Configure whether BeLazy can change the document's delivery status in memoQ during delivery (limited to users with PM rights).

Analysis weight configuration:

  • Use default weights in BMS: When creating receivable items, BeLazy typically uses analysis weights from memoQ, which are part of the online projects and configured under Options / Miscellaneous / Weighted Counts. If you enable this option, weights will come from your business management system (XTRF, Protemos) instead. Note that for Plunet users, if enabled, BeLazy will just simply ignore memoQ fuzzy match weight categories and instead of weights, will use the right prices from the price lines. This functionality only affects BeLazy's own integrations with commercial business management systems (XTRF, Plunet, Protemos), does not apply if you are working with a tracker or other business management systems.

Analysis creation settings (limited to users with PM rights):

  • Always create new analysis: In case there is no analysis yet for a project, BeLazy will create an analysis report, otherwise it will pick up the existing analysis. Enable this option to create a new analysis report even if an analysis is already available, just to be on the safe side.
  • Receivable options: Configure the memoQ-specific analysis parameters including locked rows, spaces in character counts, homogeneity calculation, repetitions precedence, cross-file repetitions, and tag weights. These parameters will be used for new analysis creation.
  • Payable options: Configure separate analysis parameters for payables if different options are needed from receivables. This way you can for example use homogeneity for the analysis created for translators, but not use homogeneity for the client-facing analysis.

Project exclusion: 

On the second configuration page you can set up project exclusion. The most typical use cases are filtering out memoQ projects created by Plunet or XTRF's own memoQ integration so that no duplicates are created, and filtering out non-launched projects from being visible in BeLazy. The latter leaves time for project preparation before synchronizing and prevents incomplete projects from appearing in your business management system or tracker.

Functionalities and connector-specific information:

memoQ for Project Managers:

  • Unit of acceptance: Project. Documents and document slices are both supported
  • Multiple target languages: Supported with optional separation into individual projects
  • Specialization (Domain, Subject), Client, Project, Workflow: Extracted from project metadata and description field
  • Project exclusion: Supported - can filter out non-launched projects to only pick up projects when they are fully prepared
  • Download files: Bilingual XLIFF files are extracted
  • Delivery: Project completion monitoring and document status changes, uploading finished XLIFF files
  • Linguist assignment: Bidirectional with configurable vendor mapping
  • Vendor creation: Not supported, you have to manually create new vendors in memoQ
  • Project bundling: Supported, document slices also supported (full analysis stored for reference)
  • 2-factor authentication: Not supported
  • Pricing: Not supported - prices are calculated by the business management system or tracker, but weights can come from memoQ
  • Analysis creation: Full analysis control with separate receivable and payable options
  • Project updates: Not supported after acceptance, supported before acceptance.

memoQ for Linguists:

  • Unit of acceptance: Single translation jobs (documents in one language and one workflow step). You can merge these into one project using project bundling.
  • Multiple target languages: Only with project bundling, one BeLazy project in the memoQ linguist scenario is one language pair
  • Project metadata: Not available, as the integration is limited by information on the web interface
  • Project exclusion: Not supported
  • Package download: Package download supported for offline translation workflows
  • Package upload: Package upload supported with .mqback packages for project delivery
  • Delivery: Package-based delivery (segments must be confirmed or proofread for it to work) and project completion monitoring on the memoQweb interface are both supported
  • Linguist assignment: Not applicable - linguist receives assigned work
  • Vendor creation: Not supported
  • Project bundling: Supported
  • 2-factor authentication: Not supported
  • Pricing: Not supported - prices calculated by business management system
  • Analysis creation: Supported

Shared limitations:

  • Only new projects supported, version updates not supported
  • Subvendor workflows not supported (memoQweb limitation)
  • Reverse vendor assignment from slices does not work with XTRF Smart projects

Business management system-specific features:

  • XTRF integration: Automatic username retrieval from Provider information (Main data / System accounts / Username in external system)
  • Only the Plunet integration supports the separate payable and receivable analysis creation as of today

Connector-specific data extracted: See here.


The integration provides comprehensive automation for both project management and translation workflows, with the project manager connector focusing on project oversight and analysis management, while the linguist connector used exclusively by vendors in memoQ specializes in package-based translation processes.