To get the server to extract metadata from a model, you must first translate the model to a viewer-friendly format. While this tutorial translates the model to SVF, you can just as well translate to SVF2. The procedure to extract metadata is identical for both formats.
For this task, you use the Base64-encoded URN of the source file. In the previous task, Postman saved this URN to the variable t5_ossEncodedSourceFileURN. You use this variable to reference the model in the next request.
-
In the Postman sidebar, click Translate to SVF > Start a Translation Job. The request loads.
-
Click the Body tab and take note of the JSON payload.
-
Click Send. If the request is successful, you should see a screen similar to the following image.
Note the
urnattribute in the JSON response. The value of this parameter is the URL-safe Base64 encoded URN of the source file. A script in the Tests tab, saves this value to a variable namedt5_url_safe_urn_of_source.
When you kick off a translation job, it takes time to complete. There are two ways to check if the translation job is done:
-
Periodically check the status of the translation job.
-
Set up a webhook to notify you when the job is done.
This tutorial checks the status of the translation job periodically. For information using the webhooks method, see the documentation on Model Derivative webhook events
-
In the Postman sidebar, click Translate to SVF > Check Status of Job. The request loads.
Note how the URL-safe Base64-encoded URN of the source file is used as a URI parameter, in the form of a variable (
t5_url_safe_urn_of_source). -
Click Send. A screen similar to the following image is displayed.
-
Repeat step 2 until the value of the
progressparameter becomescomplete, as shown in the following image.
