...
Delete termcollection | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
Request | DELETE /editor/termcollection/ID | |||||||||
URI Params | ID Required. Id of a termcollection to be deleted | |||||||||
Note: Deleting term collection will remove all terms, terms attributes and term entry attributes assigned to this term collection
|
Import terms to theterm collectionTermCollection via tbx-file | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
Request | POST /editor/termcollection/import | |||||||||
Params | collectionId Required. Id of a termcollection TermCollection where terms should be imported to. | |||||||||
customerIds Optional. Comma-separated list of customers ids for this termcollection to be associated with. | ||||||||||
mergeTerms Optional. Boolean value to merge imported terms with terms already existing (if any) in the target termcollection. By default - false. The merge process is complex and completely described here. | ||||||||||
importSource Optional. If given, should be either 'filesystem' or 'crossApi' | ||||||||||
deleteTermsLastTouchedOlderThan Optional. If given, should be in YYYY-MM-DD format, so that any terms last updated before the given date - will be deleted from the target TermCollection. 'Last updated' date for a term is initially set up at current date on import and then refreshed each time term is renamed and/or any of it's attributes created/updated/deleted. 'Last updated' date is maintained internally by translate5, and is not directly shown in TermPortal UI. However, it is replicated to 'Updated by'-field in 'Term attributes'-panel in TermPortal UI each time any further change happended after initial import. | ||||||||||
deleteTermsOlderThanCurrentImport Optional. Boolean value to delete all terms from the target TermCollection, that are were last updated before the the start of the current import. | ||||||||||
|
...