Difference between revisions of "Localyzer FAQ"
(→On-Boarding) |
|||
| Line 16: | Line 16: | ||
Each tab has a job setup during configuration. On-boarding a new job consists in copying an exiting job and configuring a set of xml files. |
Each tab has a job setup during configuration. On-boarding a new job consists in copying an exiting job and configuring a set of xml files. |
||
| − | [[On Boarding the Automation Job]] |
+ | *[[On Boarding the Automation Job]] |
| − | [[On Boarding the Nightly Job]] |
+ | *[[On Boarding the Nightly Job]] |
| − | [[On Boarding the Prep Kit Job]] |
+ | *[[On Boarding the Prep Kit Job]] |
= The LRM File System = |
= The LRM File System = |
||
Revision as of 22:18, 30 March 2015
Installation
Configuration
On-Boarding
Projects can be on-boarded one per repository, after a group has been licensed. Many groups can be licensed: It is important to determine under which group a project must reside.
- The '1 - Automation' tab contains on-boarded jobs which generate the status of the project and pushes it to the dashboard, and pseudo-localizes resource files if necessary. These jobs tend to run whenever files are pushed to the repository for the project.
- The '2 - Nightlies' tab contains on-boarded jobs which run every day or every night and provide an update to the dashboard and an email to a set of recipients based on the configured frequency.
- The '3- PrepKit' tab contains on-boarded jobs which are triggered by a human intervention to send the kits for translation based on the configured translation endpoint.
Each tab has a job setup during configuration. On-boarding a new job consists in copying an exiting job and configuring a set of xml files.
The LRM File System
- Introduction to the LRM File System
- Prepping a Kit
- Acquiring Translated Files
- Importing a Translated Kit
