...
| Term search | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Request | GET /editor/plugins_termportal_data/search | |||||||||
| Params | query * Required. Search query. Wildcard characters '*' and '?' are supported for multi- and single-char searches, respectively. | |||||||||
language Required. ID of language which searched terms belong to. See lang in Client app setup data response structure | ||||||||||
| limit Requred. Results limit per page. Integer value expected. | ||||||||||
| start Required. Results offset. Integer value expected. | ||||||||||
clientIds Optional. Comma-separated list of integers, representing client IDs. See | ||||||||||
collectionIds Optional. Comma-separated list of integers, representing collection IDs. See filterWindow.collections in Client app setup data response structure | ||||||||||
| processStatus Optional. Comma-separated list of any of 'unprocessed', 'provisionallyProcessed', 'finalized' and 'rejected'. | ||||||||||
| noTermDefinedFor Optional. ID of language, that term is not yet defined for | ||||||||||
attr-x Optional. Attribute search, where 'x' - is the key in filterWindow.attributes (see Client app setup data response structure). If param name is mentioned among request params but no param value given, the search will return the terms having such attributes defined even despite having empty value. If param value is given, wildcard characters '*' and '?' are supported, first for multichar and second for single-char purpose. Multiple attributes search are supported, just use attr-x, attr-y etc | ||||||||||
termEntryTbxId Optional. Partially known tbx ids are supported | ||||||||||
| termTbxId Optional. Partially known tbx ids are supported | ||||||||||
tbxCreatedBy Optional. ID of person who was specified as creator in imported tbx data (see filterWindow.tbxCreatedBy array in Client app setup data response structure) | ||||||||||
| tbxCreatedGt Optional. Should be used to search terms created since certain date, inclusively, according to imported tbx data. Value is expected in format yyyy-mm-dd. Can be used with tbxCreatedLt if search by date range is needed. | ||||||||||
| tbxCreatedLt Optional. Should be used to search terms created until certain date, inclusively, according to imported tbx data. Value is expected in format yyyy-mm-dd. Can be used with tbxCreatedGt if search by date range is needed. | ||||||||||
| tbxCreatedAt Optional. Exact date of creation specified in imported tbx data. Date in format yyyy-mm-dd is expected. This can only be used if f tbxCreatedGt and tbxCreatedLt are NOT given | ||||||||||
| tbxUpdatedBy Optional. ID of person who was specified as updater in imported tbx data (see filterWindow.tbxUpdatedBy array in Client app setup data response structure) | ||||||||||
| tbxUpdatedGt Optional. Should be used to search terms updated since certain date, inclusively, according to imported tbx data. Value is expected in format yyyy-mm-dd. Can be used with tbxUpdatedLt if search by date range is needed. | ||||||||||
tbxUpdatedLt Optional. Should be used to search terms updated until certain date, inclusively, according to imported tbx data. Value is expected in format yyyy-mm-dd. Can be used with tbxUpdatedGt if search by date range is needed. | ||||||||||
tbxUpdatedAt Optional. Exact date of creation specified in imported tbx data. Date in format yyyy-mm-dd is expected. This can only be used if tbxUpdatedGt and tbxUpdatedLt are NOT given | ||||||||||
| ||||||||||
...
| Transfer terms to main translate5 app as project of type 'termtranslation' | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Request | POST /editor/plugins_termportal_data/transfer | |||||||||
| Params | clientId Required. Id of a customer, that newly created termtranslation-project will belong to | |||||||||
| projectName Required. Project name | ||||||||||
sourceLang Required. ID of source language. See lang in Client app setup data response | ||||||||||
targetLang Required. Comma-separated list of target languages IDs. See langAll in Client app setup data response | ||||||||||
terms=(all|none) Required. Terms selection mode. Used in conjunction with except param, e.g. the idea of possible selections are:
| ||||||||||
| except Required if terms=none. Empty string or comma-separated list of term IDs | ||||||||||
| translated=(0|1) Required. Whether to transfer terms for translation even if they already have translation for given target languages | ||||||||||
| definition=(0|1) Required. Whether to transfer terms definition-attrs for translation as well | ||||||||||
Response is containing json-object with key names from step1 to step5, and responses from the corresponding steps of project creation workflow
| ||||||||||
| Create new term | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Request | POST /editor/attribute | |||||||||
| Params | collectionId Required. ID of TermCollection that new term should be created in See filterWindow.collections in Client app setup data response | |||||||||
language Required. Rfc5646-code of a new term's language. See langAll[*].value in Client app setup data response | ||||||||||
| term Required. Term text itself. String. | ||||||||||
| note Required if runtimeOptions.termportal.commentAttributeMandatory config is On. String. | ||||||||||
| termEntryId Optional. ID of termEntry, which new term should be attached under. If not given - new termEntry will be created. | ||||||||||
| ||||||||||
| Create proposal for existing term | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Request | PUT /editor/attribute | |||||||||
| Params | termId Required. ID of existing term, for proposal to be created for | |||||||||
| proposal Optional. If not given, the existing proposal will be deleted, so existing term will be kept with no proposal | ||||||||||
| ||||||||||
Provides access to the Term collections available in the application.
...