Views
| Related Documentation: |
You can use GlobalSight for the various translation project tasks carried out by Project Managers, translators, reviewers, DTP engineers, clients and so on.
The prerequisite is that the project has been set up by the administrator, in cooperation with the Project Manager. For more details, see Setting up GlobalSight.
Contents |
Project Overview
Project Managers or clients request translations by creating translation jobs. You can follow the progress in My Jobs.
The Project Manager assigns the work to the Project Team in the form of activities - translation, review, DTP and so on. You can follow the progress in My Activities.
Both jobs and activities have a defined status that changes as the work progresses.
The project process below is a standard one that suits most common cases. Projects can be customized to suit the work in question.
Planning
Project Managers plan the project work by creating jobs, quoting and then dispatching jobs to the project team.
Project Managers can create jobs themselves or clients can also do it themselves.
| Project Managers or clients request translations by creating jobs | |
| ||
| Project Managers or clients add any extra information needed, after submitting the job | |
|
| ||
| Project Managers send a quote for the job to the client | |
|
| ||
| Clients check the quote and approve it | |
|
| ||
| Project Managers dispatch the approved job to the project team |
Implementing
Project Teams - translators, reviewers, DTP engineers and so on - then carry out the related project activities.
Project teams are informed of the jobs that have been dispatched by the Project Manager or client.
A standard workflow involves the following activities:
| ||
|
| ||
| Translators translate the content | |
|
| ||
| Reviewers validate the translation and add comments | |
|
| ||
| Translators check the review comments added by the reviewer and make the review changes | |
|
| ||
| Reviewers validate the content corrected by the translator | |
|
| ||
| DTP engineers restore the original file format | |
|
| ||
| Reviewers check the DTP version | |
|
| ||
| DTP engineers make review changes as needed | |
|
| ||
| Translators check the review comments added by the LSO reviewer and make the LSO review changes | |
|
| ||
|
Managing
Project Managers follow up the ongoing project work to react to changes and keep the process moving smoothly from one phase to the next.
| Project Managers follow up ongoing jobs | |
|
| ||
| Project Managers make changes to ongoing jobs as the work progresses |
Finalizing
Project Managers retrieve the final files and then archive the job.
| Project Managers retrieve the final files and send them to the end user | |
|
| ||
| Project Managers archive the job as soon as they are complete |
Job and Activity Status
Each job and activity has an associated status that updates as the work progresses.
You can search by status when finding your jobs and activities.
Job Status
| Status | Explanation |
|---|---|
| Pending | The Project Manager has uploaded the job.
The job is being created and can have a status of:
|
| Ready | The job has been created successfully and is ready to be dispatched |
| In Progress | The job has been dispatched to the resource |
| Localized | The workflows have been completed and are ready to be exported.
Jobs created online or with Desktop Icon first go to Localized and then automatically to Exported when the last workflow finishes Jobs created using Data Sources->Upload go to Localized when the last activity finishes. The status changes to Exported once the workflow is exported manually |
| Exported | The related workflow(s) has been completed |
| Archived | The job has been archived by the Project Manager and can be removed |
Activity Status
| Activity Status | Explanation |
|---|---|
| Available | The activity is ready for the resource to accept |
| In Progress | The resource has accepted the task and started the work |
| In Progress (GS Edition) | Not in use |
| Finished | The resource has completed the activity |
| Document Library: Latest Versions |
|
About GlobalSight | System requirements | Setting up GlobalSight | Upgrading GlobalSight | Comparing GlobalSight with WorldServer | GlobalSight on-line help |
|
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 |
|
Using GlobalSight | Managing GlobalSight Projects | Translating with GlobalSight | Reviewing with GlobalSight | Using the 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 |
|
Help and support |