Automated Project Creation

Available for

Project Managers
Team, Ultimate and Enterprise Editions

Get in touch with Sales for licensing questions.

Automated Project Creation rules allow the configuration of how Memsource monitors specific folders and creates new projects if new or updated content is detected in them. This provides full process automation; analysis, pre-translation, assignment to Linguists/Vendors, and the e-mailing of notifications.

As soon as a project status changes to Completed either manually or by Project Status Automation rules, the translated files are sent back to the Online Repository into newly created subfolders identified by language codes (en, es, ja, etc.)

Set up Automation Rules

Prerequisites:

At least one connector and one service in a Memsource account.

Follow these steps:

From the Setup page, click Automated Project Creation.

The Automated Project Creation page opens.
Click New.

The Create Automated Project Settings page opens.
Select the source and target languages that automatically created projects will be associated with.
Choose the Remote Folder to monitor for new or updated content.

The contents of the folder is listed in the main window.
Select specific files to be monitored.

Not all options are available on all connectors. See the Use Cases section of the specific connector documentation:
- If none selected, the entire folder is monitored for a change or new files.
- Include subfolders to enable the monitoring of the selected folder and its subfolders.
Depending on the pathname of the required target files, set Export completed files to and Target Subfolder Path fields.

See Set Target Files Pathname for more information.
Designate a Processed subfolder.

Files imported to Memsource are moved to this folder providing visibility on which files are being processed. If disabled, source files stay in their original folder.

If this option is disabled and File Renaming is not used, original documents can be overwritten by their translations (depending on repository).
Set a frequency for how often Memsource should check for new content in the designated folder.
Choose required Service.
To differentiate between projects coming from different automation rules, use a Default Project Name to define the automatically-generated names of projects.

The macro {filename} can be used in the Project's title. If multiple filenames are used in the project's name, only the first filename will be used.
Set Default Project Owner.

Default Project Owner will always be notified when a new project is created using automation rules.
Customize Email Templates used for notifications if required.

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

Automatic Creation of New Projects from Online Repositories

On the Automated Project Creation page, Memsource displays currently available rules, connection status and the last checked and next check dates and times.

If new content is identified, new projects are created with either default settings or settings taken from the selected project template.

Set Target File Pathnames

Relative to the source file the target files can be exported to:

Same folder

If specific files are selected, then select Source file folder for Export completed files to and keep the Target Subfolder Path empty.Not supported if the entire folder is monitored.
Language subfolder

Always keep the Target Subfolder Path empty.

If specific files are monitored, then select Target language subfolder for Export completed files to.
Any folder

If specific files are monitored, then select Target language subfolder for Export completed files to.

Specify the folder name in the Target Subfolder Path:
- Use {targetLang} macro to represent target language.
- Subfolders can be created within the source folder.Available for Azure, 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.
  
  Available for Azure, FTP, SFTP, Dropbox, Google Drive, Box, OneDrive, Git, GitHub, GitLab, and SharePoint.The leading / in GIT-based repositories represents the root of the repository (where .git folder is located) and starts after the branch name. The target files will be stored in the same branch. Storing the files in a different branch is not supported.
- Use .. to refer to the parent folder.
Tip

Examples

If the source file is /files/loc/ui.properties and the target langauge is German (Germany):
- translations/{targetLang} will create /files/loc/translations/de_de
- /files-{targetLang}/loc will create /files-de_de/loc/<filename>
- ../{targetLang} will create /files/de_de/<filename>
Name of the actual file is based on the File Renaming set in Project settings.

Disable Automated Project Creation

There are three ways to disable APC:

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

When a connector used as part of the Automated Project Creation rules detects three or more consecutive instances of a project not being created when it should be, notification is sent to affected Memsource users.

Zip File Support

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).