Page History

...

Proposals export for a TermCollection, as XLSX

Request

GET editor/languageresourceinstance/export

Params

collectionId Required. Id of a TermCollection to be exported.

exportDate Optional.If given, should be a date in YYYY-MM-DD (or YYYY-MM-DD HH:MM:SS) format, so that only proposals happened after that date will be exported.

Important: response for this endpoint comes with 'Content-Disposition: attachment' HTTP header to provide a direct download of an exported file.

Code Block

language	js
title	Response
collapse	true

raw binary contents of an exported XLSX file

Important: If no proposals found, then the endpoint will respond with the following XML text

Code Block

language	js
title	Response
collapse	true

<?xml version="1.0"?>
<response><message>No results where found.</message></response>

Detect non-existing terms among the given ones - in any of accessible TermCollections

, among the given ones

Request

GET editor/termcollection/searchtermexists

Params

searchTerms Required. Should be given as JSON-encoded array structured in the following way:

Code Block

language	js
title	Response
collapse	true

[
    {
        "term": "Some existing term 1",
		"anyOtherProp1": "Some other value 1",
 		"anyOtherProp2": "Some other value 2", 
     },
     {
        "term": "Some non-existing term 1",
		"anyOtherProp1": "Some other value 3",
 		"anyOtherProp2": "Some other value 4", 
     },
     {
        "term": "Some non-existing term 2",
		"anyOtherProp1": "Some other value 5",
 		"anyOtherProp2": "Some other value 6", 
     }
 ]

targetLang Required. Should be given as RFC5646 language code representing a major language (e.g. 'en') or with sublanguage (e.g. 'en-US'), but keep in mind that sublanguage will be ignored.

Important: this endpoint is currently used internally by Translate5's InstantTranslate plugin, and allows to exclude existing terms from the given ones, so only non-existing are returned in response

Code Block

language	js
title	Response
collapse	true

{
    "rows: [
	     {
    	    "term": "Some non-existing term 1",
			"anyOtherProp1": "Some other value 3",
	 		"anyOtherProp2": "Some other value 4", 
    	 },
 	     {
    	    "term": "Some non-existing term 2",
			"anyOtherProp1": "Some other value 5",
	 		"anyOtherProp2": "Some other value 6", 
    	 }
     ]
}

...

Page tree

Versions Compared

Old Version 55

New Version 56

Key

Proposals export for a TermCollection, as XLSX

Detect non-existing terms among the given ones - in any of accessible TermCollections