Both translatable and non-translatable files may be needed for a job.
Examples of non-translatable files include:
The calls described in this section allow for such resource files, as well as other translatable files, to be associated with a job.
Some of these resource types, such as translation memories and terminology databases, may be updated as part of executing the job. It is important that the updated resources can be accessed both during the job and as part of the delivery when the job is completed.
In some cases it may even be necessary to upload such resources before the job itself is submitted, e.g. to provide all input required to get an accurate quote or estimate for the job.
For this reason it is possible to call associateResource
with a job ticket that is not yet known to the system (e.g before submitJob
has been called).
Resources can be associated with more than one job.
retrieveJobInformation
.retrieveResourceInformation
.disassociateResource
.retrieveFullResourceList
.Call 1 | |
associateResource |
The content owner associates a translation memory with a new job that has not yet been uploaded. A resource URI is returned, which can be used to reference or retrieve the translation memory. |
Call 2 | |
requestQuote |
The content owner submits the rest of the job information and initiates the quoting process. The same job ticket as was passed to the previous call is used here. |
Call 3 | |
retrieveQuote |
The content owner retrieves the quote for the job. |
Call 4 | |
acceptQuote |
The content owner accepts the quote and the job is started. |
Call 5 | |
retrieveJob |
Once the job is completed the content owner retrieves the URI from which the results can be downloaded. |
The final version of the translation memory can now be downloaded from the URI returned from the original associateResource
call.
See also: associateResource
, disassociateResource
, retrieveResourceInformation
, retrieveJobInformation
, retrieveFullResourceList