Automated Project Creation

Setting up and Using Automated Project Creation

The Automated Project Creation rules allow users to configure the way in which Memsource monitors specific folders and creates new projects whenever new content is detected in them. This is powered by the Memsource connectors. The logic of the project creation process is similar to that followed when the Automation Widget is used.

Note: Automated Project Creation is only available for users with the Team, Ultimate, or Enterprise editions.

Setting Up the Automation Rules

To use this feature, you will need at least one connector and at least one service created in your Memsource account. After you have established them, you can follow the instructions below:

Automated Project Settings

  1. In your account, go to Setup, Automated Project Creation, and click on New.
  2. Set up the source and target languages. Note that any project created using Automated Project Creation will have these languages specified automatically.
  3. Choose the Remote Folder which should be monitored for new or updated content.
    Please note that only some folders will be available for certain repositories (For example, Posts and Pages for Drupal and Wordpress).
  4. Designate a Processed subfolder. The files imported to Memsource will be moved to this folder. This will help you to see which files are currently being processed.
    If this option is disabled, the source files will stay in their original folder. However, they will not be picked up multiple times.
    Important: if this option is disabled and File Renaming is not used, the original documents can be overwritten by their translations (depending on the repository used).
  5. Specify a Target Subfolder Path for the translated files exported from Memsource.
    • You can use {targetLang} for the folder's name.
    • You can create subfolders within your source folder. For example: target/{targetLang} will result in source/target/de' (This option is available for FTP, SFTP, Dropbox, Google Drive, Box, OneDrive, Git, GitHub, GitLab, and Bitbucket Cloud.)
    • For some repositories, an absolute path is available. Begin your path with / to indicate the absolute path. For example: /Output/APC-out/{targetLang} (This option is available only for Azure, FTP, SFTP, Dropbox, Google Drive, Box, OneDrive, Git, and SharePoint.) For GitHub and GitLab an absolute path is available only within the same branch and the same project.
  6. Frequency of the checks can be specified to define how often Memsource should check for new content in the designated folder.
  7. Choose the appropriate Service (similar to the Automation Widget). The service used will determine multiple factors:
    1. Possible language combinations (A single service can be used in multiple Automated Project Creation rules.)
    2. The Workflow steps with which the project will be created.
    3. Project Templates that will be used for the newly created project (including project settings and user assignments).
  8. If you want to differentiate between projects coming from different automation rules, you can use a Default Project Title to define the automatically-generated names of projects. It is possible to use macro {filename} in the Project's title. If multiple filenames are used in the project's name, only the first filename will be used.
  9. The Default Project Owner will always be notified when a new project is created using the automation rules.
  10. You can also customize the Email Templates that should be used for notifications.

Using Automated Project Creation

With the automation rules set, content can now be created in the designated folders. Based on the frequency checks, Memsource will look into the specified folder and identify new or updated content (based on file names, metadata, size, etc.).

Some of the connectors have an additional means of determining new content (for example, the WordPress and Drupal plugins). Please visit our dedicated sections for WordPress and Drupal to learn more about how these plugins work and determine new content. 

Automatic Creation of New Projects from Online Repositories

On the Automated Project Creation page, Memsource will show you the currently available rules and the "last checked" and "next check" dates and times. You can also check the connection status from this page.

Depending on the selected frequency, Memsource will look in the online repository in question, and if new content is identified, new projects will be created either with the default settings or with settings taken from the selected project template. This can lead to the full automation of the process, including analysis, pre-translation, assignment to Linguists/Vendors, and the e-mailing of notifications.

List of Available Connectors

ZIP files are supported:

  • Multiple ZIP files can be imported to one project
  • Translated files are exported back to ZIP files
  • If one ZIP file is imported to multiple targets, the translated files will be exported to multiple ZIP files—one ZIP for each target language—using the target locale code in the ZIP name (for example Pack18.en_us.ZIP).

Automatic Export of Completed Files Back to Online Repositories

As soon as the project status changes to Completed, which can also be achieved using Project Status Automation rules, the translated files will be automatically sent back to the Online Repository into newly created subfolders identified by the language codes (for example, 'en' for English).

Disabling Automated Project Creation

APC can be disabled in 3 ways:

  • Manually in the APC settings
  • Automatically after 90 days of inactivity
  • Automatically after the organization account has been deactivated (at end of the subscription).

Please note that when a connector used as part of the Automated Project Creation rules detects three or more instances in a row of a project not being created when it should be, a notification will be sent to the affected Memsource users.