|Setting up GlobalSight|
|Jump to: Document Library|
| Logging in|
| Setup Overview|
Setting up Users
Setting up Locale Pairs
Setting up Activity Types
Setting up Permission Groups
Importing Translation Memories
Creating Translation Memory Profiles
Setting up Project Templates
Creating Localization Profiles
Creating File Profiles
Converting Content to GXML
Setting up Attributes
Setting up Desktop Icon
Setting up Additional Features
Once GlobalSight has been installed, the system is set up by administrators so that users can begin using it for their project work.
You can log in as:
Your GlobalSight homepage opens, showing links to all of the administration and job-related tasks that you have the permission to see.
Follow the FileSystem Guide from left to right to move from one step of the process to the next.
To open the FileSystem Guide, select Guides->FileSystem.
You can find the same options under Setup in the top-level menu and in the Quick Links.
All of the settings needed are condensed into an easy-to-use File Profile that the user selects when creating a new translation job.
Starting work in GlobalSight means creating a company.
Companies can be different clients of an LSP, or an organization that uses the system internally only.
You can use the default user accounts provided or create your own.
A locale pair consists of both a source and target language.
You can use the default locale pairs provided or create your own.
Activity types are the various tasks that users perform in a translation workflow.
Activity types are the same as "Human Steps" in WorldServer.
You can use the default activity types provided or create your own.
You can create different currencies and assign conversion factors for the US dollar (USD).
Since the conversion factor is never a constant value, most companies do not rely on the value configured in GlobalSight.
Most companies use the system to set the currency only.
You can set up rates for each particular activity.
Rates are similar to Cost Models in WorldServer. The main differences are:
|Each rate is associated with a specific locale pair||Each Cost Model can consist of multiple locale pairs|
|Each rate is associated with a specific activity type. You can therefore assign different rates to different activity types within a single workflow||Cost Models are associated with and are assigned to a project, rather than a human step|
|You cannot configure the number of match ranges and the range values. The configuration is, however, the same as that in the Trados workbench||You cannot configure the number of match ranges and the range values|
Permission groups are used to grant restricted access to groups of users.
Permission Groups are similar to User Types in WorldServer.
You may not need to configure any permission groups, since GlobalSight provides a number of them. You can edit the settings of the permission groups provided.
A Translation Memory (TM) is a database that collects text or other content that has been translated previously.
The TM stores both the source and target text, allowing the same translation to be used again.
You can import a TM into GlobalSight for use in your project.
For information on TMs in general, see Managing TMs.
A Translation Memory Profile (TM profile) specifies the TM to be used.
The TM profile also sets the segmentation rules, reference TMs, penalty rules and various leverage options.
You can import terminology or glossaries for use in your project.
In GlobalSight, a project is a template that specifies:
You can create workflows for managing jobs.
You can define the actions that can be performed on the files using activity nodes.
The localization profile ties all of the parts of the job together.
The localization profile defines:
For example, you can create a localization profile for the translation of your website or your technical documentation.
The file profile is configured with all information needed for users to submit jobs using the Desktop Icon.
The file profile is very similar to the localization profile. The main difference is that it also includes the source file format and the encoding.
Each file profile is a specific combination of:
All content is converted to a common format called GXML (GlobalSight XML) when files are imported as part of a job.
The content is converted before looking up the TM or terminology.
Exporting converts the GXML files into their final output formats.
Exporting also puts the files on the file system for download.
Attributes are an extra set of metadata that users can add to a job.
You can add attributes to the job screen in the form of:
You can then report on attributes, once they are selected in the job.
Log back in to see Create Job under Data Sources on the home page. You can also click Data Source->Create Job.
New features are added as part of each GlobalSight release.
Instructions for installing and setting up are provided as needed.
| Document Library: Latest Versions|
Installing GlobalSight | Installing GlobalSight on Windows | Installing GlobalSight on Ubuntu | Installing Third-party Components for GlobalSight on Windows | Installing Third-party Components for GlobalSight on Ubuntu | Installing the GlobalSight Desktop Icon
Developing GlobalSight | GlobalSight Architecture | | Getting the Code | Building and Deploying GlobalSight | GlobalSight Developer’s Guide | Setting up the Development Environment | Debugging GlobalSight | Designing the GlobalSight Adapters | GlobalSight Web Services API | Using the GlobalSight Web Services API Test Tool | Using the GlobalSight CVS Connector | Connecting to a CVS with the GlobalSight Desktop Icon