About Command Center
Contents
Introduction (one page)
What is Command Center?
Command Center is the next evolution of Lingoport's globalization and internationalization suite of products. In one simple application:
- Users can configure the location of their code and resource files from a variety of data sources including Github, AWS S3, and BitBucket.
- Command Center and Globalyzer can analyze the code for globalization issues.
- Reports are created showing the summary of the issues in the code.
- Code can be viewed in more detail. Suggestions for globalization compliance are given.
- Customers can identify a wide range of resource file types, configure machine translation and translation management systems and automatically submit files for translation.
- Command Center and Localyzer tracks and verifies the resource files through translation and back to the data source.
- Users in various roles (Administrator, Manager, Developer and Translator) can use the Command Center to manage and view the status of projects.
Diagram
(data sources on the left, command center in the center, TMSs/MTs on the right)
Roles
Command Center requires users to login. Each user created in Command Center is assigned a role that defines the operations that can be completed by the user. There are five roles defined:
- Administrator
- Manager
- Developer
- Translator
- API User
The Administrator user is responsible for:
- Administering users and teams and assigning them to the users and projects
- Installing and updating licenses
- Managing data credentials and assigning them to managers
- Setting up machine translations and translation management systems
The Administrator user can view all the projects in the system. The Administrator user can create and manage projects, but this role should be left to managers.
The Manager is responsible for:
- Creating, managing and running projects
- Creating project tags and tokens
The Manager can only see the projects for the teams or projects assigned to them.
The Developer and Translator can view project status for the projects in their teams, but cannot make any changes to the system.
The API user is for storing tokens. The API user cannot login to Command Center.
Globalyzer Introduction
(short, with links to Gz)
Globalyzer continues to use the the project definition file to determine what rulesets and files to scan.
For more information on Globalyzer scanning see
Localyzer Introduction
(short, with links to Lz) Diagram
Localyzer configuration in Command Center is very similar to previous methods. The user sets up the translation connection and defines the locales, sets up the resource files, and denotes which files to be included or excluded.
For more information about Localyzer, see
- [About Localyzer]
- [Localyzer FAQ]
- [Localyzer Users Guide]
