Export documents and other files on server

Some documents and reports can be exported automatically without setting specific options. All you need to set is the path and the name of the documents. Then, in a project created from a project template, memoQ server can export the documents and reports automatically.

This works for the following:

  • Exporting original source documents on the server
  • Exporting target (translated) documents on the server
  • Exporting LiveDocs corpora in XLIFF files on the server (available after project wrap-up only)
  • Exporting quality assurance (QA) reports on the server. A QA report has the statistics of automated warnings about the translation.

How to get here

  1. Open Resource console. Choose Project templates.

    Online projects only: Use an online template for this. Choose your memoQ server at the top of Resource console. Click Select.

  2. Select the project template to which you want to add the automated action. Right-click the selection, and click Edit.

    Online projects only: This action isn't available in local projects. If the eye is closed in the top right corner of the Edit project template window, click it.

  3. In the Edit project template window, choose Automated actions. Click the Project automation tab if you don't see it at first.

  4. Under Available triggers, click an event when you want memoQ to start the automated action. You may need to run this after translation and review are finished. The best event here is After project wrap-up.

    To export LiveDocs corpora, you need to choose a project-level event. The best one here is After project wrap-up.

  5. Next to Actions added to the selected trigger, click the + sign. The Select actions you want to add to the trigger window appears.

  6. Choose one of the following:

    • Export source documents on server
    • Export target documents on server
    • Export QA report on server
    • Export LiveDocs corpora on server (available after project wrap-up only)

    The corresponding settings window appears.

    If you can't add this action because it's already there: Under Actions added to the selected trigger, click the same action. Next to the list, click the Settings  button. The corresponding settings window appears.

Export source documents on server

Export target documents on server

Export LiveDocs corpora on server

Export QA report on server

What can you do?

Under Export path rules, set up the folder and name of the exported files. You can use placeholders, so that memoQ server takes the name from the name of the project, the date or time when the file was created, the project languages, and so on. memoQ fills in the placeholders with actual details in ongoing projects that are created from this project template.

There is a fixed main folder: memoQ server exports the document to the project's file store. This is a folder on the server. Only a system administrator can change the location of that folder.

Normally, memoQ server saves the exported files in one of the following folders, depending on the content type:

  • Source documents: Imported source documents, and the inside folder - if a folder structure was imported originally
  • Target documents: Target documents, and then a folder for the target language, then the inside folder (if a folder structure was imported)
  • LiveDocs: LiveDocs corpora
  • QA report: QA reports

The default names are the following for each file type:

  • Source documents: The original file name
  • Target documents: The original file name (because the document is already exported in a subfolder for the target language)
  • LiveDocs: Name of the corpus, then the date and time when the corpus is exported
  • QA report: Name of the project, then the date and time when the report is exported

You can change this: You can add folders to the path, or you can use different placeholders in the name. You can also use these placeholders in the names of the folders. Don't change the main folder.

  • RelativePath: Use this if a folder structure was imported in the project. This contains the subfolder within the original folder where the document is. For example, if you import a folder called D:\Documents\ToTranslate, and the ToTranslate folder contains an ENG subfolder, then the RelativePath for the documents in the ENG folder will be ENG.
  • OriginalFileNameExt: The name and extension of the original document. Example: if the original document is called ToTranslate.docx, OriginalFileNameExt is ToTranslate.docx.
  • OrigFileName: The name of the original document without the extension. (It's also called a file type in Windows.) Example: if the original document is called ToTranslate.docx, OrigFileName is ToTranslate.
  • OrigFileExt: The extension of the name of the original document (DOCX, HTML, XML, PDF etc.). (It's also called a file type in Windows.) Example: if the original document is called ToTranslate.docx, OrigFileExt is docx.
  • Project: Contents of the Project field of the project. This is not the project name.
  • Client: Contents of the Client field of the project. Normally, the name of the end-user of the translation.
  • Domain: Contents of the Domain field of the project. Normally, the narrower subject or the genre of the source documents.
  • Subject: Contents of the Subject field of the project. Normally, the subject field of the source documents.
  • ProjectName: The full name of the project. memoQ and memoQ server use this name to identify the project.
  • LiveDocsName: LiveDocs export only. The name of the LiveDocs corpus.
  • MajorVersion: Source and target documents only. The first version number of the document. This is the version of the source text. If the source document doesn't change during a project, it stays 1.
  • MinorVersion: Source and target documents only. The second version number of the document. This is the version of the translation. This changes a lot of times during a project: When a translator or a reviewer delivers the document; when it's updated from a bilingual document; before or after the document is pre-translated or X-translated; or when someone manually creates a snapshot.
  • SrcLangIso2: Two-letter code of the source language of the project.
  • SrcLangIso3: Three-letter code of the source language of the project.
  • DocTrgLangIso2: Source and target documents only. Two-letter code of the target language of the document. For a document, there can be only one. For the entire project, there can be several.
  • DocTrgLangIso3: Source and target documents only. Three-letter code of the target language of the document.
  • YYYY: The year when the file is exported, in four digits.
  • YY: The year when the file is exported, in four digits.
  • MM: The month when the file is exported, in two digits.
  • DD: The day when the file is exported, in two digits.
  • HH: The hour when the file is exported, in two digits.
  • NN: The minutes when the file is exported, in two digits.
  • Translator: Source and target documents only. Name of the user who got the document in the Translator role.
  • Reviewer1: Source and target documents only. Name of the user who got the document in the Reviewer 1 role. If there was no Reviewer 1, this is empty.
  • Reviewer2: Source and target documents only. Name of the user who got the document in the Reviewer 2 role. If there was no Reviewer 2, this is empty.

When you finish

To add the action to the project template: Click OK.

Nothing will be exported when you click OK: To export bilingual documents automatically in an ongoing project: Create a project from this project template, and start working on it. Check the output folder for exported files.

To return to the Edit project template window, and not add an action to the project template: Click Cancel.