Purpose

Companies, that are organizing translation processes with translate5 often need to delegate translation jobs not only to single persons, but other companies, who sub-delegate them again to other companies, freelancers or their employees.

The purpose of this issue is to offer a possibility to do this.

Overview of the feature

A new system role "job coordinator" is introduced.

A new main translate5 menu tab "Service providers" is introduced.

Job coordinators always should belong to service providers. They can manage all users of a service provider and create sub-service providers.

Users can be assigned as job coordinators to workflow steps of tasks (such as "translation" or "review"). If they are assigned, they are able to assign other users to that workflow step as editors.

Pre-assignment of job coordinators on client level can be done analogous the current pre-assignment of translators.

Job coordinators can add new users to translate5, that automatically belong to the same service provider as they do themselves.

Project overview

A job coordinator can access the project overview.

She/he can not add a project.

She/he sees only projects, that contain tasks, to which a job coordinator of the same service provider is assigned as job coordinator.

Of the tasks belonging to those projects, she/he also sees only those, where someone of the same service provider is assigned as job coordinator.

On task level there she/he has only access to the tabs users, analysis, QA and events.

Of the job assignments to those tasks she/he sees only those, that a job coordinator of the same service provider did or where she/he is assigned him/herself.

In the user tab she/he can do everything, a PM can do. But only for the workflow steps where someone of the same service provider is assigned as job coordinator.

Task overview

In the task overview a job coordinator does only see tasks, that belong to a job coordinator that belongs to the same service provider.

Besides that, she/he has the same options as a PM (except for the "burger" menu of a task - see below)

Service provider overview

Service providers have the attributes:

• ID
• name
• assigned client(s)

Only if the job coordinators service provider is assigned to a client, she/he can be assigned to projects of that client.

If a client is unassigned from a service provider, all users that belong to that service provider  (and users of sub-service providers) are unassigned from all tasks that belong to that client.

Job coordinators of service providers are able to create new service providers themselves and assign clients to them, that are assigned to their own service provider.

Clients overview

In the clients overview a job coordinator can see all clients, to whom his service provider is assigned. Of the tabs where client meta data can be edited, job coordinators can only see the "user assignment defaults" tab.

The job coordinator can not add a new client.

For what job coordinators can do in "user assignment defaults" please see "user assignment".

User management

In the user management overview job coordinators can see and manage all users that belong to the same service provider, as they do.

They can give those users the same rights, they have themselves.

Users they add are always assigned to the same service provider they belong to.

If a PM or admin is adding job coordinators, they have to assign them to a service provider. Only one service provider can be selected.

User assignment

The user assignment in current translate5 can be done as default in the clients overview, in the import wizard or in the project overview for a selected task.

The import wizard is not accessible for job coordinators.

The job coordinators can only see those assignments, a job coordinator of their service provider did (also not those of sub service providers).

For the user assignment grid a column "type" is added. When adding/editing a user assignment, a drop-down "type" is added. Type for now can have the values "job coordinator" and "editor" ("pm" might be added in a further development step). Default is "editor".

If "job coordinator" is selected, the field "status" becomes inactive and no "status" is set for the job coordinator, because he has no active role as editor in the workflow.

Assignment of multiple job coordinators

A job coordinator can assign and unassign other job coordinators, as long as the following conditions are matched

• At least one job coordinator of his own service provider is still assigned
• Assigned job coordinators can only belong to his own service provider and maximum one other service provider

A PM can also assign multiple job coordinators to the same workflow step, but all of them have to belong to the same service provider.

Editing of a task

When editing a task, a job coordinator has the same rights as a PM. She/he can always access and edit tasks, where someone of the same service provider is job coordinator, except the task is locked for editing (same behavior as for a PM).

Burger menu of a task

In the burger menu of a task a job coordinator has the same options, as an editor user (a translator or reviewer). Those unique for PMs are missing.

Workflow implications (also mail notifications)

We create a new pre-defined workflow.

For each of the following workflow steps it is marked, if (in case a job coordinator is assigned) only the job coordinator gets a notification when the stop is finished or also the PM. These are defaults, that can be changed in the workflow actions table on DB level of an installation.

1. Workflow name: With Service provider. It contains the steps:
   1. LSP Translation (Notify on finish: Job coordinator)
   2. LSP Revision (Notify on finish: Job coordinator)
   3. LSP QA (Notify on finish: PM)
   4. Review  (Notify on finish: PM)
   5. LSP Review implementation (Notify on finish: Job coordinator)
   6. LSP QA 2 (Notify on finish: PM)
2. Complex (with service provider)

Who gets an e-Mail, when a workflow step is finished is configurable as workflow action.

Assigned job coordinators can also reopen finished tasks and change the job status and user assignments of all tasks, they are assigned to - yet only as long as not a job in the workflow chain is reached, that is not an LSP workflow step.