Denis Filo 

It does sound like an interesting idea and would surely improve term recognition for languages such as Russian, Arabic, Finnish, etc. that have a rich morphology and numerous inflected forms.  Your timing is also good as the Terminology API has undergone some major changes recently, still some to come, that allow a developer to create their own Terminology Provider and integrate it more appropriately into Trados Studio than was possible before.

We haven't done anything serious with the new APIs yet, but as a starting point here's some resources you could look at that do take advantage of the Terminology API:

Integrates with the IATE terminology service:
https://github.com/RWS/Sdl-Community/tree/master/IATETerminologyProvider

Integrates to a SQLite database used by InterpretBank:
https://github.com/RWS/Sdl-Community/tree/master/InterpretBank

Integrates to Excel used as a termbase:
https://github.com/RWS/Sdl-Community/tree/master/TermExcelerator

The Terminology API itself is here: https://developers.rws.com/studio-api-docs/apiconcepts/terminology/overview.html

Most of the recent changes to the API can be found here: https://developers.rws.com/studio-api-docs/apiconcepts/releasenotes/tradosstudio2022sr2.html#terminology-provider

Hope that helps... but I'm sure others can offer more guidance if you have any questions.

Hi Paul ,

Many thanks for your reply and input. I will definitely check out the resources you have provided! That was exactly the idea we had in mind – to enhance term recognition for languages with rich morphology. As I am studying at a university in Czechia, slavic languages belong to that group, I believe.

When I have some additional questions, can I ask them via this forum thread, or is there a better/more efficient way to do so?

Thanks again!

 Denis Filo 

Denis Filo said:

can I ask them via this forum thread, or is there a better/more efficient way to do so?

Better to create a new thread for every question, and don't bundle questions into one thread.  That way we can track the threads and also mark them as suggested/verified answers which helps other users as well.

 Denis Filo 

Denis Filo said:

can I ask them via this forum thread, or is there a better/more efficient way to do so?

Better to create a new thread for every question, and don't bundle questions into one thread.  That way we can track the threads and also mark them as suggested/verified answers which helps other users as well.

Hi Paul  ,
I apologize for any inconvenience, but I would greatly value your opinion and perhaps some advice whenever you have a moment to spare. I've posted another question in a new thread here: https://community.rws.com/developers-more/trados-portfolio/trados-studio-developers/f/sdk_qa/52009/lemmatization-plugin-development-lemmatization-default-term-recognition-for-trados-studio-2022

Basically, I'm unsure if it's possible to implement lemmatization using the Terminology Provider. My intention is solely to perform lemmatization, while relying on Trados for default term check/term recognition, and translation as it is now. Since I don't have any specific termbase or glossary to integrate, and I don't know if it possible to work around it or if I should consider some other approach.

Thank you for your time and assistance.

Denis

Denis Filo 

I note Patrick responded to you.  You can absolutely do this with a Terminology Provider, but perhaps requiring a bit more work than you envisaged.  The whole point of the provider is that it can provide you access to use the term check/term recognition etc. in Studio via the API and you can add your own code into the plugin you develop using this provider to handle the lemmatization.

Patrick is a good person to advise on this.  He also built the AI Professional app and this can compare a recognised term from a termbase in MultiTerm, or Language Cloud, and ensure that the terms are being used in the translation.  It will also correct the use of the term so that it's grammatically correct to suit the context of the sentence even if the term in the termbase was a different form.  So in theory does something similar to what you are proposing here.  He didn't build something just to handle the provision of a term with the correct form, but the end result would be that.

Thank you for you clarification Paul ! Okay I see now, I will try to create a Terminology provider as you suggested to me previously, I just misunderstood some parts at first and now I have a little bit better picture of it I would say. Sorry for any inconvenience again, but I just want to ensure I'm on the right track. I may have more questions in the future, and I hope it's okay to reach out again. Thank you for your patience and guidance.