Presentation on theme: "Usage of the memoQ web service API by LSP – a case study"— Presentation transcript:
1Usage of the memoQ web service API by LSP – a case study
2Outline About think global What is a WS-API? Usage of WS-API through the engineering departmentEmbedding memoQ into automated workflowsCommon problems and limitations
3About think global think global is a medium size, multilingual LSP Customers are from different branchesSoftware companies are a big and important customer groupThis leads to rather big and complex projectsmany filesmany languagesdifferent, complex formatsfrequent updates
4About think global think global has different departments The engineering departmentprepares content for translationdevelops tools for preparationuses mainly Java as a programming language
5What is a WS-API? API – application programming interface It provides programming access to software functionalityIn memoQ: Create projects, add users, ...Advantage: Repetitive tasks can be implemented once but used several times
6What is a WS-API?A web service is a service that can be accessed through a networkThe content is packed in XML filesIt is a standard that is supported by most programming languagesFeels like local programming
7What is a WS-API? Web Service Java C++ PHP ... Because we have complex projects with automated workflows and use Java anyway, it’s only a small step to the usage of the ws-api.
8Usage of WS-API Through Engineering Simple tasks used by the engineering department:Creation of resources (e.g. TMs for multilingual projects)Cloning of resources with slightly different settingsMulti-step tasks (e.g. clearing TMs)Import of huge projects with different filtersExport to different formatsBackup of projects / resourcesControl tasks (resource settings, user groups, ...)
9Embedding memoQ Workflow example: machine translation Projects are prepared in memoQBilingual export + conversion to machine friendly formatMachine translationConversion + importtg has an own translation machine that is already trained to match our needs.
10Embedding memoQ Analysis of memoQ projects advantage: all needed analysis are done at oncememoQ client is still availableAssign translators to documentsvery time consuminghas to be done twice (in the project management system and in memoQ)
12Problems and Limitations API complexity and designThe API is complex; understanding it is time consumingThe design is not always consistent
13Problems and Limitations API functions sometimes differ from GUI functionsTM settings are not used in analysisSome project settings cannot be readSetting of import / export path is not possible...For me the worst point. Make it clear for kilgray staff !!!!!!
14Problems and Limitations UpdatesGood news!API is updated automatically with memoQ serverVery few changes in API functionsOnly MBDs have been replaced with MQXLZ recently
15Problems and Limitations BugsThere are not many bugs, but ...WS-API has few users, bugs are not reported and resolved as fast as ‘normal’ memoQ bugsInstallation of older versions is not possibleWhen problems occur, finding workarounds is difficultCombination with missing features can lead to severe problems
16Problems and Limitations Example: Export bugBug description: Some documents cannot be exportedChange to older version impossibleNo workaround via API possibleMissing functionality setExportPath()=> ‘Export to stored path’ via GUI is not possibleEvery document has to be exported manually to the correct subfolder
17ConclusionThe usage through the engineering department saves time and costs (and can be fun!)It avoids human mistakes and raises qualityAutomated usage through third parties (like project managers) can be a huge benefit, but has to be introduced with careCarefully define the functionality you want to implementThink about performance