Difference between revisions of "Step by Step Project Creation"

From Lingoport Wiki
Jump to: navigation, search
(Getting Started)
Line 7: Line 7:
 
# For Globalyzer projects, the Project Definition File must be available in the repository or on the Command Center System.
 
# For Globalyzer projects, the Project Definition File must be available in the repository or on the Command Center System.
 
# For Localyzer projects:
 
# For Localyzer projects:
## the Translation Management System or Machine Translation engine must be defined
+
** the Translation Management System or Machine Translation engine must be defined
## The locales to be translated to
+
** The locales to be translated to
## The resource file types such as .properties or .json and the naming format for the source files.
+
** The resource file types such as .properties or .json and the naming format for the source files.
## Include and Exclude folders for locating the resource files.
+
** Include and Exclude folders for locating the resource files.
## Any other configuration such as custom scripts that should be in the Command Center System.
+
** Any other configuration such as custom scripts that should be in the Command Center System.

Revision as of 17:28, 30 August 2023

Getting Started

Only users that with Manager or Administrator roles can create projects. Other users can view created projects.

Before creating a new project, there are a few items that are needed.

  1. The Data Source that the project will be using, such as GitHub, Subversion or Azure. Command Center will not allow projects to be created if there are no Data Sources available. Additionally, the specific branch being used in the repository is needed.
  2. For Globalyzer projects, the Project Definition File must be available in the repository or on the Command Center System.
  3. For Localyzer projects:
    • the Translation Management System or Machine Translation engine must be defined
    • The locales to be translated to
    • The resource file types such as .properties or .json and the naming format for the source files.
    • Include and Exclude folders for locating the resource files.
    • Any other configuration such as custom scripts that should be in the Command Center System.