Skip to main content

Setting up the project

Under Projects, using the advanced or simple form, a project manager creates a new project, typically specifying:

  • Source language
  • Target language(s)
    • This is also the time to select a "First" language, often English
    • This language will be used to create the timed template which facilitates translation into the other languages
  • Number of parts/episodes
    • And any relevant individual specifications, such as running time, part name, etc
  • Project deadline
    • When is the whole project due

Simple project form. The main data such as title and deadline is added in the top section. 

fqgproject_with_simple_form_top.png

Specify parts information. (By updating the "Number of parts" value, you get additional lines.)

project_with_simple_form_parts.png

Select all target languages and specify which is "first".

project_languages.png

Besides this data, there are numerous other fields that can be used to provide additional information. 

Applying a joblist template

Once the project is in place, a joblist template is selected and applied to the project, creating the necessary jobs that need to be done in order to complete the project.  

Click the "Job list" icon in the project bar of the newly created project.

project_bar_joblist_icon.png

On the joblist page, click "Template" and select a joblist template. (Generic example templates are included, but you would normally have a tailor-made template ready before this step.)

joblist_selecting_joblist_template.png

After the template is applied, jobs have been added to the project structure. Depending on the settings for each rule in the joblist template, they may already be assigned to users. 

joblist_after_template.png

Assigning work or verifying automatic selections

Joblist templates can be set up to automatically assign the created jobs based on criteria. They can also be made to simply store the criteria with each job, to make assignment easier later. In some cases, you may want to override all criteria and simply select users for some or all jobs. 

The starting point in all these cases is usually the joblist. View the pre-assigned jobs, fill in the blanks, adjust where necessary, until relevant jobs have someone to do them. 

(Of course, in a perfectly set up system where all relevant information is available for all users, no visual confirmation is necessary and the assigned users can simply be notified.)

Notifying users / requesting job confirmation

Jobs, especially outsourced ones, typically require confirmation by the assigned user. Regardless of whether they have been selected automatically by the system or manually by the project manager, there are tools for notifying the selected users right from the joblist.

Under emails, select the relevant notification options. They are similar in use, but made for different scenarios.

  • Confirmation emails are sent to users who have been assigned one or more jobs that have the status "Awaiting confirmation".
  • Job tank emails are sent to all users matching the job criteria for one or more jobs that have the "Job tank" option set to Yes. 
    • (In both cases, only one email is sent to each user, summarising all the information.)

job_confirmation_requests.png

At this point, the workflow is all set up and relevant users have been notified. However, there may still be work to do for the project manager before work can actually begin. Read more under "Handling project media".



Back to top