Individual Project Tasks

Introduction

When a user selects a project name from the Projects page, the Project Overview page comes up with a summary of the project. There are a number of tabs on the top of the page. The tab that is selected is highlighted. For this example the Overview button is highlighted for the Project Overview page.

• Overview - a summary of the project, showing the data source, history, and a summary of Globalyzer and Localyzer configuration
• Globalyzer - a detail of the Globalyzer information including the number of issues found
• Localyzer - a detail of the Localyzer information including the locales and translation status
• Issues - detailed information about the Globalyzer and Localyzer issues
• Logs - report of the various actions performed on the project.
• Configure - allows the user to modify the project.

Analyze Project

[Admin, Manager]

The Analyze Project icon will run the project. When the button is selected, the icon will be shown twirling and a message will come up in the upper left about the job processing.

Overview

[Admin, Manager, Developer, Translator]

Once a project is created, selecting its name will open the Project Overview. Note that the Overview tab on the top is highlighted. The Overview page is a project summary page, showing the Globalyzer and Localyzer summaries and the Project History. Any of the analysis lines are selectable and will open the corresponding logs.

The Analyze project button will run the project.

Globalyzer

[Admin, Manager, Developer, Translator]

The Globalyzer Icon opens the Globalyzer Report page with the details of the Globalyzer analysis.

• Total Remaining Issues - all the issues that Globayzer has identified. This card is selectable and will take you to the Issues page.
• Total Issues Fixed - how many issues have been fixed since the project was created.
• Total Issues Density - number of issues divided by the number of lines of code that were scanned.
• Issues Types Breakdown - What types of issues were found.
• Issues Priorities Breakdown or Issues Severities Breakdown- A list of the severity of the issues. This can be toggled in the Advanced Settings.
• Issue Scans Breakdown - The rulesets used and the items scanned for.

Localyzer

[Admin, Manager, Developer, Translator]

The Localyzer Icon opens up the Localyzer Report page. The Localyzer page has a number of icons on the left side for actions that can be done.

Send kit to translation - send the latest prep kit to be translated at the specified Translation Management System or Machine Translation engine.

Check Import - Check the translation management system to see if translations are available to import.

Deactivate last translation kit - deactivate the last translation kit that was sent. A translation kit cannot be deactivated if any part of it has been imported.

Reset all translation kits - this is used as a reset for the project.

Create project baseline - Set the baseline so that the database can keep trach of translation changes and imports. While creating and configuring the project, it does not have a baseline.

String Manager

[Admin, Manager, Developer, Translator]

String manager provides visibility into each key/value pair managed by Localyzer.

From the search box input text, find strings that match by their values, by their keys, by their filename. Filter strings that need to be sent, or have been sent and are not yet translated, or strings which are fully translated. Sort strings based on the text itself, the key, the filename, or the time it was found.

You can also set some string 'to be reviewed', or 'reviewed', or neither. Certain strings will be marked 'to be reviewed' by the system.

If the user has access to the repository, for instance a developer, A link point the browser to GitHub, GitLab or Bitbucket repository/project/branch/key-value pair. Only users with access to the repository are allowed. Typically, only developers will have access to their repositories. The rationale is to have developers create and maintain the source strings, and if some strings need to be changed, only developers can change them. Localyzer changes the target files with translations, pseudo-translation, context files, or LocalyzerQA type files.

Issues

[Admin, Manager, Developer, Translator]

The Issues icon opens the Issues page and will show all the Globalyzer and Localyzer issues. Once the issues page is open, the issues can be searched, filtered and sorted.

Selecting an issue in the list will show more detail about the issue, including its status, type and priority.

• Go to line in source code - will take the user to the line of code in the repository, for users with repository access.
• Learn more about this issue - will open up documentation about the issue.
• Comments - any comments can be added about Globalyzer issues. They will remain after further analyses.

Project logs

[Admin, Manager, Developer, Translator]

The Console Logs icon opens up the logs to show when the project has been analyzed. Selecting any of the lines will open the log and show more detail.

In this example:

• The user making the change is testAdmin
• The version of Command Center is given
• One setting in the General Settings was changed
  • Tags were modified on the project: FTP to FTP and Build 5

Edit Project configuration

[Admin, Manager]

The Edit icon will open the Edit Project Configuration page. There are several icons on the left side of the page.

- validate the Localyzer configuration finds the resource files.

- make a copy of this project

- refresh the project

- remove the project from Command Center

General Settings

Data Source Settings

Access Settings

Globalyzer Settings

Localyzer Settings

Edit a project

There are multiple ways to get to edit a project.

First, from the Projects page, hover over the project and the Edit button will appear.

Second, select the project name (or the Globalyzer or Localyzer icon) to go to the Overview, Globalyzer or Localyzer page. Select the Configure button on the top to get to the Edit Project Configuration page.

From this page, any of the settings can be changed.

When changes are made and saved, a notice appears at the top of the screen about the project being updated. The project does not run until it is manually run or by an automated task.