| In the Translation Job life cycle, once the translated XML from the Service Provider has been uploaded to the Import folder on the server, the system automatically associates it with its various translation jobs, and it is then ready to be imported into the Library. Translation jobs in this state display Ready for Import in the Status column in the Translation Jobs list. Draft import imports the job and applies the state for draft imports to the updated objects. Use Draft import to create a review document to review the translations. Or use Reviews to review the translations. After review and possible updates to the translation job xml, do a final import. The final import changes the state of the objects to the final state for translations. |
To do a Draft import of a translation job:
- From the Translation Jobs list, select one or more jobs. The jobs that are ready for importing show the status as Ready for Import.
- In the ribbon, choose Translation Jobs > Draft Import, or right-click the job or jobs and then choose Draft Import.
The XML is imported. The modified local variant objects get the release state for draft imports. The state of the translation job changes to Draft Imported.
What happens to the files after successful draft import
The associated XML files, zip files, and the job folders (which contain all of the image files) in the Import folders are not removed. The log file stays with the translation job record.
After a Draft import
The next step in the process is to publish the translated content and have it reviewed. Send any review comments to the localization service provider. The service provider updates the translation job xml (and the translation memory of the translation tool that they use). Upload this updated xml.
If no change was done the xml, because the translation was okay, you can just do a final import of the xml that was already uploaded before.
If the xml has been updated, you can decide if you do another draft import or continue with a final import.