Description
The database-side storage of terms is extended by the "TermCollection", which makes it possible, for example, to group terms that belong to a specifc client. This way an end client can be assigned to one or more TermCollections.
Provides access to the Term collections available in the application.
URL: | /editor/termcollection/[ID] |
Available Methods: | GET / POST / PUT / DELETE |
Specialities: |
|
Resource Layout
Name | Type | Info |
id | int | GET only |
name | string | The name of the term collection |
timestamp | DateTime | Date and time when the term collection is created |
customerId | integer | Foreign key to the customers table |
Import terms to the term collection
| URL: | editor/termcollection/import |
| Available Methods: | POST |
| Specialities: | Import the provided terms from the tbx file to the term collection |
POST request parameters example(json):
"data":{ "collectionId":"the id of the term collection where those terms from the tbx file are going to", "customerId":"customer for which this term collection is associated with", "mergeTerms":"If the parameter is true, translate5 will search all existing terms to see if the same term already exists in the TermCollection in the same language .If the parameter is false, a new termEntry is added to the termCollection with the term ID of the TBX file and all terms of this termEntry of the TBX file are added to this new termEntry in the termCollection with the term IDs of the TBX file (same thing as if no term from this termEntry in the TBX can be matched in the termCollection)." } |
| Important: with the import call, one or multiple tbx files must be provided |