Difference between revisions of "Step by Step Project Creation"
(→Prerequisites) |
|||
| (17 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | = |
+ | = Table of Contents = |
| + | [[Data Source Credential for the project |Step 1:Data Source Credential for the project]] |
||
| − | Only users that with Manager or Administrator roles can create projects. Other users can view created projects. |
||
| + | [[Choose a Repository|Step 2:Choose a Repository]] |
||
| − | Before creating a new project, there are a few items that are needed. |
||
| − | # 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. |
||
| − | # For Globalyzer projects, the Project Definition File must be available in the repository or on the Command Center System. |
||
| − | # 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. |
||
| + | [[Name The Project and Type |Step 3: Name the Project]] |
||
| + | [[Creating a Globalyzer Project |Creating a Globalyzer Project - Step 4: Globayzer Lite Definition File]] |
||
| − | Select the [[File:LingoportIcon.jpg|50px]] to get to the '''Projects''' page and select the [[File:CreateIcon.jpg|30px]] to '''Create new project'''. The first step in the process will come up. |
||
| + | [[Creating a Localyzer Project| Creating a Localyzer Project - Step 5: Which MT or TMS will Localyzer use ]] |
||
| − | [[File:Step1DataSource.jpg|700px|center]] |
||
| + | [[What are the Localyzer locales| Step 6: What are the locales Localyzer is acting on? ]] |
||
| − | When Manager users are created, Data Source Credentials are assigned. If the Manager does not have any Data Source Credentials assigned, the process will fail with the error: '''Must have access to at least one credential before creating a project'''. Contact an Administrator to get credential access. |
||
| + | [[Resource File(s) Format| Step 7: Resource file formats]] |
||
| − | Select '''Next''' |
||
| + | [[Include and Exclude Patterns|Step 8: Set up optional include or exclude patterns]] |
||
| − | Next Step [[Choose a Repository|Step 2:Choose a Repository]] |
||
| + | [[Optional Localyzer Settings|Step 9: Optional Advanced Localyzer Settings]] |
||
| − | [[Name The Project and Type |Step 3: Name the Project]] |
||
| + | [[Grant Users and Teams Access | Step 10: Grant Users and Teams Access]] |
||
| + | = Prerequisites = |
||
| + | Only users that with Manager or Administrator roles can create projects. Other users can view created projects if they have been granted access. |
||
| + | Before creating a new project, there are a few items that are needed. |
||
| + | # The licensing needs to be valid for Globalyzer and/or Localyzer depending on the type of projects to be created. |
||
| + | # The System Email Sender needs to be set up. |
||
| + | # 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. A Manager creating the project must have access to the data source credential. Additionally, the specific branch being used in the repository is needed. |
||
| + | # For Globalyzer projects, the Project Definition File must be available in the repository or on the Command Center System. |
||
| + | # 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. |
||
| + | This example uses a GitHub repository for the data source. If using a different data source, refer to the sections that describe how to configure and create projects using those data sources. |
||
| − | [[Step by Step Project Creation |Step 1:]] |
||
| + | |||
| − | '''Next Step: [[Choose a Repository|Step 2:Choose a Repository]]''' |
||
| − | [[ |
+ | [[Data Source Credential for the project |Step 1:Data Source Credential for the project]] |
| + | |||
| − | [[Creating a Globalyzer Project |Creating a Globalyzer Project - Step 4: Globayzer Lite Definition File]] |
||
| + | [[Command_Center_User%27s_Guide#Projects_Overview| <== Back to Projects Overview]] |
||
| − | [[Creating a Localyzer Project| Creating a Localyzer Project - Step 5: Which MT or TMS will Localyzer use ]] |
||
| − | [[Grant Users and Teams Access | Step 10: Grant Users and Teams Access]] |
||
| − | [[What are the Localyzer locales| Step 6: What are the locales Localyzer is acting on? ]] |
||
| − | [[Resource File(s) Format| Step 7: Resource file formats]] |
||
| − | [[Include and Exclude Patterns|Step 8: Set up optional include or exclude patterns]] |
||
| − | [[Optional Localyzer Settings|Step 9: Optional Advanced Localyzer Settings]] |
||
| − | [[Grant Users and Teams Access | Step 10: Grant Users and Teams Access]] |
||
Latest revision as of 15:31, 5 June 2024
Table of Contents
Step 1:Data Source Credential for the project
Creating a Globalyzer Project - Step 4: Globayzer Lite Definition File
Creating a Localyzer Project - Step 5: Which MT or TMS will Localyzer use
Step 6: What are the locales Localyzer is acting on?
Step 8: Set up optional include or exclude patterns
Step 9: Optional Advanced Localyzer Settings
Step 10: Grant Users and Teams Access
Prerequisites
Only users that with Manager or Administrator roles can create projects. Other users can view created projects if they have been granted access.
Before creating a new project, there are a few items that are needed.
- The licensing needs to be valid for Globalyzer and/or Localyzer depending on the type of projects to be created.
- The System Email Sender needs to be set up.
- 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. A Manager creating the project must have access to the data source credential. Additionally, the specific branch being used in the repository is needed.
- For Globalyzer projects, the Project Definition File must be available in the repository or on the Command Center System.
- 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.
This example uses a GitHub repository for the data source. If using a different data source, refer to the sections that describe how to configure and create projects using those data sources.
