...

All terminology is imported with respect to a customer specific config are associated to that customer, which should be copied from TermImport/config/instruction.ini and uploaded to the remote SFTP directory's Import-folder, which is then accessed by translate5.

If there is no instruction.ini in the remote directory's Import-folder - the import won't be started.

Folder structure

Each remote SFTP folder may 4 folders:directory may have from 1 to 2 of 4 possible folders (sub-directories):

• Import - This is single folder, initially expected to exist inside SFTP directory
  
  • *.tbx files to be imported
  • instruction.ini that contains the settings
  Import
  
  • In this folder there should be one instruction.ini file, that contains the setting to control the import behaviour Others files are expected to be of *.tbx-files
• Error
  • If an error happens on import, the Import-dir is renamed to Error-dirat least one tbx-file was failed to import - this folder will be automatically created and failed tbx-file will be moved here
• Import-running
  • we move the project folder here during importIf we had Import folder having valid instruction.inifile then Import folder is renamed to Import running
•  Import-success
  • In case the transfer of the data is successful, the imported tbx-files beneath the import folder is moved to the Import-success folder. Still the import itself may running in translate5.

...

Endpoint: editor/termimport/force-check

Possible GET params:

Configuration

...