Foreign Language Translation Workflow for Intel
Moraph software. Run your translation office's workflow for unclassified administrative records in one place. Requests come in from staff or through the Work API, go to linguists by language, proficiency level and workload, are checked by a second linguist in QA review, are certified by a certifying linguist other than the translator where the request needs it, and are delivered with a printable cover sheet. Your linguists do the translating, not the app. Every assignment, QA result, certification and due-date change is kept with who made it, and turnaround, backlog, throughput and quality are reported from your own records.
Raise a ticket about Foreign Language Translation Workflow for IntelTroubleshooting guide (sign in to read)Product documentation
Critical incident? Raise an S1 ticket and also call the support number in your organization’s service agreement, so the on-call team is engaged straight away. Check Moraph Status for incidents already under way.
What Moraph Support handles
- The queue, suggestions and assignment not behaving as described.
- Roster, QA review or turnaround pages showing unexpected figures.
- Settings, Work API keys and sign-in on the Moraph side.
- Questions about how features work.
What goes elsewhere
- Translation quality and judgments go to your linguists and the translation office.
- Linguists’ proficiency levels and testing go to your language program.
- Classification and handling questions go to your security staff; never enter classified material here.
- Machine translation is not part of this product.
Choosing a severity
| Severity | Examples for Foreign Language Translation Workflow for Intel |
|---|---|
| S1 Critical A production service is down or unusable, data may be at risk, or a security incident is under way, and there is no workaround. |
|
| S2 High A production service is badly degraded or an important function is failing, and the workaround is poor or temporary. |
|
| S3 Normal Something is not working as it should, but there is a reasonable workaround or the impact is limited. |
|
| S4 Low A question, a minor problem, a request for information or a change that can be planned. |
|
Response and resolution targets for each severity are the ones in your organization’s service agreement with Moraph.
Before you raise a ticket
- Check the linguist is Active, available and at the minimum level in Translation settings.
- Check the language is spelled the same on the request and the linguist.
- Check Activity for recent changes to settings.
- For integrations, check the Work API key has not expired or been revoked.
What to include in the ticket
- The request or linguist reference.
- The languages involved.
- What you expected and what happened, with the time.
- The role of the person affected.
- A description only; never paste source material or translations into the ticket.
Don’t include passwords, secrets or full records of patients, customers or citizens. If we need data like that, we will arrange a secure way to receive it.
Common problems and fixes
A request shows no suggested linguist.
Likely cause: No Active, available linguist at the minimum level in the language has room under their capacity.
What to do: Check the roster’s coverage for the language, a linguist’s capacity or Unavailable until date, or the minimum level in Translation settings.
A linguist with the language isn’t suggested.
Likely cause: The language is spelled differently on the linguist and the request, or their level is below the minimum.
What to do: Use the same language name on both, and check the level.
A request can’t be delivered.
Likely cause: QA is required and there is no passing QA result, or the result is Returned for rework.
What to do: Have the QA reviewer record the result, or send it back to In translation.
A linguist can’t record a QA result.
Likely cause: They are the request’s translating linguist.
What to do: The QA reviewer or a product administrator records it.
A request can’t be created.
Likely cause: It wasn’t confirmed unclassified.
What to do: Confirm it is unclassified. Classified material must not be entered at all.
A linguist doesn’t get tasks for their requests.
Likely cause: Their Linguist record isn’t assigned to their Moraph account.
What to do: Assign the Linguist record to their account; new assignments follow it.
A QA result or certification is refused.
Likely cause: The request isn’t in QA review, the person isn’t the QA reviewer or certifier on their own account, or they translated it.
What to do: Move it to QA review; the QA reviewer, the certifying linguist or a product administrator records it.
A linguist can’t change their own levels.
Likely cause: Linguists can’t change their own levels, QA or certification flags.
What to do: A coordinator or product administrator records the new levels; the level history keeps the change.
A language name is refused.
Likely cause: Translation settings have a language list and the name isn’t on it.
What to do: Use the listed name, or ask a product administrator to add it.