Values.ImportTerminologyRequestSourceCreates or updates a custom terminology, depending on whether one already exists for the given terminology name. Importing a terminology with the same name as an existing one will merge the terminologies based on the chosen merge strategy. The only supported merge strategy is OVERWRITE, where the imported terminology overwrites the existing terminology of the same name. If you import a terminology that overwrites an existing one, the new terminology takes up to 10 minutes to fully propagate. After that, translations have access to the new terminology.
type nonrec t = {name : ResourceName.t;The name of the custom terminology being imported.
*)mergeStrategy : MergeStrategy.t;The merge strategy of the custom terminology being imported. Currently, only the OVERWRITE merge strategy is supported. In this case, the imported terminology will overwrite an existing terminology of the same name.
*)description : Description.t option;The description of the custom terminology being imported.
*)terminologyData : TerminologyData.t;The terminology data for the custom terminology being imported.
*)encryptionKey : EncryptionKey.t option;The encryption key for the custom terminology being imported.
*)}val make :
?description:??? ->
?encryptionKey:??? ->
?tags:??? ->
name:ResourceName.t ->
mergeStrategy:MergeStrategy.t ->
terminologyData:TerminologyData.t ->
unit ->
tval to_value :
t ->
[> `Structure of
(string
* [> `Enum of string
| `List of
[> `Structure of (string * [> `String of TagKey.t ]) list ] list
| `String of ResourceName.t
| `Structure of
(string
* [> `Blob of TerminologyFile.t
| `Enum of string
| `String of EncryptionKeyID.t ])
list ])
list ]