AI Value Translation Format

(Since version 1.19)

As a Large Language Model the Ursula AI is also capable of translating texts into various languages.

In this article you will learn how to create and navigate the translation formatting to your purposes.

 

How to create a formatting

1) In your job go to Datamaps.

2) Open Mapping.

3) Add a formatting by clicking on the + symbol.

 

4) Now go to Format (the third box from the left) and select ‘Translate via Ursula AI’ in the drop-down menu.

 

5) By clicking on ‘Edit format’ (the cogwheel symbol) you will enter the Settings window

 

Settings

 

Formatting

Shows the formatting you are currently working on. This can not be changed in the Settings window.

 

Status

The process condition of the formatting. For example, if it is approved, a work-in-progress or denied.

 

Name

The title of the formatting. This setting is only recommended if you are planning to link to this format via the format ‘Link on another configuration‘.

 

> Conditions

Here you can set the conditions to meet before the formatting starts.

You can find out more by clicking on this LINK (Setting conditions).

 

> Placeholders

Allows you to control the placeholders of the formatting.

Learn more by clicking on this LINK (Working with placeholder conditions).

 

Format of the source value

Specifies the format how the source value will be transformed before it is given to the AI.

 

Source language for the translation

Select the language to be translated here. Since the Ursula AI is not able to recognize the language to be translated independently, it must be instructed via this input box.

For example: If your source value is in English, choose English.

 

Behavior, when and how the translation should be made

Here you can choose conditions on how and when the texts will be translated. For example, if the Ursula AI should always translate or pay attention to values that have already been inherited.

This of course, also controls how often the AI is prompted, meaning this affects the costs. We only recommend the option `Always translate` for testing purposes and then switching to `Only translate from the source language if the value in the current language is empty`, so that the AI is only prompted when necessary.

 

Prompt dependent on target languages. You can use the placeholders {Language} = full name of the CS language and {SourceValue} = input value

Allows you to create specific AI prompts for the translation. For example if texts should be shortened in German—since they tend to be longer in this language.

Important: If you create a prompt (by clicking on the + symbol beneath the table) it will not only overwrite the ‘DEFAULT‘ prompt and also any prompt in the same language that came before. Therefore it is necessary to copy any text from earlier prompts into the latest one to ensure the instructions will still be followed by the AI.

 

Should results be cached with the same source value and prompt?

Controls whether the AI shall always be prompted anew even if the prompt and the source value is the same.

Please note: You can only choose between ‘yes‘ and ‘no‘. Latter will create more costs. If ‘yes‘ is selected the previous answers will be reused.

 

Run Example

To fully understand how you can translate values with the Ursula AI it is best demonstrated with a step-by-step case example.

My goal for this example is to translate the German values of an language-independent attribute into English, French and Japanese.

 

1) I create a format by clicking on the + symbol beneath the table.

2) As Attribute I select ‘Description (26)‘.

3) In the Export Column I write ‘productTexts|description|{StoreView}‘

With the pipe I I make sure that the ‘description‘ is sorted into ‘productTexts‘  when exported into an array. With the curly brackets { } I create a placeholder, in my example for language switches.

4) As Format I choose ‘ Translate via Ursula AI‘.

5) With the basics set I click on the ‘Edit format‘ button (the cogwheel) to open the Settings window.

 

6) For a Name I choose ‘Translation Format‘.

 

7) For Format of the source value I select ‘CS::Formatted value (CS formatted)‘, since it retrieves the good-looking displayed value of an attribute, which is perfect for the AI to work with.

 

8) As for the Source language for the translation, I choose German (de(2)) since in my case, the passed value to the format is in German and I am planning to translate it into the other languages.

9) For the Behavior, when and how the translation should be made I allow the Ursula AI to ‘Always translate‘. This means it is translated even if values are existent in the target language.

 

10) For the language dependent prompt I create an own by clicking on the + symbol below the table.

11) For the language I select English (en). Then I copy the prompt from the ‘DEFAULT‘ into my new prompt and add the new instruction that the Ursula AI may not use the words ‘seamless‘ and ‘robust‘.

Since I only specified an extra prompt for English, all other languages will take their prompt out of the `DEFAULT` case. Hence, it is acting as the master case.

 

12) When asked if the results should be cached with the same source value and prompt, I choose ‘yes‘ .

 

12)  Afterwards I save my progress by clicking on the floppy disc button. Or just by pressing ALT + S.

 

Warning & Disclaimer

Was this article helpful?

0 0

How can we improve this article?

Please submit the reason for your vote so that we can improve the article.

Name

Email

Submit